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

Affected components

• AWS us-east-1

1. resolvedJul 13, 2026, 04:15 UTC

   This incident has been resolved.

2. identifiedJul 12, 2026, 23:46 UTC

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

3. investigatingJul 12, 2026, 23:21 UTC

   We are observing freshness lag affecting a small number of indexes in AWS us-east-1, resulting in some queries not serving fresh data. We are actively investigating.

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.

• Sentry: Ingestion delayed for spans, logs, crons in US regionCritical · Jul 13, 2026, 00:58 UTC
• Inngest: Issues Affecting Function Triggering from EventsMajor · Jul 10, 2026, 17:44 UTC
• Clerk: Elevated errors while configuring domainsMajor · Jul 12, 2026, 22:05 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC

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