User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 4 min ago. Last stored result reached it in 253 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 282 ms | 0 |
| Mon 19 | 0 | 0.0 | 177 ms | 0 |
| Mon 21 | 0 | 0.0 | 281 ms | 0 |
| Mon 23 | 0 | 0.0 | 239 ms | 0 |
| Tue 01 | 0 | 0.0 | 213 ms | 0 |
| Tue 04 | 0 | 0.0 | 162 ms | 0 |
| Tue 06 | 0 | 0.0 | 241 ms | 0 |
| Tue 08 | 0 | 0.0 | 177 ms | 0 |
| Tue 10 | 0 | 0.0 | 247 ms | 0 |
| Tue 12 | 0 | 0.0 | 236 ms | 0 |
| Tue 14 | 0 | 0.0 | 329 ms | 0 |
| Tue 16 | 0 | 0.0 | 317 ms | 0 |
| Tue 19 | 0 | 0.0 | 148 ms | 0 |
| Tue 21 | 0 | 0.0 | 180 ms | 0 |
| Tue 23 | 0 | 0.0 | 256 ms | 0 |
| Wed 01 | 0 | 0.0 | 204 ms | 0 |
| Wed 04 | 0 | 0.0 | 306 ms | 0 |
| Wed 06 | 0 | 0.0 | 237 ms | 0 |
| Wed 08 | 0 | 0.0 | 279 ms | 0 |
| Wed 10 | 0 | 0.0 | 280 ms | 0 |
| Wed 13 | 0 | 0.0 | 356 ms | 0 |
| Wed 15 | 0 | 0.0 | 398 ms | 0 |
| Wed 17 | 0 | 0.0 | 340 ms | 0 |
| Wed 19 | 0 | 0.0 | 220 ms | 0 |
| Wed 21 | 0 | 0.0 | 241 ms | 0 |
| Wed 23 | 0 | 0.0 | 326 ms | 0 |
| Thu 02 | 0 | 0.0 | 294 ms | 0 |
| Thu 04 | 0 | 0.0 | 186 ms | 0 |
| Thu 06 | 0 | 0.0 | 370 ms | 0 |
| Thu 08 | 0 | 0.0 | 320 ms | 0 |
| Thu 10 | 0 | 0.0 | 354 ms | 0 |
| Thu 12 | 0 | 0.0 | 235 ms | 0 |
| Thu 14 | 0 | 0.0 | 440 ms | 0 |
| Thu 16 | 0 | 0.0 | 310 ms | 0 |
| Thu 18 | 0 | 0.0 | 217 ms | 0 |
| Thu 20 | 0 | 0.0 | 272 ms | 0 |
| Thu 22 | 0 | 0.0 | 154 ms | 0 |
| Thu 23 | 0 | 0.0 | 243 ms | 0 |
| Fri 02 | 0 | 0.0 | 318 ms | 0 |
| Fri 04 | 0 | 0.0 | 299 ms | 0 |
| Fri 06 | 0 | 0.0 | 289 ms | 0 |
| Fri 08 | 0 | 0.0 | 254 ms | 0 |
| Fri 10 | 0 | 0.0 | 202 ms | 0 |
| Fri 11 | 0 | 0.0 | 241 ms | 0 |
| Fri 13 | 0 | 0.0 | 346 ms | 0 |
| Fri 15 | 0 | 0.0 | 357 ms | 0 |
| Fri 17 | 0 | 0.0 | 303 ms | 0 |
| Fri 18 | 0 | 0.0 | 253 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Chargeblast yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Chargeblast goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Chargeblast alerts to Slack, Discord or a webhook — free.
Chargeblast is listed in our Money category and checked at chargeblast.com. Chargeblast helps ecommerce merchants prevent chargebacks, win disputes, and stop friendly fraud automatically. Trusted by Shopify and Stripe merchants.
Chargeblast publishes an official status page at status.chargeblast.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 271 ms average, 129–363 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Chargeblast incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
271 ms on average over the last 24 hours (129–363 ms).
Yes, at https://status.chargeblast.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Chargeblast here at once, the problem is on Chargeblast's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Chargeblast. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.