Changes / Chargebee / API Service Degradation
Chargebee: Major incident: API Service Degradation
Summary
Chargebee reported major API degradation affecting some US-region users, with intermittent failures between 12:54 UTC and 12:57 UTC. The incident record started at 2026-09-02 13:28 UTC and was resolved at 2026-09-02 13:35 UTC, lasting 7 min; services had recovered by the initial update 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-02 13:28 UTC
Before: not present
After: 2026-09-02 13:35 UTC
Before: not present
After: API Endpoints - API (US), API (US)
Before: not present
After: Between 12:54 UTC and 12:57 UTC, some users may have experienced intermittent API failures in the US region. The services have recovered, and we are monitoring the situation for 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 API degradation affecting some US-region users, with intermittent failures between 12:54 UTC and 12:57 UTC. The incident record started at 2026-09-02 13:28 UTC and was resolved at 2026-09-02 13:35 UTC, lasting 7 min; services had recovered by the initial update and were monitored for stability. | Major incident |
All Chargebee changes → · Chargebee profile · Markdown · JSON