Compare the status, incidents stats and history between Airbrake and logz.io
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.
Our alerts notifications have been disabled. Digests and other notification types (like Slack) are unaffected. We are working with our email service provider to reenable our alerts domain and will ...
We have identified an issue with delivering email alerts. We are investigating the cause of the disruption and will report more as we gather more info. Errors are still being recorded and are being...
We have identified an issue affecting a certain subset of customers and are currently working on remediation. You may notice a delay in Error processing. We'll keep this issue updated. Please reach...
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.
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