Skip to main content
Vendor reliability

Vendor record

Sentry

Vendor reports Operational

Checked

Front door check counts and Sentry’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Sentry endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,854 of 2,855 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    24 more checks gave no clear answer and are not counted.

    Endpoint checked
    sentry.io
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Sentry product, region or your app worked.

How we count front door checks

Sentry says

Incident posts from Sentry’s status page, with its titles, impact levels and times. They say what Sentry chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

1

incidents Sentry posted, last 7 days

All vendors’ incidents

Most recent records · all dates

  • Ingestion Halted for EAP data in EU

    Major

    Started, per Sentry

    Closed in our record(2h 43m)

    Sentry’s post
  • Sentry dashboard down

    Critical

    Started, per Sentry

    Closed in our record(47m)

    Sentry’s post
  • Delays in spans ingestion

    Major

    Started, per Sentry

    Closed in our record(43m)

    Sentry’s post
  • Delayed ingestion of errors in EU

    Critical

    Started, per Sentry

    Closed in our record(3h 23m)

    Sentry’s post
  • Ingestion is delayed in US

    Minor

    Started, per Sentry

    Closed in our record(1h 1m)

    Sentry’s post
15 older records
  • Sentry.io elevated number of 500 errors

    Minor

    Started, per Sentry

    Closed in our record(1h 9m)

    Sentry’s post
  • Span ingestion is degraded in US

    Minor

    Started, per Sentry

    Closed in our record(6h 14m)

    Sentry’s post
  • Sentry requests timing out / 504's

    Major

    Started, per Sentry

    Closed in our record(3h 28m)

    Sentry’s post
  • Ingestion backlog

    Minor

    Started, per Sentry

    Closed in our record(2h 23m)

    Sentry’s post
  • sentry.io is not available

    Major

    Started, per Sentry

    Closed in our record(6h 26m)

    Sentry’s post
  • Issues performance is degraded in the US

    Minor

    Started, per Sentry

    Closed in our record(4h 22m)

    Sentry’s post
  • Errors alerting degraded in US region

    Minor

    Started, per Sentry

    Closed in our record(3h 2m)

    Sentry’s post
  • gocd deployment pipelines down

    Not specified

    Started, per Sentry

    Closed in our record(16m)

    Sentry’s post
  • Alert backlogs in US

    Minor

    Started, per Sentry

    Closed in our record(47m)

    Sentry’s post
  • Span & Transaction ingestion delayed in DE

    Major

    Started, per Sentry

    Closed in our record(4h 43m)

    Sentry’s post
  • Error ingestion delays in US

    Major

    Started, per Sentry

    Closed in our record(56m)

    Sentry’s post
  • Sentry API timeouts (US)

    Minor

    Started, per Sentry

    Closed in our record(1h 31m)

    Sentry’s post
  • Delayed Error ingestion in our US region

    Major

    Started, per Sentry

    Closed in our record(3h 4m)

    Sentry’s post
  • Spans, crons, logs ingestion delayed in US region

    Critical

    Started, per Sentry

    Closed in our record(49m)

    Sentry’s post
  • Delayed Error ingestion in our US region

    Major

    Started, per Sentry

    Closed in our record(2h 31m)

    Sentry’s post

Your code, your dependencies

See which of your code paths call Sentry

Connect GitHub or GitLab to find where your public or private repository uses Sentry. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Sentry status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · SentryStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/sentry?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Sentry status badge"></iframe>

Frequently Asked Questions

Is Sentry currently down?

Sentry's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Sentry last have an outage?

The most recent closed incident record began 2 days ago and spans 2h 43m. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Sentry?

No. CheckUpstream checks Sentry’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Sentry in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Sentry?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.