Minor impactResolvedDatabases

Pinecone incident: [AWS][us-east-1] 5xx errors for some requests on some indexes

Pinecone reported this minor-impact incident on its official status page on Jun 6, 2026, 00:48 UTC. It was resolved after 27 min.

Right now Pinecone is operational. Live Pinecone status →

🔔 Get alerted when Pinecone has issuesFree · email alerts · no credit card
Jun 6, 2026, 00:48 UTC
started
Jun 6, 2026, 01:15 UTC
resolved
27 min
duration
Minor
impact

Affected components

  • AWS us-east-1

Timeline

updates from Pinecone's status page ↗
  1. resolvedJun 6, 2026, 01:15 UTC

    This incident has been resolved.

  2. monitoringJun 6, 2026, 01:00 UTC

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

  3. identifiedJun 6, 2026, 00:53 UTC

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

  4. investigatingJun 6, 2026, 00:52 UTC

    We are continuing to investigate this issue.

  5. investigatingJun 6, 2026, 00:48 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-west-2] 5xx errors and longer response times on upsert requests for some indexes. (May 25, 2026)Next: [Serverless][AWS][us-west-2] Read path operations for some indexes may experience elevated latency and timeouts (Jun 6, 2026) →
Pinecone incident on Jun 6, 2026: [AWS][us-east-1] 5xx errors for some requests on some indexes · APIStatus.watch