User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Instruqt down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → instruqt.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 306 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 89 ms | 0 |
| Tue 00 | 0 | 0.0 | 258 ms | 0 |
| Tue 02 | 0 | 0.0 | 156 ms | 0 |
| Tue 04 | 0 | 0.0 | 132 ms | 0 |
| Tue 06 | 0 | 0.0 | 130 ms | 0 |
| Tue 08 | 0 | 0.0 | 237 ms | 0 |
| Tue 10 | 0 | 0.0 | 191 ms | 0 |
| Tue 12 | 0 | 0.0 | 124 ms | 0 |
| Tue 13 | 0 | 0.0 | 46 ms | 0 |
| Tue 15 | 0 | 0.0 | 301 ms | 0 |
| Tue 17 | 0 | 0.0 | 118 ms | 0 |
| Tue 19 | 0 | 0.0 | 176 ms | 0 |
| Tue 22 | 0 | 0.0 | 234 ms | 0 |
| Wed 00 | 0 | 0.0 | 140 ms | 0 |
| Wed 02 | 0 | 0.0 | 140 ms | 0 |
| Wed 04 | 0 | 0.0 | 202 ms | 0 |
| Wed 06 | 0 | 0.0 | 120 ms | 0 |
| Wed 09 | 0 | 0.0 | 149 ms | 0 |
| Wed 11 | 0 | 0.0 | 166 ms | 0 |
| Wed 13 | 0 | 0.0 | 145 ms | 0 |
| Wed 15 | 0 | 0.0 | 146 ms | 0 |
| Wed 17 | 0 | 0.0 | 174 ms | 0 |
| Wed 20 | 0 | 0.0 | 206 ms | 0 |
| Wed 22 | 0 | 0.0 | 121 ms | 0 |
| Thu 00 | 0 | 0.0 | 181 ms | 0 |
| Thu 02 | 0 | 0.0 | 168 ms | 0 |
| Thu 04 | 0 | 0.0 | 330 ms | 0 |
| Thu 06 | 0 | 0.0 | 64 ms | 0 |
| Thu 08 | 0 | 0.0 | 80 ms | 0 |
| Thu 10 | 0 | 0.0 | 124 ms | 0 |
| Thu 12 | 0 | 0.0 | 25 ms | 0 |
| Thu 14 | 0 | 0.0 | 134 ms | 0 |
| Thu 17 | 0 | 0.0 | 184 ms | 0 |
| Thu 19 | 0 | 0.0 | 242 ms | 0 |
| Thu 21 | 0 | 0.0 | 179 ms | 0 |
| Thu 23 | 0 | 0.0 | 78 ms | 0 |
| Fri 01 | 0 | 0.0 | 142 ms | 0 |
| Fri 03 | 0 | 0.0 | 358 ms | 0 |
| Fri 05 | 0 | 0.0 | 107 ms | 0 |
| Fri 07 | 0 | 0.0 | 159 ms | 0 |
| Fri 09 | 0 | 0.0 | 114 ms | 0 |
| Fri 11 | 0 | 0.0 | 121 ms | 0 |
| Fri 13 | 0 | 0.0 | 66 ms | 0 |
| Fri 15 | 0 | 0.0 | 159 ms | 0 |
| Fri 17 | 0 | 0.0 | 73 ms | 0 |
| Fri 19 | 0 | 0.0 | 246 ms | 0 |
| Fri 21 | 0 | 0.0 | 90 ms | 0 |
| Fri 23 | 0 | 0.0 | 306 ms | 0 |
Reliability
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.
Embed this status: free live Instruqt badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Instruqt yet. Outages of 10 minutes or more get their own page here.
Having trouble with Instruqt?
One report per service every 10 minutes from this network. No account.
Follow Instruqt
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.
About Instruqt
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: 157 ms average, 27–358 ms range across 13 successful checks.
Questions
Is Instruqt down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Instruqt last down?
We have not recorded a public Instruqt incident since monitoring began 7 days ago.
What is Instruqt's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Instruqt respond?
157 ms on average over the last 24 hours (27–358 ms).
Does Instruqt have an official status page?
Yes, at https://status.instruqt.com.
Instruqt not working for me but the status is fine. What now?
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.