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 7 min ago. Last stored result reached it in 187 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 297 ms | 0 |
| Mon 21 | 0 | 0.0 | 301 ms | 0 |
| Mon 23 | 0 | 0.0 | 292 ms | 0 |
| Tue 02 | 0 | 0.0 | 363 ms | 0 |
| Tue 04 | 0 | 0.0 | 364 ms | 0 |
| Tue 06 | 0 | 0.0 | 223 ms | 0 |
| Tue 08 | 0 | 0.0 | 359 ms | 0 |
| Tue 10 | 0 | 0.0 | 337 ms | 0 |
| Tue 12 | 0 | 0.0 | 306 ms | 0 |
| Tue 14 | 0 | 0.0 | 366 ms | 0 |
| Tue 17 | 0 | 0.0 | 567 ms | 0 |
| Tue 19 | 0 | 0.0 | 416 ms | 0 |
| Tue 21 | 0 | 0.0 | 265 ms | 0 |
| Tue 23 | 0 | 0.0 | 361 ms | 0 |
| Wed 02 | 0 | 0.0 | 457 ms | 0 |
| Wed 04 | 0 | 0.0 | 226 ms | 0 |
| Wed 06 | 0 | 0.0 | 347 ms | 0 |
| Wed 08 | 0 | 0.0 | 305 ms | 0 |
| Wed 11 | 0 | 0.0 | 336 ms | 0 |
| Wed 13 | 0 | 0.0 | 347 ms | 0 |
| Wed 15 | 0 | 0.0 | 318 ms | 0 |
| Wed 17 | 0 | 0.0 | 392 ms | 0 |
| Wed 19 | 0 | 0.0 | 269 ms | 0 |
| Wed 21 | 0 | 0.0 | 430 ms | 0 |
| Wed 23 | 0 | 0.0 | 383 ms | 0 |
| Thu 01 | 0 | 0.0 | 389 ms | 0 |
| Thu 03 | 0 | 0.0 | 385 ms | 0 |
| Thu 06 | 0 | 0.0 | 344 ms | 0 |
| Thu 08 | 0 | 0.0 | 283 ms | 0 |
| Thu 10 | 0 | 0.0 | 256 ms | 0 |
| Thu 12 | 0 | 0.0 | 349 ms | 0 |
| Thu 14 | 0 | 0.0 | 362 ms | 0 |
| Thu 16 | 0 | 0.0 | 385 ms | 0 |
| Thu 18 | 0 | 0.0 | 319 ms | 0 |
| Thu 20 | 0 | 0.0 | 347 ms | 0 |
| Thu 22 | 0 | 0.0 | 321 ms | 0 |
| Fri 00 | 0 | 0.0 | 259 ms | 0 |
| Fri 02 | 0 | 0.0 | 429 ms | 0 |
| Fri 04 | 0 | 0.0 | 356 ms | 0 |
| Fri 06 | 0 | 0.0 | 346 ms | 0 |
| Fri 08 | 0 | 0.0 | 340 ms | 0 |
| Fri 10 | 0 | 0.0 | 550 ms | 0 |
| Fri 11 | 0 | 0.0 | 316 ms | 0 |
| Fri 13 | 0 | 0.0 | 330 ms | 0 |
| Fri 14 | 0 | 0.0 | 327 ms | 0 |
| Fri 17 | 0 | 0.0 | 357 ms | 0 |
| Fri 18 | 0 | 0.0 | 343 ms | 0 |
| Fri 20 | 0 | 0.0 | 271 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 TCPShield 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 TCPShield goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TCPShield alerts to Slack, Discord or a webhook — free.
TCPShield, at tcpshield.com, is one of the Gaming services we monitor. Trusted by 100,000+ Minecraft networks since 2015. TCPShield provides highly available DDoS protection with low latency and 100% uptime for gaming networks.
TCPShield publishes an official status page at status.tcpshield.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 344 ms average, 187–550 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public TCPShield incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
344 ms on average over the last 24 hours (187–550 ms).
Yes, at https://status.tcpshield.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 TCPShield here at once, the problem is on TCPShield'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 TCPShield. 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.