User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
nexcess.net · Productivity
Is Nexcess down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → nexcess.net—
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, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 311 ms · just now.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 03 | 0 | 0.0 | 812 ms | 0 |
| Mon 04 | 0 | 0.0 | 441 ms | 0 |
| Mon 05 | 0 | 0.0 | 570 ms | 0 |
| Mon 06 | 0 | 0.0 | 302 ms | 0 |
| Mon 07 | 0 | 0.0 | 461 ms | 0 |
| Mon 08 | 0 | 0.0 | 476 ms | 0 |
| Mon 09 | 0 | 0.0 | 365 ms | 0 |
| Mon 10 | 0 | 0.0 | 602 ms | 0 |
| Mon 11 | 0 | 0.0 | 1071 ms | 0 |
| Mon 12 | 0 | 0.0 | 583 ms | 0 |
| Mon 13 | 0 | 0.0 | 604 ms | 0 |
| Mon 14 | 0 | 0.0 | 655 ms | 0 |
| Mon 15 | 0 | 0.0 | 445 ms | 0 |
| Mon 16 | 0 | 0.0 | 261 ms | 0 |
| Mon 17 | 0 | 0.0 | 400 ms | 0 |
| Mon 18 | 0 | 0.0 | 624 ms | 0 |
| Mon 19 | 0 | 0.0 | 1077 ms | 0 |
| Mon 20 | 0 | 0.0 | 325 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live Nexcess status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Nexcess yet. Outages of 10 minutes or more get their own page here.
Having trouble with Nexcess?
One report per service every 10 minutes from this network. No account.
Follow Nexcess
Get an email when Nexcess goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Nexcess alerts to Slack, Discord or a webhook — free.
Questions
Is Nexcess down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Nexcess not working for me but the status is fine. What now?
If Nexcess is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Nexcess's side.
How does Damn is it down decide Nexcess's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is Nexcess checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.