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 661 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 744 ms | 0 |
| Nov 7 | 0 | 0.0 | 755 ms | 0 |
| Nov 8 | 0 | 0.0 | 720 ms | 0 |
| Nov 8 | 0 | 0.0 | 644 ms | 0 |
| Nov 8 | 0 | 0.0 | 821 ms | 0 |
| Nov 8 | 0 | 0.0 | 871 ms | 0 |
| Nov 9 | 0 | 0.0 | 824 ms | 0 |
| Nov 9 | 0 | 0.0 | 873 ms | 0 |
| Nov 9 | 0 | 0.0 | 612 ms | 0 |
| Nov 9 | 0 | 0.0 | 701 ms | 0 |
| Nov 10 | 0 | 0.0 | 713 ms | 0 |
| Nov 10 | 0 | 0.0 | 813 ms | 0 |
| Nov 10 | 0 | 0.0 | 602 ms | 0 |
| Nov 10 | 0 | 0.0 | 249 ms | 0 |
| Nov 11 | 0 | 0.0 | 693 ms | 0 |
| Nov 11 | 0 | 0.0 | 624 ms | 0 |
| Nov 11 | 0 | 0.0 | 853 ms | 0 |
| Nov 11 | 0 | 0.0 | 390 ms | 0 |
| Nov 12 | 0 | 0.0 | 942 ms | 0 |
| Nov 12 | 0 | 0.0 | 701 ms | 0 |
| Nov 12 | 0 | 0.0 | 810 ms | 0 |
| Nov 12 | 0 | 0.0 | 852 ms | 0 |
| Nov 13 | 0 | 0.0 | 575 ms | 0 |
| Nov 13 | 0 | 0.0 | 674 ms | 0 |
| Nov 13 | 0 | 0.0 | 796 ms | 0 |
| Nov 13 | 0 | 0.0 | 820 ms | 0 |
| Nov 14 | 0 | 0.0 | 733 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 Testomat.io 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 Testomat.io goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Testomat.io alerts to Slack, Discord or a webhook — free.
We track Testomat.io (testomat.io) as part of the AI group. AI test management with Testomat.io: manage automated & manual testing. Real-time reports, advanced JIRA plugin & AI agents. Start free!
Testomat.io publishes an official status page at status.testomat.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: 709 ms average, 340–947 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Testomat.io incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
709 ms on average over the last 24 hours (340–947 ms).
Yes, at https://status.testomat.io.
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 Testomat.io here at once, the problem is on Testomat.io'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 Testomat.io. 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.