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 1 hr ago. Last stored result reached it in 805 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 380 ms | 0 |
| Tue 00 | 0 | 0.0 | 956 ms | 0 |
| Tue 02 | 0 | 0.0 | 713 ms | 0 |
| Tue 04 | 0 | 0.0 | 386 ms | 0 |
| Tue 07 | 0 | 0.0 | 813 ms | 0 |
| Tue 09 | 0 | 0.0 | 635 ms | 0 |
| Tue 11 | 0 | 0.0 | 862 ms | 0 |
| Tue 13 | 0 | 0.0 | 594 ms | 0 |
| Tue 15 | 0 | 0.0 | 696 ms | 0 |
| Tue 17 | 0 | 0.0 | 602 ms | 0 |
| Tue 20 | 0 | 0.0 | 249 ms | 0 |
| Tue 22 | 0 | 0.0 | 450 ms | 0 |
| Wed 00 | 0 | 0.0 | 829 ms | 0 |
| Wed 02 | 0 | 0.0 | 390 ms | 0 |
| Wed 05 | 0 | 0.0 | 693 ms | 0 |
| Wed 07 | 0 | 0.0 | 871 ms | 0 |
| Wed 09 | 0 | 0.0 | 376 ms | 0 |
| Wed 12 | 0 | 0.0 | 853 ms | 0 |
| Wed 14 | 0 | 0.0 | 343 ms | 0 |
| Wed 16 | 0 | 0.0 | 893 ms | 0 |
| Wed 18 | 0 | 0.0 | 906 ms | 0 |
| Wed 20 | 0 | 0.0 | 203 ms | 0 |
| Wed 22 | 0 | 0.0 | 390 ms | 0 |
| Thu 00 | 0 | 0.0 | 952 ms | 0 |
| Thu 03 | 0 | 0.0 | 942 ms | 0 |
| Thu 05 | 0 | 0.0 | 731 ms | 0 |
| Thu 07 | 0 | 0.0 | 701 ms | 0 |
| Thu 09 | 0 | 0.0 | 724 ms | 0 |
| Thu 11 | 0 | 0.0 | 360 ms | 0 |
| Thu 13 | 0 | 0.0 | 794 ms | 0 |
| Thu 15 | 0 | 0.0 | 387 ms | 0 |
| Thu 17 | 0 | 0.0 | 828 ms | 0 |
| Thu 19 | 0 | 0.0 | 863 ms | 0 |
| Thu 21 | 0 | 0.0 | 873 ms | 0 |
| Thu 23 | 0 | 0.0 | 506 ms | 0 |
| Fri 01 | 0 | 0.0 | 575 ms | 0 |
| Fri 03 | 0 | 0.0 | 545 ms | 0 |
| Fri 06 | 0 | 0.0 | 825 ms | 0 |
| Fri 08 | 0 | 0.0 | 682 ms | 0 |
| Fri 10 | 0 | 0.0 | 518 ms | 0 |
| Fri 12 | 0 | 0.0 | 796 ms | 0 |
| Fri 14 | 0 | 0.0 | 340 ms | 0 |
| Fri 16 | 0 | 0.0 | 920 ms | 0 |
| Fri 18 | 0 | 0.0 | 795 ms | 0 |
| Fri 20 | 0 | 0.0 | 560 ms | 0 |
| Fri 21 | 0 | 0.0 | 909 ms | 0 |
| Fri 23 | 0 | 0.0 | 947 ms | 0 |
| Sat 01 | 0 | 0.0 | 805 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: 691 ms average, 227–947 ms range across 16 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.
691 ms on average over the last 24 hours (227–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.