Skip to main content
Sentry

Elevated errors (EU)

Degraded Lasted 0m · started · Sentry's page

Level
confirmed
Worst impact
Degraded
Components
API
Regions
eu

What to do

  • Check whether you use Sentry API in eu. 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 0m it lasted.

    Anything that failed between 2026-06-02 07:45 UTC and 2026-06-02 07:45 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 1

  1. resolved

    Between 06:00-07:00 UTC, we saw increased numbers of API errors in the EU region. The largest impact was between 06:46-07:00. We've implemented a fix and we're no longer seeing elevated errors.

    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-f3b678ae98

Is Sentry still down?

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

How long did it last?

0m, from 2026-06-02 07:45 UTC to 2026-06-02 07:45 UTC, by the times Sentry posted.

What was affected?

Sentry named API in eu.

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.