User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
inspectlet.com · Cloud & developer
Is Inspectlet 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 → inspectlet.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 276 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 272 ms | 0 |
| Mon 14 | 0 | 0.0 | 162 ms | 0 |
| Mon 17 | 0 | 0.0 | 187 ms | 0 |
| Mon 19 | 0 | 0.0 | 209 ms | 0 |
| Mon 21 | 0 | 0.0 | 144 ms | 0 |
| Mon 23 | 0 | 0.0 | 287 ms | 0 |
| Tue 01 | 0 | 0.0 | 189 ms | 0 |
| Tue 03 | 0 | 0.0 | 170 ms | 0 |
| Tue 05 | 0 | 0.0 | 80 ms | 0 |
| Tue 07 | 0 | 0.0 | 178 ms | 0 |
| Tue 09 | 0 | 0.0 | 279 ms | 0 |
| Tue 12 | 0 | 0.0 | 255 ms | 0 |
| Tue 14 | 0 | 0.0 | 266 ms | 0 |
| Tue 16 | 0 | 0.0 | 208 ms | 0 |
| Tue 18 | 0 | 0.0 | 226 ms | 0 |
| Tue 21 | 0 | 0.0 | 186 ms | 0 |
| Tue 23 | 0 | 0.0 | 200 ms | 0 |
| Wed 01 | 0 | 0.0 | 240 ms | 0 |
| Wed 03 | 0 | 0.0 | 245 ms | 0 |
| Wed 05 | 0 | 0.0 | 291 ms | 0 |
| Wed 08 | 0 | 0.0 | 154 ms | 0 |
| Wed 10 | 0 | 0.0 | 67 ms | 0 |
| Wed 12 | 0 | 0.0 | 184 ms | 0 |
| Wed 14 | 0 | 0.0 | 191 ms | 0 |
| Wed 16 | 0 | 0.0 | 237 ms | 0 |
| Wed 19 | 0 | 0.0 | 40 ms | 0 |
| Wed 21 | 0 | 0.0 | 291 ms | 0 |
| Wed 23 | 0 | 0.0 | 244 ms | 0 |
| Thu 01 | 0 | 0.0 | 257 ms | 0 |
| Thu 03 | 0 | 0.0 | 192 ms | 0 |
| Thu 05 | 0 | 0.0 | 259 ms | 0 |
| Thu 07 | 0 | 0.0 | 192 ms | 0 |
| Thu 09 | 0 | 0.0 | 178 ms | 0 |
| Thu 11 | 0 | 0.0 | 269 ms | 0 |
| Thu 13 | 0 | 0.0 | 206 ms | 0 |
| Thu 15 | 0 | 0.0 | 200 ms | 0 |
| Thu 18 | 0 | 0.0 | 222 ms | 0 |
| Thu 20 | 0 | 0.0 | 171 ms | 0 |
| Thu 22 | 0 | 0.0 | 163 ms | 0 |
| Fri 00 | 0 | 0.0 | 253 ms | 0 |
| Fri 02 | 0 | 0.0 | 279 ms | 0 |
| Fri 04 | 0 | 0.0 | 213 ms | 0 |
| Fri 06 | 0 | 0.0 | 242 ms | 0 |
| Fri 08 | 0 | 0.0 | 254 ms | 0 |
| Fri 10 | 0 | 0.0 | 164 ms | 0 |
| Fri 12 | 0 | 0.0 | 233 ms | 0 |
| Fri 14 | 0 | 0.0 | 60 ms | 0 |
| Fri 16 | 0 | 0.0 | 276 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Inspectlet 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 Inspectlet yet. Outages of 10 minutes or more get their own page here.
Having trouble with Inspectlet?
One report per service every 10 minutes from this network. No account.
Follow Inspectlet
Get an email when Inspectlet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Inspectlet alerts to Slack, Discord or a webhook — free.
About Inspectlet
We track Inspectlet (inspectlet.com) as part of the Cloud & developer group. Inspectlet records videos of your visitors as they use your site, allowing you to see everything they do. See every mouse movement, scroll, click, and keypress on your site. Forget traditional analytics. You never need to wonder how exactly people are using your site again.
Inspectlet publishes an official status page at status.inspectlet.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 210 ms average, 60–279 ms range across 11 successful checks.
Questions
Is Inspectlet down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Inspectlet last down?
We have not recorded a public Inspectlet incident since monitoring began 8 days ago.
What is Inspectlet's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Inspectlet respond?
210 ms on average over the last 24 hours (60–279 ms).
Does Inspectlet have an official status page?
Yes, at https://status.inspectlet.com.
Inspectlet 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Inspectlet here at once, the problem is on Inspectlet'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 Inspectlet. 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.