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 some of our customers, 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 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.
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 monitoring improvement in an incident with a subset of API keys in all Service Regions, where API keys created by deleted users were no longer active. We have deployed a fix, and we expect s...
We are monitoring improvement in an incident with Incident Workflow conditional triggers, Incident Roles, and Custom Fields being set from Event Orchestration. We have deployed a fix, observed that...
14-day free trial · No credit card required · No code required