Sentry service status
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Live Domain Check
Is Sentry Down? Check sentry.io Status and Outages
Run a live reachability check for sentry.io. Compare the regional responses with the problem you see in Sentry.
Find Sentry help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked-
Verdict-
Response Time-
Final URL-
Regional checks
Understanding Sentry connection and service problems
Sentry event ingestion, processing, issue views and alerts may fail separately.
The checker above requests sentry.io from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Sentry action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Sentry status information and official help
Sentry help and reporting
Use the affected product/project and ingestion or alert context.
Open sentry.io
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
Where to report a Sentry problem
Use the affected product/project and ingestion or alert context.
Open Sentry help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Include these details in a Sentry report
Project/region, event ID, SDK/version, time range and response without private event payloads or keys.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Sentry.
What to check when Sentry is not working
These are troubleshooting comparisons, not claims that Sentry is currently experiencing a particular incident.
Start with the action that failed
Compare a controlled test event with the project's issue list and inspect ingestion responses.
Narrow down the affected service
Check the relevant Sentry status component and client sampling/filtering before assuming missing events were lost by the service.
Read the actual checker response
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if Sentry is down: a step-by-step workflow
- Capture the original failure. Save the exact action, error and time before refreshing. Preserve drafts and check whether a submission already completed.
- Run the sentry.io check. Compare each response, the measurement time and available locations. A repeated click can reuse a cached observation.
- Compare the relevant provider information. Open Sentry status and check whether the named service and incident time fit your error.
- Test one useful difference, then report. Compare another permitted session, network or service component using the tailored checks above. Send the result and the actual app error through the reporting route on this page.
If Sentry Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when Sentry seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open sentry.io in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Sentry issue.
3. Compare permitted network paths
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Sentry support.
Frequently asked questions about Sentry problems
Is Sentry down, or is the problem limited to one feature?
Run the sentry.io check and compare its original timestamps and responses with your actual error. Sentry event ingestion, processing, issue views and alerts may fail separately.
Where can I report a problem with Sentry?
Use the official help/reporting resource linked above. Use the affected product/project and ingestion or alert context.
What should I check first when Sentry is not working?
Compare a controlled test event with the project's issue list and inspect ingestion responses. Check the relevant Sentry status component and client sampling/filtering before assuming missing events were lost by the service.
What information helps Sentry support investigate?
Project/region, event ID, SDK/version, time range and response without private event payloads or keys.