Vendor reports: operationalResolved · vendor status “resolved”Official status API
Issues with BugSnag Event processing times
Reported by Bugsnag · Observability & Incident · source last read 2 min ago
- Vendor start
- Aug 15, 2024, 14:14 UTC
- Vendor's clock
- Resolved
- Aug 15, 2024, 21:17 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 7 h 3 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
What is unknown
Last update in these facts: 2024-08-15 21:17 UTC · summary s1, evidence 9b82e33a54fd6d7c
Evidence (7)
- E1Bugsnag reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Issues with BugSnag Event processing times". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2024-08-15 14:14 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2024-08-15 21:17 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
Bugsnag is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Aug 15, 2024, 14:14 UTCVendor-reported startVendor time
- Aug 15, 2024, 21:17 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.