Compare the status, incidents stats and history between logz.io and Bugsnag
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 currently investigating issues with broken Slack Integration buttons for updating error statuses.
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,...
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