Minor impactResolvedDatabases

Pinecone incident: Some initial queries to infrequently read namespaces incorrectly returning empty results

Pinecone reported this minor-impact incident on its official status page on Jun 18, 2026, 10:00 UTC. It was resolved after 8h 23m.

Right now Pinecone is operational. Live Pinecone status →

🔔 Get alerted when Pinecone has issuesFree · email alerts · no credit card
Jun 18, 2026, 10:00 UTC
started
Jun 18, 2026, 18:23 UTC
resolved
8h 23m
duration
Minor
impact

Affected components

  • AWS eu-west-1
  • AWS us-west-2
  • Azure eastus2
  • GCP europe-west4
  • GCP us-central1

Timeline

updates from Pinecone's status page ↗
  1. resolvedJun 18, 2026, 18:23 UTC

    This incident has been resolved.

  2. investigatingJun 18, 2026, 10:00 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 for some requests on some indexes (Jun 6, 2026)Next: [Serverless][Azure][eastus2] 5xx errors on some requests for some indexes (Jul 9, 2026) →
Pinecone incident on Jun 18, 2026: Some initial queries to infrequently read namespaces incorrectly returning empty results · APIStatus.watch