User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Sports
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 45 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 21 | 0 | 0.0 | 64 ms | 0 |
| Tue 23 | 0 | 0.0 | 55 ms | 0 |
| Wed 02 | 0 | 0.0 | 214 ms | 0 |
| Wed 04 | 0 | 0.0 | 88 ms | 0 |
| Wed 06 | 0 | 0.0 | 169 ms | 0 |
| Wed 08 | 0 | 0.0 | 50 ms | 0 |
| Wed 11 | 0 | 0.0 | 127 ms | 0 |
| Wed 13 | 0 | 0.0 | 70 ms | 0 |
| Wed 15 | 0 | 0.0 | 133 ms | 0 |
| Wed 17 | 0 | 0.0 | 95 ms | 0 |
| Wed 19 | 0 | 0.0 | 82 ms | 0 |
| Wed 21 | 0 | 0.0 | 66 ms | 0 |
| Thu 00 | 0 | 0.0 | 71 ms | 0 |
| Thu 02 | 0 | 0.0 | 54 ms | 0 |
| Thu 04 | 0 | 0.0 | 76 ms | 0 |
| Thu 06 | 0 | 0.0 | 46 ms | 0 |
| Thu 08 | 0 | 0.0 | 77 ms | 0 |
| Thu 10 | 0 | 0.0 | 55 ms | 0 |
| Thu 12 | 0 | 0.0 | 72 ms | 0 |
| Thu 14 | 0 | 0.0 | 89 ms | 0 |
| Thu 16 | 0 | 0.0 | 59 ms | 0 |
| Thu 18 | 0 | 0.0 | 89 ms | 0 |
| Thu 20 | 0 | 0.0 | 43 ms | 0 |
| Thu 22 | 0 | 0.0 | 194 ms | 0 |
| Fri 01 | 0 | 0.0 | 38 ms | 0 |
| Fri 03 | 0 | 0.0 | 74 ms | 0 |
| Fri 05 | 0 | 0.0 | 91 ms | 0 |
| Fri 07 | 0 | 0.0 | 55 ms | 0 |
| Fri 09 | 0 | 0.0 | 138 ms | 0 |
| Fri 11 | 0 | 0.0 | 36 ms | 0 |
| Fri 12 | 0 | 0.0 | 62 ms | 0 |
| Fri 14 | 0 | 0.0 | 38 ms | 0 |
| Fri 16 | 0 | 0.0 | 73 ms | 0 |
| Fri 18 | 0 | 0.0 | 83 ms | 0 |
| Fri 19 | 0 | 0.0 | 62 ms | 0 |
| Fri 21 | 0 | 0.0 | 143 ms | 0 |
| Fri 23 | 0 | 0.0 | 34 ms | 0 |
| Sat 01 | 0 | 0.0 | 90 ms | 0 |
| Sat 02 | 0 | 0.0 | 29 ms | 0 |
| Sat 04 | 0 | 0.0 | 85 ms | 0 |
| Sat 05 | 0 | 0.0 | 133 ms | 0 |
| Sat 07 | 0 | 0.0 | 141 ms | 0 |
| Sat 10 | 0 | 0.0 | 50 ms | 0 |
| Sat 12 | 0 | 0.0 | 136 ms | 0 |
| Sat 14 | 0 | 0.0 | 140 ms | 0 |
| Sat 16 | 0 | 0.0 | 78 ms | 0 |
| Sat 18 | 0 | 0.0 | 171 ms | 0 |
| Sat 20 | 0 | 0.0 | 45 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 SX.bet 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 SX.bet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
SX.bet is listed in our Sports category and checked at sx.bet. Bet online with SX Bet, the largest crypto sports betting exchange in the world. Browse the best odds, including NFL, MLB, NHL, and NBA. Peer-to-peer sports betting. Earn Crypto and Stake on SX Bet.
SX.bet publishes an official status page at status.sx.bet; when we can read it, its incident level is folded into the status shown here.
Typical issues with sports services: ticketing, team app and live-score pages slowing down around game time.
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: 97 ms average, 29–232 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 SX.bet incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
97 ms on average over the last 24 hours (29–232 ms).
Yes, at https://status.sx.bet.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For sports services, watch for ticketing, team app and live-score pages slowing down around game time. If many people report SX.bet here at once, the problem is on SX.bet'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 SX.bet. 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.