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 1 hr ago. Last stored result reached it in 115 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 82 ms | 0 |
| Mon 21 | 0 | 0.0 | 118 ms | 0 |
| Mon 23 | 0 | 0.0 | 61 ms | 0 |
| Tue 01 | 0 | 0.0 | 52 ms | 0 |
| Tue 04 | 0 | 0.0 | 147 ms | 0 |
| Tue 06 | 0 | 0.0 | 96 ms | 0 |
| Tue 08 | 0 | 0.0 | 128 ms | 0 |
| Tue 10 | 0 | 0.0 | 75 ms | 0 |
| Tue 12 | 0 | 0.0 | 98 ms | 0 |
| Tue 14 | 0 | 0.0 | 145 ms | 0 |
| Tue 17 | 0 | 0.0 | 89 ms | 0 |
| Tue 19 | 0 | 0.0 | 102 ms | 0 |
| Tue 21 | 0 | 0.0 | 40 ms | 0 |
| Tue 23 | 0 | 0.0 | 59 ms | 0 |
| Wed 01 | 0 | 0.0 | 33 ms | 0 |
| Wed 04 | 0 | 0.0 | 73 ms | 0 |
| Wed 06 | 0 | 0.0 | 68 ms | 0 |
| Wed 08 | 0 | 0.0 | 164 ms | 0 |
| Wed 11 | 0 | 0.0 | 101 ms | 0 |
| Wed 13 | 0 | 0.0 | 100 ms | 0 |
| Wed 15 | 0 | 0.0 | 72 ms | 0 |
| Wed 17 | 0 | 0.0 | 131 ms | 0 |
| Wed 19 | 0 | 0.0 | 147 ms | 0 |
| Wed 21 | 0 | 0.0 | 96 ms | 0 |
| Wed 23 | 0 | 0.0 | 119 ms | 0 |
| Thu 02 | 0 | 0.0 | 145 ms | 0 |
| Thu 04 | 0 | 0.0 | 73 ms | 0 |
| Thu 06 | 0 | 0.0 | 119 ms | 0 |
| Thu 08 | 0 | 0.0 | 88 ms | 0 |
| Thu 10 | 0 | 0.0 | 111 ms | 0 |
| Thu 12 | 0 | 0.0 | 168 ms | 0 |
| Thu 14 | 0 | 0.0 | 99 ms | 0 |
| Thu 16 | 0 | 0.0 | 182 ms | 0 |
| Thu 18 | 0 | 0.0 | 111 ms | 0 |
| Thu 20 | 0 | 0.0 | 103 ms | 0 |
| Thu 22 | 0 | 0.0 | 116 ms | 0 |
| Fri 00 | 0 | 0.0 | 108 ms | 0 |
| Fri 02 | 0 | 0.0 | 97 ms | 0 |
| Fri 04 | 0 | 0.0 | 87 ms | 0 |
| Fri 06 | 0 | 0.0 | 133 ms | 0 |
| Fri 09 | 0 | 0.0 | 54 ms | 0 |
| Fri 11 | 0 | 0.0 | 113 ms | 0 |
| Fri 13 | 0 | 0.0 | 111 ms | 0 |
| Fri 15 | 0 | 0.0 | 85 ms | 0 |
| Fri 17 | 0 | 0.0 | 118 ms | 0 |
| Fri 19 | 0 | 0.0 | 170 ms | 0 |
| Fri 21 | 0 | 0.0 | 72 ms | 0 |
| Fri 23 | 0 | 0.0 | 115 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 Pike13 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 Pike13 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pike13 alerts to Slack, Discord or a webhook — free.
We track Pike13 (pike13.com) as part of the Sports group. Pike13 is scheduling, enrollment, payment, and skill tracking software for fitness studios, music schools, swim schools, martial arts, youth coding, and franchise networks.
Pike13 publishes an official status page at status.pike13.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 105 ms average, 54–170 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 Pike13 incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
105 ms on average over the last 24 hours (54–170 ms).
Yes, at https://status.pike13.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 Pike13 here at once, the problem is on Pike13'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 Pike13. 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.