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 66 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 90 ms | 0 |
| Tue 04 | 0 | 0.0 | 159 ms | 0 |
| Tue 06 | 0 | 0.0 | 1054 ms | 0 |
| Tue 08 | 0 | 0.0 | 632 ms | 0 |
| Tue 10 | 0 | 0.0 | 595 ms | 0 |
| Tue 12 | 0 | 0.0 | 71 ms | 0 |
| Tue 14 | 0 | 0.0 | 699 ms | 0 |
| Tue 17 | 0 | 0.0 | 992 ms | 0 |
| Tue 19 | 0 | 0.0 | 1074 ms | 0 |
| Tue 21 | 0 | 0.0 | 644 ms | 0 |
| Tue 23 | 0 | 0.0 | 96 ms | 0 |
| Wed 02 | 0 | 0.0 | 880 ms | 0 |
| Wed 04 | 0 | 0.0 | 707 ms | 0 |
| Wed 06 | 0 | 0.0 | 1252 ms | 0 |
| Wed 08 | 0 | 0.0 | 1005 ms | 0 |
| Wed 11 | 0 | 0.0 | 89 ms | 0 |
| Wed 13 | 0 | 0.0 | 51 ms | 0 |
| Wed 15 | 0 | 0.0 | 635 ms | 0 |
| Wed 17 | 0 | 0.0 | 905 ms | 0 |
| Wed 19 | 0 | 0.0 | 655 ms | 0 |
| Wed 21 | 0 | 0.0 | 262 ms | 0 |
| Thu 00 | 0 | 0.0 | 1239 ms | 0 |
| Thu 02 | 0 | 0.0 | 2669 ms | 0 |
| Thu 04 | 0 | 0.0 | 59 ms | 0 |
| Thu 06 | 0 | 0.0 | 1051 ms | 0 |
| Thu 08 | 0 | 0.0 | 71 ms | 0 |
| Thu 10 | 0 | 0.0 | 950 ms | 0 |
| Thu 12 | 0 | 0.0 | 44 ms | 0 |
| Thu 14 | 0 | 0.0 | 40 ms | 0 |
| Thu 16 | 0 | 0.0 | 1059 ms | 0 |
| Thu 18 | 0 | 0.0 | 65 ms | 0 |
| Thu 20 | 0 | 0.0 | 446 ms | 0 |
| Thu 22 | 0 | 0.0 | 1383 ms | 0 |
| Fri 00 | 0 | 0.0 | 71 ms | 0 |
| Fri 03 | 0 | 0.0 | 75 ms | 0 |
| Fri 05 | 0 | 0.0 | 56 ms | 0 |
| Fri 07 | 0 | 0.0 | 1286 ms | 0 |
| Fri 09 | 0 | 0.0 | 68 ms | 0 |
| Fri 10 | 0 | 0.0 | 42 ms | 0 |
| Fri 12 | 0 | 0.0 | 49 ms | 0 |
| Fri 14 | 0 | 0.0 | 891 ms | 0 |
| Fri 16 | 0 | 0.0 | 1994 ms | 0 |
| Fri 18 | 0 | 0.0 | 1149 ms | 0 |
| Fri 20 | 0 | 0.0 | 1465 ms | 0 |
| Fri 22 | 0 | 0.0 | 988 ms | 0 |
| Sat 00 | 0 | 0.0 | 79 ms | 0 |
| Sat 01 | 0 | 0.0 | 855 ms | 0 |
| Sat 02 | 0 | 0.0 | 66 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for serp.co 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 serp.co goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send serp.co alerts to Slack, Discord or a webhook — free.
We track serp.co (serp.co) as part of the Gaming group. SERP builds everyday software: Keybumps for Mac, Zenbu Japanese for iPhone, and free tools, games, and checklists for everyone.
serp.co publishes an official status page at status.serp.co; when we can read it, its incident level is folded into the status shown here.
Typical issues with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 631 ms average, 41–1994 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 serp.co incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
631 ms on average over the last 24 hours (41–1994 ms).
Yes, at https://status.serp.co.
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 serp.co here at once, the problem is on serp.co'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 serp.co. 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.