Chargebee: Authentication Issues For APAC Customers
Timeline of updates
- resolved
We identified that the incident impacting APAC users was caused by a network connectivity issue specific to this region. The issue affected traffic from certain end-user networks in the Asia Pacific region when accessing services hosted in the US-EAST-1 AWS region. Users in other regions were not affected by this disruption. The root cause was traced to a network-level issue within AWS’s infrastructure, which impacted connectivity for APAC users. As of 04:30 UTC, the issue has been resolved, and there are no further signs of latency or dropped requests. The incident is now considered resolved. If you have any additional concerns or need further assistance, please contact our support team.
From Chargebee’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.chargebee.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Chargebee, started 2024-09-10 04:10 UTC, resolved after 1.1 h, 1 update(s).
- Title
- Authentication Issues For APAC Customers
- Vendor
- Chargebee
- Date
- URL
- https://rewindex.com/company/chargebee/incidents/jkrmps1zz1r4
Chargebee profileRecent Chargebee incidentsAll outages on September 10, 2024Chargebee in September 2024MarkdownJSON