User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Social
Is CNS Next down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → cnsnext.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 min ago. Last stored result reached it in 587 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 561 ms | 0 |
| Tue 02 | 0 | 0.0 | 564 ms | 0 |
| Tue 04 | 0 | 0.0 | 574 ms | 0 |
| Tue 06 | 0 | 0.0 | 488 ms | 0 |
| Tue 07 | 0 | 0.0 | 155 ms | 0 |
| Tue 09 | 0 | 0.0 | 590 ms | 0 |
| Tue 11 | 0 | 0.0 | 555 ms | 0 |
| Tue 13 | 0 | 0.0 | 478 ms | 0 |
| Tue 15 | 0 | 0.0 | 561 ms | 0 |
| Tue 17 | 0 | 0.0 | 615 ms | 0 |
| Tue 20 | 0 | 0.0 | 621 ms | 0 |
| Tue 22 | 0 | 0.0 | 590 ms | 0 |
| Wed 00 | 0 | 0.0 | 639 ms | 0 |
| Wed 02 | 0 | 0.0 | 680 ms | 0 |
| Wed 05 | 0 | 0.0 | 597 ms | 0 |
| Wed 07 | 0 | 0.0 | 448 ms | 0 |
| Wed 09 | 0 | 0.0 | 273 ms | 0 |
| Wed 11 | 0 | 0.0 | 260 ms | 0 |
| Wed 13 | 0 | 0.0 | 598 ms | 0 |
| Wed 15 | 0 | 0.0 | 291 ms | 0 |
| Wed 18 | 0 | 0.0 | 601 ms | 0 |
| Wed 20 | 0 | 0.0 | 620 ms | 0 |
| Wed 22 | 0 | 0.0 | 434 ms | 0 |
| Thu 00 | 0 | 0.0 | 678 ms | 0 |
| Thu 02 | 0 | 0.0 | 786 ms | 0 |
| Thu 04 | 0 | 0.0 | 395 ms | 0 |
| Thu 06 | 0 | 0.0 | 626 ms | 0 |
| Thu 08 | 0 | 0.0 | 626 ms | 0 |
| Thu 10 | 0 | 0.0 | 569 ms | 0 |
| Thu 13 | 0 | 0.0 | 571 ms | 0 |
| Thu 15 | 0 | 0.0 | 580 ms | 0 |
| Thu 17 | 0 | 0.0 | 310 ms | 0 |
| Thu 19 | 0 | 0.0 | 487 ms | 0 |
| Thu 21 | 0 | 0.0 | 589 ms | 0 |
| Thu 23 | 0 | 0.0 | 571 ms | 0 |
| Fri 01 | 0 | 0.0 | 674 ms | 0 |
| Fri 03 | 0 | 0.0 | 631 ms | 0 |
| Fri 04 | 0 | 0.0 | 625 ms | 0 |
| Fri 06 | 0 | 0.0 | 295 ms | 0 |
| Fri 09 | 0 | 0.0 | 312 ms | 0 |
| Fri 11 | 0 | 0.0 | 587 ms | 0 |
| Fri 13 | 0 | 0.0 | 645 ms | 0 |
| Fri 15 | 0 | 0.0 | 590 ms | 0 |
| Fri 17 | 0 | 0.0 | 297 ms | 0 |
| Fri 19 | 0 | 0.0 | 650 ms | 0 |
| Fri 21 | 0 | 0.0 | 572 ms | 0 |
| Fri 23 | 0 | 0.0 | 646 ms | 0 |
| Sat 01 | 0 | 0.0 | 587 ms | 0 |
Reliability
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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live CNS Next badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for CNS Next yet. Outages of 10 minutes or more get their own page here.
Having trouble with CNS Next?
One report per service every 10 minutes from this network. No account.
Follow CNS Next
Get an email when CNS Next goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CNS Next alerts to Slack, Discord or a webhook — free.
About CNS Next
CNS Next, at cnsnext.com, is one of the Social services we monitor. Thomasville launched CNS in 1999, expanding its fiber-optic network to deliver reliable high-speed internet and telecommunications services community-wide.
CNS Next publishes an official status page at status.cnsnext.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with social services: feeds not loading, posts or messages not sending, and login loops.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 547 ms average, 295–674 ms range across 13 successful checks.
Questions
Is CNS Next down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was CNS Next last down?
We have not recorded a public CNS Next incident since monitoring began 7 days ago.
What is CNS Next's uptime?
From our own checks: 100% over 7 days of checks.
How fast does CNS Next respond?
547 ms on average over the last 24 hours (295–674 ms).
Does CNS Next have an official status page?
Yes, at https://status.cnsnext.com.
CNS Next not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report CNS Next here at once, the problem is on CNS Next'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 CNS Next. 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.