Compare the status, incidents stats and history between Bugsnag and PagerDuty
Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.
We are currently experiencing an outage. The dashboard may not be accessible and there may be delays to event processing. We are investigating this issue.
Some mapping files uploaded between 10 and 11 AM UTC may not be available for the symbolication of events. Resolution is underway to make these available and is complete for Proguard, .so mappings,...
We are currently experiencing an outage on the BugSnag dashboard, and there may be delays to event processing. We are investigating this.
We are investigating an incident where some PagerDuty customers in the US Service Region may be experiencing issues with Incident Workflows. Impacted customers may see delays in triggering incident...
We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.
We are continuing to investigate an incident where some PagerDuty customers are experiencing issues with the Slack integration. We will provide further updates within 30 minutes.
How much time you'll save your team, by having the outages information close to them?
14-day free trial · No credit card required · Cancel anytime