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 27 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 10:45 | 0 | 0.0 | 124 ms | 0 |
| 12:45 | 0 | 0.0 | 25 ms | 0 |
| 14:45 | 0 | 0.0 | 134 ms | 0 |
| 17:00 | 0 | 0.0 | 184 ms | 0 |
| 19:00 | 0 | 0.0 | 242 ms | 0 |
| 21:00 | 0 | 0.0 | 179 ms | 0 |
| 23:00 | 0 | 0.0 | 78 ms | 0 |
| 01:00 | 0 | 0.0 | 142 ms | 0 |
| 03:15 | 0 | 0.0 | 358 ms | 0 |
| 05:15 | 0 | 0.0 | 107 ms | 0 |
| 07:30 | 0 | 0.0 | 159 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.
No outages on record for Instruqt 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 Instruqt goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Instruqt alerts to Slack, Discord or a webhook — free.
Instruqt, at instruqt.com, is one of the AI services we monitor. Turn complex software into immersive, hands-on experiences that drive qualified pipeline, accelerate POCs, and close the AI adoption gap. Trusted by MongoDB, Elastic, Google, and SUSE.
Instruqt publishes an official status page at status.instruqt.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 158 ms average, 25–358 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Instruqt incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
158 ms on average over the last 24 hours (25–358 ms).
Yes, at https://status.instruqt.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 Instruqt here at once, the problem is on Instruqt'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 Instruqt. 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.