Compare the status, incidents stats and history between logz.io 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 have detected an issue that may affect our AWS ca-central-1 Log Ingestion service, and we are working to identify the cause and take the appropriate steps to remediate it.
We have detected an issue that may affect our [Region & Service] service, and we are working to identify the cause and take the appropriate steps to remediate it.
The issue has been identified and a fix is being implemented.
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 monitor improvement in an incident where impacted customers would have experienced a delay in applying incident workflows with a conditional trigger. We expect systems to conti...
We are seeing signs of recovery for an incident affecting the conditional incident workflow for PagerDuty customers in the US Service Region. Impacted customers may still see delays with their work...
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