Bugsnag vs. logz.io

Compare the status, incidents stats and history between Bugsnag 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.

Bugsnag

Bugsnag current official status is Operational

Statistics

1
Incidents in the last 7 days
1
Incidents in the last 30 days
1
Incidents in the last 90 days

Latest incidents

Resolved Delays in Macho event processing

The issue has been identified and a fix is being implemented.

4 days ago Official incident report
Resolved Macho Event processing delays

We are currently investigating this issue.

3 months ago Official incident report
Resolved Event processing delays

As of 19:49 UTC, we are currently experiencing issues processing received events so there may be a delay before error reports appear in the BugSnag dashboard. We’re still investigating the root ca...

4 months ago Official incident report

Components

Bugsnag Error Reporting API
OK
Bugsnag Sessions API
OK
Bugsnag Data Access API
OK
Bugsnag Upload API
OK
Bugsnag Dashboard
OK

logz.io

logz.io current official status is Operational

Statistics

0
Incidents in the last 7 days
1
Incidents in the last 30 days
4
Incidents in the last 90 days

Latest incidents

Resolved Lag on US-East-1 is affecting some accounts

The issue causing lag on US-East-1 has been Identified and our team is working on Fixing it

19 days ago Official incident report
Resolved AWS us-east-1 - Discovery and Explore Page - Outage - for a small number of accounts

We are currently Investigating an issue that is causing log data to not load in the Discovery and Explore Page

about 1 month ago Official incident report
Resolved Lag on Eu-Central-1 for small number of accounts

We have identified the cause of the issue that affected our Log Ingestion service. Our engineering team is working on getting this resolved as soon as possible

2 months ago Official incident report

Components

AWS London (eu-west-2)
OK
Azure Netherlands (West Europe)
OK
AWS N. Virginia (us-east-1)
OK
AWS Frankfurt (eu-central-1)
OK
AWS Canada (ca-central-1)
OK
AWS Sydney (ap-southeast-2)
OK
Azure Washington (West US 2)
OK

Never again lose time looking in the wrong place

Start Monitoring in 5 minutes

14-day free trial · No credit card required · No code required