User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / News
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 12 min ago. Last stored result reached it in 87 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 08 | 0 | 0.0 | 121 ms | 0 |
| Tue 10 | 0 | 0.0 | 39 ms | 0 |
| Tue 12 | 0 | 0.0 | 37 ms | 0 |
| Tue 14 | 0 | 0.0 | 89 ms | 0 |
| Tue 16 | 0 | 0.0 | 27 ms | 0 |
| Tue 19 | 0 | 0.0 | 124 ms | 0 |
| Tue 21 | 0 | 0.0 | 50 ms | 0 |
| Tue 23 | 0 | 0.0 | 105 ms | 0 |
| Wed 01 | 0 | 0.0 | 28 ms | 0 |
| Wed 03 | 0 | 0.0 | 34 ms | 0 |
| Wed 06 | 0 | 0.0 | 41 ms | 0 |
| Wed 08 | 0 | 0.0 | 160 ms | 0 |
| Wed 10 | 0 | 0.0 | 32 ms | 0 |
| Wed 12 | 0 | 0.0 | 124 ms | 0 |
| Wed 15 | 0 | 0.0 | 74 ms | 0 |
| Wed 17 | 0 | 0.0 | 75 ms | 0 |
| Wed 19 | 0 | 0.0 | 126 ms | 0 |
| Wed 21 | 0 | 0.0 | 152 ms | 0 |
| Wed 23 | 0 | 0.0 | 83 ms | 0 |
| Thu 01 | 0 | 0.0 | 95 ms | 0 |
| Thu 03 | 0 | 0.0 | 114 ms | 0 |
| Thu 06 | 0 | 0.0 | 40 ms | 0 |
| Thu 08 | 0 | 0.0 | 27 ms | 0 |
| Thu 10 | 0 | 0.0 | 33 ms | 0 |
| Thu 12 | 0 | 0.0 | 70 ms | 0 |
| Thu 14 | 0 | 0.0 | 117 ms | 0 |
| Thu 16 | 0 | 0.0 | 109 ms | 0 |
| Thu 18 | 0 | 0.0 | 150 ms | 0 |
| Thu 20 | 0 | 0.0 | 74 ms | 0 |
| Thu 22 | 0 | 0.0 | 43 ms | 0 |
| Fri 00 | 0 | 0.0 | 37 ms | 0 |
| Fri 02 | 0 | 0.0 | 110 ms | 0 |
| Fri 03 | 0 | 0.0 | 40 ms | 0 |
| Fri 05 | 0 | 0.0 | 75 ms | 0 |
| Fri 07 | 0 | 0.0 | 48 ms | 0 |
| Fri 09 | 0 | 0.0 | 63 ms | 0 |
| Fri 11 | 0 | 0.0 | 137 ms | 0 |
| Fri 13 | 0 | 0.0 | 124 ms | 0 |
| Fri 15 | 0 | 0.0 | 101 ms | 0 |
| Fri 16 | 0 | 0.0 | 115 ms | 0 |
| Fri 17 | 0 | 0.0 | 69 ms | 0 |
| Fri 18 | 0 | 0.0 | 156 ms | 0 |
| Fri 20 | 0 | 0.0 | 34 ms | 0 |
| Fri 21 | 0 | 0.0 | 113 ms | 0 |
| Fri 23 | 0 | 0.0 | 186 ms | 0 |
| Sat 01 | 0 | 0.0 | 115 ms | 0 |
| Sat 03 | 0 | 0.0 | 87 ms | 0 |
| Sat 04 | 0 | 0.0 | 104 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 TigerNet 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 TigerNet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TigerNet alerts to Slack, Discord or a webhook — free.
TigerNet, at tigernet.com, is one of the News services we monitor. TigerNet is the oldest and largest source of Clemson Football and Recruiting News and Discussion. Join our community today, 100% free!
TigerNet publishes an official status page at status.tigernet.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with news services: news sites and live streams slowing under breaking-news traffic, and weather alerts and radar pages failing during storms.
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: 98 ms average, 18–186 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public TigerNet incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
98 ms on average over the last 24 hours (18–186 ms).
Yes, at https://status.tigernet.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For news services, watch for news sites and live streams slowing under breaking-news traffic, and weather alerts and radar pages failing during storms. If many people report TigerNet here at once, the problem is on TigerNet'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 TigerNet. 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.