Resolved incident
API Service Degradation
Chargebee · Minor · Started
- Duration
- 1h 38m
- Severity
- Minor
- Status
- Resolved
Summary
Minor · Resolved
We have identified that the issue was due to the AWS platform, leading to increased API timeouts. AWS has confirmed that the services have fully recovered. We apologize for any inconvenience caused.
Event timeline
How this incident unfolded, from the official status page.
Identified
Chargebee
We experienced a brief interruption to our API service due to an internal server issue, and we are analysing the impact.
Monitoring
Chargebee
API timeouts were observed in the US region during two intervals: 17:44–17:54 UTC and 18:00–18:02 UTC. The services have fully recovered, and we are continuing to monitor system reliability.
Resolved
Chargebee
We have identified that the issue was due to the AWS platform, leading to increased API timeouts. AWS has confirmed that the services have fully recovered. We apologize for any inconvenience caused.