User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is NextSDS 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 → nextsds.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 hr ago. Last stored result reached it in 55 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 79 ms | 0 |
| Mon 21 | 0 | 0.0 | 59 ms | 0 |
| Mon 23 | 0 | 0.0 | 52 ms | 0 |
| Tue 01 | 0 | 0.0 | 46 ms | 0 |
| Tue 03 | 0 | 0.0 | 43 ms | 0 |
| Tue 05 | 0 | 0.0 | 52 ms | 0 |
| Tue 07 | 0 | 0.0 | 59 ms | 0 |
| Tue 09 | 0 | 0.0 | 118 ms | 0 |
| Tue 12 | 0 | 0.0 | 52 ms | 0 |
| Tue 14 | 0 | 0.0 | 83 ms | 0 |
| Tue 16 | 0 | 0.0 | 60 ms | 0 |
| Tue 18 | 0 | 0.0 | 104 ms | 0 |
| Tue 21 | 0 | 0.0 | 38 ms | 0 |
| Tue 23 | 0 | 0.0 | 59 ms | 0 |
| Wed 01 | 0 | 0.0 | 62 ms | 0 |
| Wed 03 | 0 | 0.0 | 34 ms | 0 |
| Wed 06 | 0 | 0.0 | 47 ms | 0 |
| Wed 08 | 0 | 0.0 | 36 ms | 0 |
| Wed 10 | 0 | 0.0 | 28 ms | 0 |
| Wed 12 | 0 | 0.0 | 21 ms | 0 |
| Wed 14 | 0 | 0.0 | 67 ms | 0 |
| Wed 16 | 0 | 0.0 | 106 ms | 0 |
| Wed 19 | 0 | 0.0 | 90 ms | 0 |
| Wed 21 | 0 | 0.0 | 45 ms | 0 |
| Wed 23 | 0 | 0.0 | 78 ms | 0 |
| Thu 01 | 0 | 0.0 | 32 ms | 0 |
| Thu 03 | 0 | 0.0 | 54 ms | 0 |
| Thu 05 | 0 | 0.0 | 88 ms | 0 |
| Thu 07 | 0 | 0.0 | 104 ms | 0 |
| Thu 09 | 0 | 0.0 | 84 ms | 0 |
| Thu 11 | 0 | 0.0 | 75 ms | 0 |
| Thu 14 | 0 | 0.0 | 71 ms | 0 |
| Thu 16 | 0 | 0.0 | 59 ms | 0 |
| Thu 18 | 0 | 0.0 | 267 ms | 0 |
| Thu 20 | 0 | 0.0 | 105 ms | 0 |
| Thu 22 | 0 | 0.0 | 46 ms | 0 |
| Fri 00 | 0 | 0.0 | 77 ms | 0 |
| Fri 02 | 0 | 0.0 | 60 ms | 0 |
| Fri 04 | 0 | 0.0 | 42 ms | 0 |
| Fri 06 | 0 | 0.0 | 73 ms | 0 |
| Fri 08 | 0 | 0.0 | 55 ms | 0 |
| Fri 10 | 0 | 0.0 | 37 ms | 0 |
| Fri 11 | 0 | 0.0 | 37 ms | 0 |
| Fri 12 | 0 | 0.0 | 65 ms | 0 |
| Fri 14 | 0 | 0.0 | 49 ms | 0 |
| Fri 16 | 0 | 0.0 | 48 ms | 0 |
| Fri 18 | 0 | 0.0 | 86 ms | 0 |
| Fri 20 | 0 | 0.0 | 55 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 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live NextSDS 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 NextSDS yet. Outages of 10 minutes or more get their own page here.
Having trouble with NextSDS?
One report per service every 10 minutes from this network. No account.
Follow NextSDS
Get an email when NextSDS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send NextSDS alerts to Slack, Discord or a webhook — free.
About NextSDS
NextSDS, at nextsds.com, is one of the AI services we monitor. Manage every safety data sheet in one place. AI reads your SDSs, flags outdated versions and keeps you OSHA, REACH and CLP compliant. Start free.
NextSDS publishes an official status page at status.nextsds.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 56 ms average, 21–89 ms range across 14 successful checks.
Questions
Is NextSDS down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was NextSDS last down?
We have not recorded a public NextSDS incident since monitoring began 6 days ago.
What is NextSDS's uptime?
From our own checks: 100% over 6 days of checks.
How fast does NextSDS respond?
56 ms on average over the last 24 hours (21–89 ms).
Does NextSDS have an official status page?
Yes, at https://status.nextsds.com.
NextSDS 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report NextSDS here at once, the problem is on NextSDS'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 NextSDS. 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.