Our UI was unavailable between 12:01 pm - 12:06 pm UTC
Timeline · 1 update
- resolved Dec 01, 2025, 03:57 PM UTC
Between 12:01 pm - 12:06 pm UTC our UI was unavailable, we have resolved the issue and apologize for any inconvenience this caused.
Sentry had 66 outages in the last 2 years totaling 43h 39m of downtime — averaging 2.7 incidents per month.
There were 66 Sentry outages since October 11, 2025 totaling 43h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between 12:01 pm - 12:06 pm UTC our UI was unavailable, we have resolved the issue and apologize for any inconvenience this caused.
We are currently investigating delayed ingestion for Profiles
This incident has been resolved.
We are currently investigating this issue.
We have restarted the affected component and the service is now operating normally. We're continuing to monitor and investigate the root cause.
This incident has been resolved.
We are currently investigating an issue in our infrastructure that is causing degraded search performance on the issues page
We implemented a fix and are monitoring
This incident has been resolved
We're investigating increased latency and 429 responses across our APIs
A fix has been implemented and we're monitoring the results
We are continuing to monitor the situation. While recovery is in progress, some users may experience intermittent issues accessing the user interface.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We're aware of an issue on our checkout page and currently investigating.
The issue has been identified and we're deploying a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Currently we are experiencing delays in webhook sending for custom integrations in the US region.
Webhooks latency has returned to normal levels.
Ingesting and storing profiles in the US is delayed.
A fix has been implemented and all messages have been processed.
We are investigating increased ingestion latency in the US region.
We're continuing to investigate increased latency for ingestion of all event types in our US region.
The increased latency for ingestion of all events has been resolved, we're continuing to monitor.
Ingestion latency has returned to normal levels.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating elevated API latency in the US region.
We have identified the issue and put a mitigation in place. API latency has returned to normal levels.
We are currently investigating an issue where Uptime Monitors may be missing their name.
We've identified the issue and are deploying a fix.
Uptime monitor names are now always correctly displayed.
We are currently investigating delays in error ingestion in the US region.
We are experiencing high load due to upstream problems.
We are beginning to recover and process our backlog
New events are being processed promptly, and we are continuing to process backlogged events.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are investigating increased latency for span ingestion in the US region.
A fix has been made, and we're continuing to monitor the backlog
The backlog has been processed and latency is back to normal.