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 8 min ago. Last stored result reached it in 143 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 112 ms | 0 |
| Mon 19 | 0 | 0.0 | 201 ms | 0 |
| Mon 21 | 0 | 0.0 | 105 ms | 0 |
| Mon 23 | 0 | 0.0 | 53 ms | 0 |
| Tue 01 | 0 | 0.0 | 155 ms | 0 |
| Tue 03 | 0 | 0.0 | 82 ms | 0 |
| Tue 06 | 0 | 0.0 | 148 ms | 0 |
| Tue 08 | 0 | 0.0 | 152 ms | 0 |
| Tue 10 | 0 | 0.0 | 51 ms | 0 |
| Tue 12 | 0 | 0.0 | 42 ms | 0 |
| Tue 14 | 0 | 0.0 | 146 ms | 0 |
| Tue 16 | 0 | 0.0 | 196 ms | 0 |
| Tue 19 | 0 | 0.0 | 38 ms | 0 |
| Tue 21 | 0 | 0.0 | 587 ms | 0 |
| Tue 23 | 0 | 0.0 | 54 ms | 0 |
| Wed 01 | 0 | 0.0 | 146 ms | 0 |
| Wed 04 | 0 | 0.0 | 69 ms | 0 |
| Wed 06 | 0 | 0.0 | 145 ms | 0 |
| Wed 08 | 0 | 0.0 | 70 ms | 0 |
| Wed 10 | 0 | 0.0 | 223 ms | 0 |
| Wed 13 | 0 | 0.0 | 36 ms | 0 |
| Wed 15 | 0 | 0.0 | 185 ms | 0 |
| Wed 17 | 0 | 0.0 | 141 ms | 0 |
| Wed 19 | 0 | 0.0 | 157 ms | 0 |
| Wed 21 | 0 | 0.0 | 209 ms | 0 |
| Wed 23 | 0 | 0.0 | 165 ms | 0 |
| Thu 01 | 0 | 0.0 | 144 ms | 0 |
| Thu 03 | 0 | 0.0 | 658 ms | 0 |
| Thu 05 | 0 | 0.0 | 70 ms | 0 |
| Thu 08 | 0 | 0.0 | 147 ms | 0 |
| Thu 10 | 0 | 0.0 | 77 ms | 0 |
| Thu 12 | 0 | 0.0 | 239 ms | 0 |
| Thu 14 | 0 | 0.0 | 155 ms | 0 |
| Thu 16 | 0 | 0.0 | 172 ms | 0 |
| Thu 18 | 0 | 0.0 | 156 ms | 0 |
| Thu 20 | 0 | 0.0 | 111 ms | 0 |
| Thu 22 | 0 | 0.0 | 42 ms | 0 |
| Fri 00 | 0 | 0.0 | 73 ms | 0 |
| Fri 02 | 0 | 0.0 | 80 ms | 0 |
| Fri 04 | 0 | 0.0 | 156 ms | 0 |
| Fri 06 | 0 | 0.0 | 129 ms | 0 |
| Fri 08 | 0 | 0.0 | 62 ms | 0 |
| Fri 10 | 0 | 0.0 | 197 ms | 0 |
| Fri 12 | 0 | 0.0 | 115 ms | 0 |
| Fri 14 | 0 | 0.0 | 53 ms | 0 |
| Fri 17 | 0 | 0.0 | 129 ms | 0 |
| Fri 19 | 0 | 0.0 | 98 ms | 0 |
| Fri 21 | 0 | 0.0 | 143 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 databallr 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 databallr goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send databallr alerts to Slack, Discord or a webhook — free.
databallr, at databallr.com, is one of the Gaming services we monitor. Advanced NBA and WNBA analytics — RAPM and DPM impact, WOWY lineup splits, shot quality, matchups, contracts, rankings, and live scores, plus the SixRings draft games.
databallr publishes an official status page at status.databallr.com; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 106 ms average, 42–197 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 databallr incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
106 ms on average over the last 24 hours (42–197 ms).
Yes, at https://status.databallr.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 databallr here at once, the problem is on databallr'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 databallr. 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.