If you still can't connect, the outage is on your side: DNS cache, VPN routing, ISP filtering, or a browser-level block. Try a different network or device to confirm.
What to try next
Check your DNS
Flush your DNS cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.
Try another network
Switch between Wi-Fi and mobile data, or disable your VPN. If it works there, the issue is on your primary network.
Browser reset
Try an incognito window or a different browser — a bad extension or cached error page can masquerade as downtime.
FAQ
Why won't Shotbow connect?
Minecraft servers go offline for the same reasons any service does — restarts after updates, DDoS, host outages, or expired domains. We connect directly to Shotbow via the SLP handshake; if the TCP socket refuses or times out, the server is unreachable. If our check shows online but you can't connect, verify your client version matches the server's protocol version.
What does the player count actually mean?
It's the live count returned by the server's own SLP response — not an estimate. Shotbow reports 50 of 1 player slots in use right now. Some servers underreport (cracked, BungeeCord, sample-only) which is a server-side choice, not a probe artifact.
How often does isitdown.io re-check Shotbow?
Every 5 minutes from the background monitor. You can also re-probe on demand by reloading this page — the probe runs server-side and the result you see is fresh.
Status badge
Embed a live status badge on your site, README, or status page. Updates automatically — same status-aware SVG the rest of isitdown.io uses.
We open a TCP socket to the server and issue a Minecraft Server List Ping (SLP) handshake, parsing the JSON response for version, MOTD, and player counts.
Counts as DOWN
The SLP handshake fails (TCP refused, timeout, or malformed response).
Counts as DEGRADED
Rarely used for Minecraft — the SLP handshake is binary: either it completes or the server is unreachable.
Detail
Latency measures the full SLP round-trip from TCP connect to handshake response, not raw ICMP ping.
Cadence
Every 5 minutes, in parallel across 4 monitoring regions (US East Virginia, US West Oregon, Europe London, Asia Singapore).
Rate-limited targets
If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status — we do not flood the target to confirm the outage.
Data source
Direct probes from our monitoring infrastructure. We do not aggregate crowd reports, Twitter mentions, or DownDetector signals — every result on this page is a live network request.