Live / Chargebee / Incident
Chargebee: API Service Degradation
Chargebee · chargebee.comMinor incidentResolved2026-11-15 10:10 UTC
Public — what happened
Summary
Chargebee reported a minor incident it called an API service degradation, which involved on-and-off failures of its API in the US region. The problem began at 08:48 UTC on 2026-11-15. The company said services recovered and that it was watching them to make sure they stayed stable, and the incident was marked resolved at 10:10 UTC. No cause was given in the text provided.
Affected
API (US)
Timeline
- Started — 2026-11-15 08:48 UTC
- Monitoring — 2026-11-15 08:48 UTC
- Resolved — 2026-11-15 10:10 UTC · 1h 23m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Chargebee against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Chargebee: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Chargebee report →
More from Chargebee
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.