Is Chime down in the US?
Vendor reports no incidentWhat Chime reports
Chime reports no incident on its status page.
As of the last successful poll, 2026-11-05 17:17 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 Chime at Nov 5, 2026, 4:58 PM UTC.
Over the last 24 hours we completed 85 checks from Ashburn and San Jose and 85 answered cleanly, 100.00% availability.
We check Chime from no region outside the US, so there is nothing here to compare it against.
Email me when Chime 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, 4:58 PM UTC.
Chime from Ashburn and San Jose over the last 30 days
Over the last 30 days, Chime answered our Ashburn probe in 596 ms on average, and 1 check in 20 took longer than 1,014 ms.
Over the last 30 days, Chime answered our San Jose probe in 710 ms on average, and 1 check in 20 took longer than 1,031 ms.
Ranked by average response time across the 2 cities we check Chime from, Ashburn 1st, San Jose 2nd; Ashburn was fastest at 596 ms and San Jose slowest at 710 ms.
From Ashburn and San Jose we ran 2,826 checks of Chime in 30 days, and 2,806 answered cleanly: 99.29% availability.
10 of the 30 days had at least one failed check. The weakest was Oct 21 (UTC), at 93.75% across 96 checks.
In Ashburn local time (EST), Chime was slowest around 5 AM, at 1,097 ms on average over the last 14 days, and quickest around 3 PM, at 598 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 61 | 100.00% | 1,241 ms |
| Wed, Nov 4 | 86 | 100.00% | 998 ms |
| Tue, Nov 3 | 84 | 100.00% | 941 ms |
| Mon, Nov 2 | 92 | 100.00% | 1,196 ms |
| Sun, Nov 1 | 95 | 100.00% | 1,184 ms |
| Sat, Oct 31 | 96 | 100.00% | 985 ms |
| Fri, Oct 30 | 96 | 100.00% | 1,060 ms |
| Thu, Oct 29 | 97 | 98.96% | 938 ms |
| Wed, Oct 28 | 96 | 98.95% | 987 ms |
| Tue, Oct 27 | 96 | 100.00% | 851 ms |
| Mon, Oct 26 | 98 | 97.95% | 845 ms |
| Sun, Oct 25 | 96 | 100.00% | 734 ms |
| Sat, Oct 24 | 96 | 100.00% | 679 ms |
| Fri, Oct 23 | 96 | 100.00% | 594 ms |
Chime outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Chime outage in the last 90 days.
How the other regions read right now
We check Chime from no region outside the US, so there is nothing here to compare it against.
Chime serves United States customers, so we check it from our US regions only.
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Chime's public endpoints. They are not user reports, and they are not Chime's own status page.
See Chime's full check readings, the 90-day history by region, or the outage tracker methodology.
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