Is Chargebee down in the US?
Vendor reports no incidentWhat Chargebee reports
Chargebee reports no incident on its status page.
As of the last successful poll, 2026-11-05 17:54 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Chargebee at Nov 5, 2026, 5:48 PM UTC.
Over the last 24 hours we completed 254 checks from Ashburn and San Jose and 254 answered cleanly, 100.00% availability.
Of the 2 other regions we check Chargebee from, all 2 read checks passing right now.
Email me when Chargebee reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 5:48 PM UTC.
Chargebee from Ashburn and San Jose over the last 30 days
Over the last 30 days, Chargebee answered our Ashburn probe in 574 ms on average, and 1 check in 20 took longer than 926 ms.
Over the last 30 days, Chargebee answered our San Jose probe in 944 ms on average, and 1 check in 20 took longer than 1,672 ms.
Ranked by average response time across the 4 cities we check Chargebee from, Ashburn 1st, San Jose 3rd; Ashburn was fastest at 574 ms and Tokyo slowest at 1,498 ms.
From Ashburn and San Jose we ran 800 checks of Chargebee in 4 days, and 800 answered cleanly: 100.00% availability.
Every one of those days was clean: not one failed check.
In Ashburn local time (EST), Chargebee was slowest around 1 PM, at 738 ms on average over the last 14 days, and quickest around 6 AM, at 373 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 190 | 100.00% | 739 ms |
| Wed, Nov 4 | 254 | 100.00% | 651 ms |
| Tue, Nov 3 | 249 | 100.00% | 754 ms |
| Mon, Nov 2 | 107 | 100.00% | 897 ms |
Chargebee outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Chargebee outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Chargebee from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 101 checks |
| Tokyo | Checks passing | 100.00% of 62 checks |
Other countries we check Chargebee from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Chargebee's public endpoints. They are not user reports, and they are not Chargebee's own status page.
See Chargebee's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Chargebee has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter