Is Sentry down right now?

No. Our checks are finding no problems with Sentry right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Sentry continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are API errors, 5xx error pages, no response / timing out, can't connect, webhooks not firing, can't log in, slow or laggy and website / app down. Those are the options the report button offers for Sentry, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Sentry specifically, Sentry's event ingestion pipeline, webhook delivery system, and API endpoints can fail independently. Your application may be sending events successfully while Sentry's servers are not processing them, or webhooks may be queued but not delivered. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Sentry, send a test event through Sentry's SDK in your application and check if it appears in the dashboard within 30 seconds. If the event arrives but others do not, the issue is likely with your application's error handling, not Sentry. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Sentry's side. Specifically: do not repeatedly restart your application or resend errors, as this will create duplicate events and make debugging harder once Sentry recovers. Check the Sentry status page and wait for the incident to be resolved. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Sentry publishes a machine-readable status feed, so our first check reads it directly and reports what Sentry itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.sentry.io, and it is linked further up this page. That is Sentry's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Sentry or sentry.io. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Sentry's own support, not us.