Issues with the BugSnag Error Reporting API
This incident has been resolved.
Home
/
Status
/
Service
Error monitoring and real user monitoring for mobile apps.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 20m ago
6
Components
0
Active incidents
0
Maintenance
100%
90d uptime
Issues with the BugSnag Error Reporting API
Jan 22, 4:54 PM
Normalized official status-page data for incidents, maintenance, components, and history.
100%
Known uptime
1 known history days
6
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
1
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
BugSnag Dashboard
Operational
BugSnag Data Access API
Operational
BugSnag Error Reporting API
Operational
BugSnag OTLP Trace Reporting API
Operational
BugSnag Sessions API
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
0
outage days
0
maintenance days
89
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Degraded performance between 17:15 and 17:40 UTC which included a backlog in Unity event processing. Customers may experience delays in integration processing (e.g. webhooks) between 17:15 and 18:02 UTC.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
Uptimus tracks the official Bugsnag status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.bugsnag.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 6 of 6 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
BugSnag Dashboard The main BugSnag dashboard at app.bugsnag.com | Operational | Component | Not recorded |
BugSnag Error Reporting API The endpoint which receives crashes/errors from your applications, hosted on notify.bugsnag.com | Operational | Component | Not recorded |
BugSnag Sessions API The endpoint which receives sessions from your applications, hosted on sessions.bugsnag.com | Operational | Component | Not recorded |
BugSnag Upload API The api hosted on upload.bugsnag.com | Operational | Component | Not recorded |
BugSnag Data Access API The read/write JSON api hosted on api.bugsnag.com | Operational | Component | Not recorded |
BugSnag OTLP Trace Reporting API The endpoint which receives OTLP traces from your applications, hosted on otlp.bugsnag.com. | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Bugsnag is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.