Minor impactResolvedDatabases

Pinecone incident: [Serverless][GCP][europe-west4] Indexing lag on some indexes; recent writes may not appear in reads

Pinecone reported this minor-impact incident on its official status page on Aug 26, 2025, 13:22 UTC. It was resolved after 1h 43m.

Right now Pinecone is operational. Live Pinecone status →

🔔 Get alerted when Pinecone has issuesFree · email alerts · no credit card
Aug 26, 2025, 13:22 UTC
started
Aug 26, 2025, 15:05 UTC
resolved
1h 43m
duration
Minor
impact

Affected components

  • GCP europe-west4

Timeline

updates from Pinecone's status page ↗
  1. resolvedAug 26, 2025, 15:05 UTC

    This incident has been resolved.

  2. monitoringAug 26, 2025, 14:13 UTC

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

  3. investigatingAug 26, 2025, 13:22 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] Unavailability for some read path operations for some indexes (Aug 21, 2025)Next: [Serverless][AWS][us-west-2] Unavailability for some read path operations for some indexes (Aug 28, 2025) →
Pinecone incident on Aug 26, 2025: [Serverless][GCP][europe-west4] Indexing lag on some indexes; recent writes may not appear in reads · APIStatus.watch