User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Gaming
Is NeoDB down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → neodb.social—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 214 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 934 ms | 0 |
| Mon 23 | 0 | 0.0 | 121 ms | 0 |
| Tue 01 | 0 | 0.0 | 134 ms | 0 |
| Tue 03 | 0 | 0.0 | 313 ms | 0 |
| Tue 05 | 0 | 0.0 | 122 ms | 0 |
| Tue 08 | 0 | 0.0 | 361 ms | 0 |
| Tue 10 | 0 | 0.0 | 114 ms | 0 |
| Tue 12 | 0 | 0.0 | 107 ms | 0 |
| Tue 14 | 0 | 0.0 | 127 ms | 0 |
| Tue 16 | 0 | 0.0 | 229 ms | 0 |
| Tue 19 | 0 | 0.0 | 198 ms | 0 |
| Tue 21 | 0 | 0.0 | 137 ms | 0 |
| Tue 23 | 0 | 0.0 | 223 ms | 0 |
| Wed 01 | 0 | 0.0 | 130 ms | 0 |
| Wed 04 | 0 | 0.0 | 380 ms | 0 |
| Wed 06 | 0 | 0.0 | 111 ms | 0 |
| Wed 08 | 0 | 0.0 | 132 ms | 0 |
| Wed 10 | 0 | 0.0 | 167 ms | 0 |
| Wed 12 | 0 | 0.0 | 258 ms | 0 |
| Wed 15 | 0 | 0.0 | 102 ms | 0 |
| Wed 17 | 0 | 0.0 | 138 ms | 0 |
| Wed 19 | 0 | 0.0 | 150 ms | 0 |
| Wed 21 | 0 | 0.0 | 125 ms | 0 |
| Wed 23 | 0 | 0.0 | 115 ms | 0 |
| Thu 01 | 0 | 0.0 | 101 ms | 0 |
| Thu 03 | 0 | 0.0 | 122 ms | 0 |
| Thu 05 | 0 | 0.0 | 131 ms | 0 |
| Thu 07 | 0 | 0.0 | 106 ms | 0 |
| Thu 09 | 0 | 0.0 | 88 ms | 0 |
| Thu 11 | 0 | 0.0 | 120 ms | 0 |
| Thu 13 | 0 | 0.0 | 147 ms | 0 |
| Thu 16 | 0 | 0.0 | 116 ms | 0 |
| Thu 18 | 0 | 0.0 | 279 ms | 0 |
| Thu 20 | 0 | 0.0 | 1516 ms | 0 |
| Thu 22 | 0 | 0.0 | 234 ms | 0 |
| Fri 00 | 0 | 0.0 | 171 ms | 0 |
| Fri 02 | 0 | 0.0 | 144 ms | 0 |
| Fri 04 | 0 | 0.0 | 122 ms | 0 |
| Fri 05 | 0 | 0.0 | 98 ms | 0 |
| Fri 06 | 0 | 0.0 | 202 ms | 0 |
| Fri 08 | 0 | 0.0 | 117 ms | 0 |
| Fri 10 | 0 | 0.0 | 168 ms | 0 |
| Fri 11 | 0 | 0.0 | 136 ms | 0 |
| Fri 13 | 0 | 0.0 | 897 ms | 0 |
| Fri 15 | 0 | 0.0 | 124 ms | 0 |
| Fri 17 | 0 | 0.0 | 254 ms | 0 |
| Fri 19 | 0 | 0.0 | 1799 ms | 0 |
| Fri 21 | 0 | 0.0 | 173 ms | 0 |
Reliability
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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live NeoDB badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for NeoDB yet. Outages of 10 minutes or more get their own page here.
Having trouble with NeoDB?
One report per service every 10 minutes from this network. No account.
Follow NeoDB
Get an email when NeoDB goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send NeoDB alerts to Slack, Discord or a webhook — free.
About NeoDB
NeoDB is listed in our Gaming category and checked at neodb.social. reviews about book, film, music, podcast and game.
NeoDB publishes an official status page at status.neodb.social; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 353 ms average, 98–1799 ms range across 16 successful checks.
Questions
Is NeoDB down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was NeoDB last down?
We have not recorded a public NeoDB incident since monitoring began 8 days ago.
What is NeoDB's uptime?
From our own checks: 100% over 8 days of checks.
How fast does NeoDB respond?
353 ms on average over the last 24 hours (98–1799 ms).
Does NeoDB have an official status page?
Yes, at https://status.neodb.social.
NeoDB not working for me but the status is fine. What now?
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 NeoDB here at once, the problem is on NeoDB'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 NeoDB. 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.