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.
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 20 min ago. Last stored result reached it in 383 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 21:45 | 0 | 0.0 | 283 ms | 0 |
| 00:00 | 0 | 0.0 | 317 ms | 0 |
| 02:00 | 0 | 0.0 | 273 ms | 0 |
| 04:15 | 0 | 0.0 | 351 ms | 0 |
| 06:15 | 0 | 0.0 | 334 ms | 0 |
| 08:00 | 0 | 0.0 | 314 ms | 0 |
| 10:15 | 0 | 0.0 | 322 ms | 0 |
| 11:30 | 0 | 0.0 | 352 ms | 0 |
| 13:45 | 0 | 0.0 | 223 ms | 0 |
| 15:45 | 0 | 0.0 | 292 ms | 0 |
| 17:45 | 0 | 0.0 | 253 ms | 0 |
| 19:45 | 0 | 0.0 | 383 ms | 0 |
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.
Response time over the last 24 hours: 308 ms average, 223–383 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
308 ms on average over the last 24 hours (223–383 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.