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 2 hr ago. Last stored result reached it in 247 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 195 ms | 0 |
| Tue 01 | 0 | 0.0 | 160 ms | 0 |
| Tue 03 | 0 | 0.0 | 118 ms | 0 |
| Tue 06 | 0 | 0.0 | 152 ms | 0 |
| Tue 08 | 0 | 0.0 | 45 ms | 0 |
| Tue 10 | 0 | 0.0 | 59 ms | 0 |
| Tue 12 | 0 | 0.0 | 233 ms | 0 |
| Tue 14 | 0 | 0.0 | 178 ms | 0 |
| Tue 17 | 0 | 0.0 | 185 ms | 0 |
| Tue 19 | 0 | 0.0 | 95 ms | 0 |
| Tue 21 | 0 | 0.0 | 194 ms | 0 |
| Tue 23 | 0 | 0.0 | 249 ms | 0 |
| Wed 02 | 0 | 0.0 | 57 ms | 0 |
| Wed 04 | 0 | 0.0 | 158 ms | 0 |
| Wed 06 | 0 | 0.0 | 310 ms | 0 |
| Wed 08 | 0 | 0.0 | 114 ms | 0 |
| Wed 11 | 0 | 0.0 | 91 ms | 0 |
| Wed 13 | 0 | 0.0 | 136 ms | 0 |
| Wed 15 | 0 | 0.0 | 43 ms | 0 |
| Wed 17 | 0 | 0.0 | 116 ms | 0 |
| Wed 19 | 0 | 0.0 | 172 ms | 0 |
| Wed 21 | 0 | 0.0 | 367 ms | 0 |
| Thu 00 | 0 | 0.0 | 218 ms | 0 |
| Thu 02 | 0 | 0.0 | 53 ms | 0 |
| Thu 04 | 0 | 0.0 | 99 ms | 0 |
| Thu 05 | 0 | 0.0 | 285 ms | 0 |
| Thu 07 | 0 | 0.0 | 255 ms | 0 |
| Thu 09 | 0 | 0.0 | 36 ms | 0 |
| Thu 11 | 0 | 0.0 | 234 ms | 0 |
| Thu 13 | 0 | 0.0 | 39 ms | 0 |
| Thu 15 | 0 | 0.0 | 202 ms | 0 |
| Thu 17 | 0 | 0.0 | 185 ms | 0 |
| Thu 19 | 0 | 0.0 | 112 ms | 0 |
| Thu 21 | 0 | 0.0 | 262 ms | 0 |
| Thu 23 | 0 | 0.0 | 126 ms | 0 |
| Fri 01 | 0 | 0.0 | 289 ms | 0 |
| Fri 03 | 0 | 0.0 | 193 ms | 0 |
| Fri 06 | 0 | 0.0 | 292 ms | 0 |
| Fri 08 | 0 | 0.0 | 102 ms | 0 |
| Fri 09 | 0 | 0.0 | 86 ms | 0 |
| Fri 11 | 0 | 0.0 | 202 ms | 0 |
| Fri 13 | 0 | 0.0 | 179 ms | 0 |
| Fri 15 | 0 | 0.0 | 169 ms | 0 |
| Fri 17 | 0 | 0.0 | 233 ms | 0 |
| Fri 18 | 0 | 0.0 | 176 ms | 0 |
| Fri 19 | 0 | 0.0 | 269 ms | 0 |
| Fri 21 | 0 | 0.0 | 45 ms | 0 |
| Fri 23 | 0 | 0.0 | 247 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Text Cortex AI UG 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 Text Cortex AI UG goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Text Cortex AI UG alerts to Slack, Discord or a webhook — free.
Text Cortex AI UG is listed in our AI category and checked at textcortex.com. Find valuable workflows and build agents with the people who use them. Grow adoption in a governed workspace built for Europe.
Text Cortex AI UG publishes an official status page at status.textcortex.com; 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: 191 ms average, 45–292 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 Text Cortex AI UG incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
191 ms on average over the last 24 hours (45–292 ms).
Yes, at https://status.textcortex.com.
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 Text Cortex AI UG here at once, the problem is on Text Cortex AI UG'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 Text Cortex AI UG. 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.