Skip to main content
Sentry

Issues performance is degraded in the US

Degraded Lasted 4h 19m · started · Sentry's page

Level
confirmed
Worst impact
Degraded
Regions
us

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 4h 19m it lasted.

    Anything that failed between 2026-08-26 16:17 UTC and 2026-08-26 20:36 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 5

  1. investigating

    We are experiencing slower page loads and API responses due to a database issue in us

    provider

  2. identified

    We have identified a potential cause of excess traffic and are working on a fix.

    provider

  3. monitoring

    We have put a fix into place and are monitoring the situation

    provider

  4. monitoring

    We have put a fix into place and are monitoring the situation

    provider

  5. resolved

    The issue 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-1609e37bd3

Is Sentry still down?

No, this incident was resolved 2026-08-26 20:36 UTC. For Sentry's live state, see https://down.guide/sentry.

How long did it last?

4h 19m, from 2026-08-26 16:17 UTC to 2026-08-26 20:36 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.