Changes / Chargebee / API Service Degradation
Chargebee: Major incident: API Service Degradation
Summary
Chargebee reported major degradation affecting API (US), with failed requests for some merchants between 11:58 UTC and 12:08 UTC. The incident started at 2026-09-29 12:35 UTC and resolved at 2026-09-29 14:35 UTC (2 h 0 min); Chargebee said services had recovered and were monitored for stability.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: API Service Degradation
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-29 12:35 UTC
Before: not present
After: 2026-09-29 14:35 UTC
Before: not present
After: API Endpoints - API (US), API (US)
Before: not present
After: Between 11:58 UTC and 12:08 UTC, we experienced a brief service interruption in the US region that resulted in failed API requests for some merchants. Services have recovered, and we are currently monitoring the systems for continued stability.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: API Service Degradation (this change) Chargebee reported major degradation affecting API (US), with failed requests for some merchants between 11:58 UTC and 12:08 UTC. The incident started at 2026-09-29 12:35 UTC and resolved at 2026-09-29 14:35 UTC (2 h 0 min); Chargebee said services had recovered and were monitored for stability. | Major incident |
All Chargebee changes → · Chargebee profile · Markdown · JSON