Official incident history

  1. Sentry: dashboard, outage or errors

    Provider's original title: US issues feed throwing intermittent errors

    Started: · Duration: 52 min
    Provider updates (4)
    1. Investigating “We're investigating an intermittent problem causing issues queries to intermittently return errors.”
    2. Identified “We have identified the issue. We are actively rolling out a fix.”
    3. Monitoring “We have deployed a fix and are monitoring for any issues.”
    4. Resolved “The incident is now resolved.”
    Resolved
  2. Started: · Duration: 43 min
    Provider updates (2)
    1. Investigating “Since 21:37 UTC on November 10, some account emails from Sentry have not been delivered. This includes email address verification, adding new email addresses, and emails sent when you create an account or organization. Organization invites and password reset emails may also be affected. Alert and notification emails are being delivered as normal. We're investigating and working on a fix. Emails…”
    2. Resolved “This incident was caused by an infrastructure configuration change, which we reverted at 08:15 UTC on November 11. Account emails have been delivered normally since then. Emails that failed between 21:37 UTC on November 10 and 08:15 UTC on November 11 won't be re-sent automatically. If you were waiting for an email verification, a new email address confirmation, an organization invite or a passw…”
    Resolved
  3. Sentry: EU Replay Ingestion, increased latency

    Provider's original title: EU region replay ingestion latency

    Started: · Duration: 48 min
    Provider updates (2)
    1. Identified “We have identified an issue causing ingestion latency for replay events in our EU region and are working on a fix.”
    2. Resolved “We have resolved the issue causing ingestion latency for replay events in our EU region.”
    Resolved
  4. Sentry: US Error Ingestion, US Transaction Ingestion, increased latency

    Provider's original title: Ingestion delays across all data

    Started: · Duration: 70 min
    Provider updates (2)
    1. Monitoring “We are monitoring an issue involving increased ingestion latency across all our datasets.”
    2. Resolved “The issue causing ingestion delays in our US region has been resolved, all data has been backfilled and latency has returned to normal.”
    Resolved
  5. Sentry: US Transaction Ingestion, US Span Ingestion, increased latency

    Provider's original title: Delays in spans and transactions processing

    Started: · Duration: 105 min
    Provider updates (3)
    1. Investigating “We are investigating an incident affecting ingestion of spans and transactions. No data has been lost.”
    2. Identified “We have identified the issue. We are working to roll out a fix.”
    3. Resolved “The issue has been resolved. Spans and transaction ingestion in the US is back to normal and all delayed data has been processed. No data was lost.”
    Resolved
  6. Sentry: API, dashboard, outage or errors

    Provider's original title: Sentry.io dashboard and API is down

    Started: · Duration: 93 min
    Provider updates (3)
    1. Investigating “We are investigating the issue. This is affecting both US and EU customers.”
    2. Monitoring “The issue has been mitigated. Dashboard and API are operational.”
    3. Resolved “The issue has been resolved.”
    Resolved
  7. Sentry: API, dashboard, outage or errors

    Provider's original title: Sentry dashboard is down

    Started: · Duration: 261 min
    Provider updates (3)
    1. Investigating “We are investigating the issue, will update when we know more.”
    2. Monitoring “The issue is mitigated, but we are continuing to monitor the situation.”
    3. Resolved “We have deployed a fix and the incident is resolved.”
    Resolved
  8. Sentry: Slack, Integration Pipeline, increased latency

    Provider's original title: Increased latency processing integration webhooks

    Started: · Duration: 21 min
    Provider updates (2)
    1. Investigating “We are working on mitigating an incident that affects external integrations such as GitHub, Slack, and Autofix PRs. No data is being lost.”
    2. Resolved “We are working on mitigating an incident that affects external integrations such as GitHub, Slack, and Autofix PRs. No data is being lost.”
    Resolved
  9. Sentry: outage or errors

    Provider's original title: Sentry.io not loading in US region

    Started: · Duration: 60 min
    Provider updates (3)
    1. Investigating “We are currently investigating an issue affecting US Sentry region”
    2. Monitoring “We have identified the problem, and addressed the cause of the outage. We will continue monitoring the fix”
    3. Resolved “Native events ingestion has caught up, everything should be operational now”
    Resolved
  10. Sentry: outage or errors

    Provider's original title: Sentry.io not loading

    Started: · Duration: 198 min
    Provider updates (3)
    1. Investigating “Users are experiencing issues loading the Sentry dashboard. We are investigating the problem.”
    2. Monitoring “We have put a better mitigation in place while we work on a fix. Things continue to be operational and we are monitoring the situation.”
    3. Resolved “We have a mitigation in place that should prevent this from occurring again in the short term while we continue to work on a proper fix. We are going to close the Statuspage incident for now, but will reopen it if things become unstable again.”
    Resolved
  11. Sentry: outage or errors

    Provider's original title: Sentry is down

    Started: · Duration: 53 min
    Provider updates (3)
    1. Investigating “Sentry.io is taking a long time to load and ingestion may be impacted. We will update as we know more.”
    2. Monitoring “We have identified and addressed the cause of the outage. Things are moving again and we are burning through ingestion backlogs. We will update the statuspage again as things progress.”
    3. Resolved “Backlogs have been processed and we are back to normal.”
    Resolved
  12. Started: · Duration: 154 min
    Provider updates (3)
    1. Identified “In the EU we've identified an issue with ingestion into EAP and are working towards a fix.”
    2. Monitoring “In the EU we've identified an issue with ingestion into EAP and have implemented a fix. Waiting on ingestion lag burn down.”
    3. Resolved “The issue with EAP ingestion in EU has been resolved.”
    Resolved
  13. Sentry: dashboard, outage or errors

    Provider's original title: Sentry dashboard down

    Started: · Duration: 42 min
    Provider updates (4)
    1. Investigating “We are investigating an issue impacting our dashboard in both US and EU regions”
    2. Identified “We have identified the issue and are working on a fix”
    3. Monitoring “We have deployed a fix and are things are recovering. We are continuing to monitor the situation.”
    4. Resolved “Dashboard is back to operational.”
    Resolved
  14. Sentry: increased latency

    Provider's original title: Delayed ingestion of errors in EU

    Started: · Duration: 200 min
    Provider updates (4)
    1. Investigating “We are currently investigating an issue that causes new errors to be delayed in the EU region.”
    2. Monitoring “We are processing real-time data again and are working on burning our backlog.”
    3. Identified “We have identified a networking issue with an upstream provider and are working on mitigations.”
    4. Resolved “We are processing real-time data for all data types again.”
    Resolved
  15. Sentry: increased latency

    Provider's original title: Delays in spans ingestion

    Started: · Duration: 41 min
    Provider updates (2)
    1. Investigating “We are currently investigating an issue affecting spans ingestion in the EU region”
    2. Resolved “We have identified a networking issue with an upstream provider and are working on mitigations.”
    Resolved
  16. Sentry: increased latency

    Provider's original title: Ingestion is delayed in US

    Started: · Duration: 57 min
    Provider updates (2)
    1. Investigating “We are investigating degraded ingestion in US.”
    2. Resolved “Ingestion is now operating normally.”
    Resolved
  17. Sentry: degraded performance

    Provider's original title: Sentry.io elevated number of 500 errors

    Started: · Duration: 61 min
    Provider updates (3)
    1. Identified “During migration to new control silo region we started to observe increased number of 500 errors. Migration procedure was rolled back.”
    2. Monitoring “Issue were identified and fixes were applied. We continue to monitor situation”
    3. Resolved “Issue fully resolved”
    Resolved
  18. Sentry: degraded performance

    Provider's original title: Span ingestion is degraded in US

    Started: · Duration: 374 min
    Provider updates (3)
    1. Investigating “We are experiencing slow ingestion for spans in US”
    2. Monitoring “A fix has been implemented, and latency is coming down.”
    3. Resolved “Spans ingestion is now operating normally.”
    Resolved
  19. Started: · Duration: 200 min
    Provider updates (3)
    1. Investigating “We are currently investigating what's going on and why requests timing out”
    2. Monitoring “We identified the issue and rolled out a configuration change”
    3. Resolved “This incident has been resolved.”
    Resolved
  20. Started: · Duration: 132 min
    Provider updates (5)
    1. Investigating “we are investigating a failure in our infrastructure that is delaying ingestion”
    2. Monitoring “The fix has been deployed and our ingestion backlogs are recovering”
    3. Investigating “API is experiencing issues”
    4. Monitoring “Our systems are recovering from an ingestion backlog”
    5. Resolved “This incident has been resolved.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
Sentry Status ↗ · All Systems Operational · Nov 18, 10:26 PM UTC

Why this assessment

  • Provider reports no active incident.

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official2 min agoYes, recent

Technical details

Affected components (provider)

The provider lists no degraded components.

Official status page ↗