User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Nutrient 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 → nutrient.io—
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 54 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 12 | 0 | 0.0 | 52 ms | 0 |
| Mon 14 | 0 | 0.0 | 225 ms | 0 |
| Mon 16 | 0 | 0.0 | 85 ms | 0 |
| Mon 18 | 0 | 0.0 | 165 ms | 0 |
| Mon 20 | 0 | 0.0 | 56 ms | 0 |
| Mon 22 | 0 | 0.0 | 266 ms | 0 |
| Tue 00 | 0 | 0.0 | 55 ms | 0 |
| Tue 02 | 0 | 0.0 | 137 ms | 0 |
| Tue 05 | 0 | 0.0 | 35 ms | 0 |
| Tue 07 | 0 | 0.0 | 40 ms | 0 |
| Tue 09 | 0 | 0.0 | 42 ms | 0 |
| Tue 11 | 0 | 0.0 | 58 ms | 0 |
| Tue 13 | 0 | 0.0 | 64 ms | 0 |
| Tue 15 | 0 | 0.0 | 163 ms | 0 |
| Tue 18 | 0 | 0.0 | 123 ms | 0 |
| Tue 20 | 0 | 0.0 | 91 ms | 0 |
| Tue 22 | 0 | 0.0 | 129 ms | 0 |
| Wed 00 | 0 | 0.0 | 60 ms | 0 |
| Wed 03 | 0 | 0.0 | 44 ms | 0 |
| Wed 05 | 0 | 0.0 | 41 ms | 0 |
| Wed 07 | 0 | 0.0 | 50 ms | 0 |
| Wed 09 | 0 | 0.0 | 60 ms | 0 |
| Wed 12 | 0 | 0.0 | 236 ms | 0 |
| Wed 14 | 0 | 0.0 | 205 ms | 0 |
| Wed 16 | 0 | 0.0 | 113 ms | 0 |
| Wed 18 | 0 | 0.0 | 132 ms | 0 |
| Wed 20 | 0 | 0.0 | 218 ms | 0 |
| Wed 22 | 0 | 0.0 | 99 ms | 0 |
| Thu 01 | 0 | 0.0 | 245 ms | 0 |
| Thu 03 | 0 | 0.0 | 50 ms | 0 |
| Thu 05 | 0 | 0.0 | 165 ms | 0 |
| Thu 07 | 0 | 0.0 | 60 ms | 0 |
| Thu 09 | 0 | 0.0 | 57 ms | 0 |
| Thu 11 | 0 | 0.0 | 100 ms | 0 |
| Thu 13 | 0 | 0.0 | 771 ms | 0 |
| Thu 15 | 0 | 0.0 | 121 ms | 0 |
| Thu 17 | 0 | 0.0 | 89 ms | 0 |
| Thu 19 | 0 | 0.0 | 221 ms | 0 |
| Thu 21 | 0 | 0.0 | 43 ms | 0 |
| Thu 23 | 0 | 0.0 | 32 ms | 0 |
| Fri 01 | 0 | 0.0 | 218 ms | 0 |
| Fri 04 | 0 | 0.0 | 20 ms | 0 |
| Fri 06 | 0 | 0.0 | 64 ms | 0 |
| Fri 08 | 0 | 0.0 | 31 ms | 0 |
| Fri 10 | 0 | 0.0 | 26 ms | 0 |
| Fri 11 | 0 | 0.0 | 52 ms | 0 |
| Fri 13 | 0 | 0.0 | 43 ms | 0 |
| Fri 15 | 0 | 0.0 | 54 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Nutrient 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 Nutrient yet. Outages of 10 minutes or more get their own page here.
Having trouble with Nutrient?
One report per service every 10 minutes from this network. No account.
Follow Nutrient
Get an email when Nutrient goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Nutrient alerts to Slack, Discord or a webhook — free.
About Nutrient
We track Nutrient (nutrient.io) as part of the AI group. Turn knowledge trapped in documents into action with AI data extraction, document tools, and controls for agentic workflows.
Nutrient publishes an official status page at status.nutrient.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 74 ms average, 19–221 ms range across 13 successful checks.
Questions
Is Nutrient down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Nutrient last down?
We have not recorded a public Nutrient incident since monitoring began 8 days ago.
What is Nutrient's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Nutrient respond?
74 ms on average over the last 24 hours (19–221 ms).
Does Nutrient have an official status page?
Yes, at https://status.nutrient.io.
Nutrient 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 Nutrient here at once, the problem is on Nutrient'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 Nutrient. 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.