- Level
- confirmed
- Worst impact
- Partial outage
- Components
- AWS us-east-1
- Regions
- us, us-east-1
What to do
Check whether you use Pinecone AWS us-east-1 in us, us-east-1. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 15h 14m it lasted.
Anything that failed between 2025-09-02 22:46 UTC and 2025-09-03 14:00 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 3
- investigating
We are currently investigating this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-4fa2b49693
Is Pinecone still down?
No, this incident was resolved 2025-09-03 14:00 UTC. For Pinecone's live state, see https://down.guide/providers/pinecone.
How long did it last?
15h 14m, from 2025-09-02 22:46 UTC to 2025-09-03 14:00 UTC, by the times Pinecone posted.
What was affected?
Pinecone named AWS us-east-1 in us, us-east-1.
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.