Major impactResolvedDatabases

Pinecone outage: [Serverless][AWS][us-east-1] 5xx errors on read operations for some indexes

Pinecone reported this major-impact incident on its official status page on Jan 15, 2026, 12:12 UTC. It was resolved after 3h 18m.

Right now Pinecone is operational. Live Pinecone status →

🔔 Get alerted when Pinecone has issuesFree · email alerts · no credit card
Jan 15, 2026, 12:12 UTC
started
Jan 15, 2026, 15:30 UTC
resolved
3h 18m
duration
Major
impact

Affected components

  • AWS us-east-1

Timeline

updates from Pinecone's status page ↗
  1. resolvedJan 15, 2026, 15:30 UTC

    This incident has been resolved.

  2. monitoringJan 15, 2026, 14:30 UTC

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

  3. identifiedJan 15, 2026, 13:57 UTC

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

  4. investigatingJan 15, 2026, 12:12 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: Intermittent unavailability across all environments for some indexes (Jan 2, 2026)Next: [Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces (Feb 5, 2026) →
Pinecone outage on Jan 15, 2026: [Serverless][AWS][us-east-1] 5xx errors on read operations for some indexes · APIStatus.watch