Sentry: Ingestion delayed for spans, logs, crons in US region

What to do

Check whether you use Sentry in 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 1h 58m it lasted.
Anything that failed between 2026-07-13 00:58 UTC and 2026-07-13 02:56 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.

investigatingJul 13, 2026, 12:58 AM UTC
We are currently investigating the issue.
provider
identifiedJul 13, 2026, 1:46 AM UTC
We have identified the problem and are working to restore ingestion
provider
monitoringJul 13, 2026, 2:01 AM UTC
We have implemented a fix and are monitoring the situation. We expect ingestion to catch up in the next hour, approximately.
provider
resolvedJul 13, 2026, 2:56 AM UTC
Ingestion has caught up and alerts have been restored.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Sentry still down?

No, this incident was resolved 2026-07-13 02:56 UTC. For Sentry's live state, see https://down.guide/sentry.

How long did it last?

1h 58m, from 2026-07-13 00:58 UTC to 2026-07-13 02:56 UTC, by the times Sentry posted.

What was affected?

Sentry named in 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.