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 53 min ago. Last stored result reached it in 120 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 20:15 | 0 | 0.0 | 157 ms | 0 |
| 22:15 | 0 | 0.0 | 115 ms | 0 |
| 00:15 | 0 | 0.0 | 176 ms | 0 |
| 02:15 | 0 | 0.0 | 189 ms | 0 |
| 04:30 | 0 | 0.0 | 258 ms | 0 |
| 06:30 | 0 | 0.0 | 97 ms | 0 |
| 08:45 | 0 | 0.0 | 214 ms | 0 |
| 10:30 | 0 | 0.0 | 45 ms | 0 |
| 12:15 | 0 | 0.0 | 138 ms | 0 |
| 14:15 | 0 | 0.0 | 113 ms | 0 |
| 16:15 | 0 | 0.0 | 151 ms | 0 |
| 18:15 | 0 | 0.0 | 120 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Bound 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 Bound goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Bound alerts to Slack, Discord or a webhook — free.
Bound, at gobound.com, is one of the Sports services we monitor. Youth Sports and Activities
Bound publishes an official status page at status.gobound.com; when we can read it, its incident level is folded into the status shown here.
Common problems for sports services: ticketing, team app and live-score pages slowing down around game time.
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: 144 ms average, 30–258 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 Bound incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
144 ms on average over the last 24 hours (30–258 ms).
Yes, at https://status.gobound.com.
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 Bound here at once, the problem is on Bound'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 Bound. 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.