- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu, us
- Down Index
- 30of 100
What to do
Check whether you use Sentry in eu, us. 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 8h 48m it lasted.
Anything that failed between 2026-07-06 13:30 UTC and 2026-07-06 22:18 UTC may need a replay.Subscribe to Sentry's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=sentry works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Sentry 14
- investigating
We are investigating consumers for spans, logs and metrics are not ingested
provider
- monitoring
The issue was fixed and we are now monitoring the fix
provider
- monitoring
Backlog is being consumed and we’re still monitoring recovery
provider
- monitoring
We're still consuming the backlog and monitoring the situation.
provider
- investigating
We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.
provider
- investigating
We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.
provider
- investigating
We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.
provider
- investigating
We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.
provider
- investigating
We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.
provider
- monitoring
We've taken steps to mitigate the issue in the US and we're burning our backlog and expect to be have it fully consumed in about 4 hours. We're continuing to investigate the delayed ingestion in our EU region.
provider
- monitoring
We're continuing burning our backlog in US and expect to be have it fully consumed in about 1 hour. We're continuing to investigate the delayed ingestion in our EU region.
provider
- monitoring
We're continuing burning our backlog in US and expect to be have it fully consumed within the next hour. We're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this incident.
provider
- monitoring
We're still burning the last of our backlog in US and expect to be back to normal the next hour. We're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this incident.
provider
- resolved
US ingestion is back to normal. EU ingestion is still delayed, but we are now recovering. We have created a new Statuspage incident for tracking EU, follow that for further updates: https://status.sentry.io/incidents/7tfjf5k3m0g3
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-3f43becba3
Is Sentry still down?
No, this incident was resolved 2026-07-06 22:18 UTC. For Sentry's live state, see https://down.guide/sentry.
How long did it last?
8h 48m, from 2026-07-06 13:30 UTC to 2026-07-06 22:18 UTC, by the times Sentry posted.
What was affected?
Sentry named in eu, us.
What caused it?
Sentry hasn't published a root cause. If it does, it shows here.
Where does this come from?
Sentry's official status page, https://status.sentry.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.