User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
pubg.com · Gaming
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests pubg.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 622 ms · 3 min ago.
No status feed
PUBG does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 723 ms | 0 |
| 11:45 | 0 | 0.0 | 183 ms | 0 |
| 12:00 | 0 | 0.0 | 561 ms | 0 |
| 12:15 | 0 | 0.0 | 582 ms | 0 |
| 12:30 | 0 | 0.0 | 356 ms | 0 |
| 12:45 | 0 | 0.0 | 456 ms | 0 |
| 13:00 | 0 | 0.0 | 349 ms | 0 |
| 13:15 | 0 | 0.0 | 858 ms | 0 |
| 13:30 | 0 | 0.0 | 344 ms | 0 |
| 13:45 | 0 | 0.0 | 613 ms | 0 |
| 14:00 | 0 | 0.0 | 675 ms | 0 |
| 14:15 | 0 | 0.0 | 218 ms | 0 |
| 14:30 | 0 | 0.0 | 436 ms | 0 |
| 14:45 | 0 | 0.0 | 161 ms | 0 |
| 15:00 | 0 | 0.0 | 148 ms | 0 |
| 15:15 | 0 | 0.0 | 131 ms | 0 |
| 15:30 | 0 | 0.0 | 454 ms | 0 |
| 15:45 | 0 | 0.0 | 330 ms | 0 |
| 16:00 | 0 | 0.0 | 197 ms | 0 |
| 16:15 | 0 | 0.0 | 80 ms | 0 |
| 16:30 | 0 | 0.0 | 655 ms | 0 |
| 16:45 | 0 | 0.0 | 552 ms | 0 |
| 17:00 | 0 | 0.0 | 283 ms | 0 |
| 17:15 | 0 | 0.0 | 829 ms | 0 |
| 17:30 | 0 | 0.0 | 475 ms | 0 |
| 17:45 | 0 | 0.0 | 287 ms | 0 |
| 18:00 | 0 | 0.0 | 713 ms | 0 |
| 18:15 | 0 | 0.0 | 549 ms | 0 |
| 18:30 | 0 | 0.0 | 341 ms | 0 |
| 18:45 | 0 | 0.0 | 696 ms | 0 |
| 19:00 | 0 | 0.0 | 176 ms | 0 |
| 19:15 | 0 | 0.0 | 340 ms | 0 |
| 19:30 | 0 | 0.0 | 421 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for PUBG 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 PUBG goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Checks are succeeding and user reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.