User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 38 min ago. Last stored result reached it in 364 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 167 ms | 0 |
| Nov 7 | 0 | 0.0 | 248 ms | 0 |
| Nov 7 | 0 | 0.0 | 98 ms | 0 |
| Nov 7 | 0 | 0.0 | 163 ms | 0 |
| Nov 8 | 0 | 0.0 | 153 ms | 0 |
| Nov 8 | 0 | 0.0 | 190 ms | 0 |
| Nov 8 | 0 | 0.0 | 222 ms | 0 |
| Nov 8 | 0 | 0.0 | 186 ms | 0 |
| Nov 9 | 0 | 0.0 | 262 ms | 0 |
| Nov 9 | 0 | 0.0 | 166 ms | 0 |
| Nov 9 | 0 | 0.0 | 168 ms | 0 |
| Nov 9 | 0 | 0.0 | 328 ms | 0 |
| Nov 10 | 0 | 0.0 | 199 ms | 0 |
| Nov 10 | 0 | 0.0 | 262 ms | 0 |
| Nov 10 | 0 | 0.0 | 200 ms | 0 |
| Nov 10 | 0 | 0.0 | 163 ms | 0 |
| Nov 11 | 0 | 0.0 | 178 ms | 0 |
| Nov 11 | 0 | 0.0 | 219 ms | 0 |
| Nov 11 | 0 | 0.0 | 191 ms | 0 |
| Nov 11 | 0 | 0.0 | 441 ms | 0 |
| Nov 12 | 0 | 0.0 | 227 ms | 0 |
| Nov 12 | 0 | 0.0 | 284 ms | 0 |
| Nov 12 | 0 | 0.0 | 377 ms | 0 |
| Nov 12 | 0 | 0.0 | 212 ms | 0 |
| Nov 13 | 0 | 0.0 | 284 ms | 0 |
| Nov 13 | 0 | 0.0 | 212 ms | 0 |
| Nov 13 | 0 | 0.0 | 174 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 7 days of data so far, so the 90-day numbers fill in over time.
Scheduled Maintenance: GenAI Workflows
On Saturday, November 14, 2026, between 20:00 and 21:00 UTC, we will perform scheduled maintenance on the infrastructure behind our LLM (GenAI) workflows in the Intento and EU data centers. During this window, LLM workflows will be unavailable for approximately 10 minutes. Translation requests that use LLM workflows during this time may fail, so we recommend retrying them after the maintenance…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Intento 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 Intento goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Intento alerts to Slack, Discord or a webhook — free.
We track Intento (inten.to) as part of the AI group. Intento Language Hub connects 40+ MT engines and LLMs and runs AI agents for translation, LQA and post-editing in ServiceNow, Salesforce, Jira and more.
Intento publishes an official status page at status.inten.to; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 252 ms average, 70–463 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Intento incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
252 ms on average over the last 24 hours (70–463 ms).
Yes, at https://status.inten.to.
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 Intento here at once, the problem is on Intento'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 Intento. 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.