Minor impactResolvedDatabases

Pinecone incident: [Pods][AWS][us-east-1] Write failures and high latency

Pinecone reported this minor-impact incident on its official status page on Sep 28, 2026, 04:13 UTC. It was resolved after 8 min.

Right now Pinecone is operational. Live Pinecone status →

🔔 Get alerted when Pinecone has issuesFree · email alerts · no credit card
Sep 28, 2026, 04:13 UTC
started
Sep 28, 2026, 04:20 UTC
resolved
8 min
duration
Minor
impact

Affected components

  • us-east-1-aws

Timeline

updates from Pinecone's status page ↗
  1. resolvedSep 28, 2026, 04:20 UTC

    The third party dependency recovered, this incident has resolved.

  2. identifiedSep 28, 2026, 04:13 UTC

    A shared dependency is having issues. Determining mitigation

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][eu-west-1] 5xx on read requests (Sep 22, 2026)
Pinecone incident on Sep 28, 2026: [Pods][AWS][us-east-1] Write failures and high latency · APIStatus.watch