Minor impactResolvedDatabases

Pinecone incident: [Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces

Pinecone reported this minor-impact incident on its official status page on Feb 5, 2026, 10:55 UTC. It was resolved after 11h 2m.

Right now Pinecone is operational. Live Pinecone status →

🔔 Get alerted when Pinecone has issuesFree · email alerts · no credit card
Feb 5, 2026, 10:55 UTC
started
Feb 5, 2026, 21:57 UTC
resolved
11h 2m
duration
Minor
impact

Affected components

  • AWS us-east-1

Timeline

updates from Pinecone's status page ↗
  1. resolvedFeb 5, 2026, 21:57 UTC

    This incident has been resolved.

  2. monitoringFeb 5, 2026, 21:01 UTC

    A fix has been implemented and we are monitoring the results.

  3. identifiedFeb 5, 2026, 14:29 UTC

    The issue has been identified and a fix is being implemented.

  4. investigatingFeb 5, 2026, 10:55 UTC

    We are currently investigating this issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Pinecone's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Pinecone have incidents?

Pinecone reported 9 incidents in the last 90 days, 6 of them major or critical. A typical incident lasted 1h 15m. See Pinecone's uptime and incident history

← Previous: [Serverless][AWS][us-east-1] 5xx errors on read operations for some indexes (Jan 15, 2026)Next: [GCP][us-central1][europe-west4] Errors on some read operations (Feb 23, 2026) →
Pinecone incident on Feb 5, 2026: [Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces · APIStatus.watch