- Level
- confirmed
- Worst impact
- Degraded
- Components
- AWS us-west-2
- Regions
- us, us-west-2
- Down Index
- 28of 100
What to do
Check whether you use Pinecone AWS us-west-2 in us, us-west-2. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 45m it lasted.
Anything that failed between 2026-06-06 13:05 UTC and 2026-06-06 15:50 UTC may need a replay.Subscribe to Pinecone's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=pinecone works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Pinecone 2
- investigating
We are currently investigating this issue.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-b1f83b5cfb
Is Pinecone still down?
No, this incident was resolved 2026-06-06 15:50 UTC. For Pinecone's live state, see https://down.guide/pinecone.
How long did it last?
2h 45m, from 2026-06-06 13:05 UTC to 2026-06-06 15:50 UTC, by the times Pinecone posted.
What was affected?
Pinecone named AWS us-west-2 in us, us-west-2.
What caused it?
Pinecone hasn't published a root cause. If it does, it shows here.
Where does this come from?
Pinecone's official status page, https://status.pinecone.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.