User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
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 2 hr ago. Last stored result reached it in 292 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 286 ms | 0 |
| Mon 14 | 0 | 0.0 | 370 ms | 0 |
| Mon 16 | 0 | 0.0 | 329 ms | 0 |
| Mon 18 | 0 | 0.0 | 273 ms | 0 |
| Mon 21 | 0 | 0.0 | 403 ms | 0 |
| Mon 23 | 0 | 0.0 | 314 ms | 0 |
| Tue 01 | 0 | 0.0 | 321 ms | 0 |
| Tue 03 | 0 | 0.0 | 382 ms | 0 |
| Tue 05 | 0 | 0.0 | 294 ms | 0 |
| Tue 07 | 0 | 0.0 | 327 ms | 0 |
| Tue 09 | 0 | 0.0 | 355 ms | 0 |
| Tue 11 | 0 | 0.0 | 402 ms | 0 |
| Tue 14 | 0 | 0.0 | 286 ms | 0 |
| Tue 16 | 0 | 0.0 | 326 ms | 0 |
| Tue 18 | 0 | 0.0 | 278 ms | 0 |
| Tue 20 | 0 | 0.0 | 358 ms | 0 |
| Tue 23 | 0 | 0.0 | 497 ms | 0 |
| Wed 01 | 0 | 0.0 | 240 ms | 0 |
| Wed 03 | 0 | 0.0 | 455 ms | 0 |
| Wed 05 | 0 | 0.0 | 364 ms | 0 |
| Wed 08 | 0 | 0.0 | 325 ms | 0 |
| Wed 10 | 0 | 0.0 | 323 ms | 0 |
| Wed 12 | 0 | 0.0 | 200 ms | 0 |
| Wed 14 | 0 | 0.0 | 279 ms | 0 |
| Wed 16 | 0 | 0.0 | 386 ms | 0 |
| Wed 19 | 0 | 0.0 | 222 ms | 0 |
| Wed 21 | 0 | 0.0 | 296 ms | 0 |
| Wed 23 | 0 | 0.0 | 319 ms | 0 |
| Thu 01 | 0 | 0.0 | 191 ms | 0 |
| Thu 03 | 0 | 0.0 | 385 ms | 0 |
| Thu 05 | 0 | 0.0 | 288 ms | 0 |
| Thu 07 | 0 | 0.0 | 438 ms | 0 |
| Thu 09 | 0 | 0.0 | 351 ms | 0 |
| Thu 11 | 0 | 0.0 | 328 ms | 0 |
| Thu 13 | 0 | 0.0 | 359 ms | 0 |
| Thu 15 | 0 | 0.0 | 337 ms | 0 |
| Thu 17 | 0 | 0.0 | 379 ms | 0 |
| Thu 19 | 0 | 0.0 | 347 ms | 0 |
| Thu 21 | 0 | 0.0 | 283 ms | 0 |
| Fri 00 | 0 | 0.0 | 317 ms | 0 |
| Fri 02 | 0 | 0.0 | 273 ms | 0 |
| Fri 04 | 0 | 0.0 | 351 ms | 0 |
| Fri 06 | 0 | 0.0 | 334 ms | 0 |
| Fri 08 | 0 | 0.0 | 314 ms | 0 |
| Fri 10 | 0 | 0.0 | 322 ms | 0 |
| Fri 11 | 0 | 0.0 | 352 ms | 0 |
| Fri 13 | 0 | 0.0 | 223 ms | 0 |
| Fri 15 | 0 | 0.0 | 292 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 ZBD API 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 ZBD API goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ZBD API alerts to Slack, Discord or a webhook — free.
ZBD API, at zbdpay.com, is one of the Gaming services we monitor. ZBD is the money layer for games, the licensed financial infrastructure that turns money movement into a driver of engagement, revenue, and loyalty.
ZBD API publishes an official status page at status.zbdpay.com; when we can read it, its incident level is folded into the status shown here.
Common problems for gaming services: login and matchmaking failures, server disconnects, and store or download 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: 320 ms average, 223–402 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public ZBD API incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
320 ms on average over the last 24 hours (223–402 ms).
Yes, at https://status.zbdpay.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For gaming services, watch for login and matchmaking failures, server disconnects, and store or download errors. If many people report ZBD API here at once, the problem is on ZBD API'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 ZBD API. 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.