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 32 min 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 |
|---|---|---|---|---|
| Wed 05 | 0 | 0.0 | 49 ms | 0 |
| Wed 07 | 0 | 0.0 | 47 ms | 0 |
| Wed 09 | 0 | 0.0 | 67 ms | 0 |
| Wed 11 | 0 | 0.0 | 85 ms | 0 |
| Wed 13 | 0 | 0.0 | 102 ms | 0 |
| Wed 15 | 0 | 0.0 | 78 ms | 0 |
| Wed 18 | 0 | 0.0 | 72 ms | 0 |
| Wed 20 | 0 | 0.0 | 76 ms | 0 |
| Wed 22 | 0 | 0.0 | 91 ms | 0 |
| Thu 00 | 0 | 0.0 | 60 ms | 0 |
| Thu 02 | 0 | 0.0 | 61 ms | 0 |
| Thu 04 | 0 | 0.0 | 73 ms | 0 |
| Thu 06 | 0 | 0.0 | 71 ms | 0 |
| Thu 08 | 0 | 0.0 | 57 ms | 0 |
| Thu 11 | 0 | 0.0 | 91 ms | 0 |
| Thu 13 | 0 | 0.0 | 71 ms | 0 |
| Thu 15 | 0 | 0.0 | 39 ms | 0 |
| Thu 17 | 0 | 0.0 | 87 ms | 0 |
| Thu 19 | 0 | 0.0 | 52 ms | 0 |
| Thu 21 | 0 | 0.0 | 34 ms | 0 |
| Thu 23 | 0 | 0.0 | 52 ms | 0 |
| Fri 01 | 0 | 0.0 | 34 ms | 0 |
| Fri 03 | 0 | 0.0 | 21 ms | 0 |
| Fri 05 | 0 | 0.0 | 39 ms | 0 |
| Fri 07 | 0 | 0.0 | 55 ms | 0 |
| Fri 08 | 0 | 0.0 | 27 ms | 0 |
| Fri 11 | 0 | 0.0 | 25 ms | 0 |
| Fri 12 | 0 | 0.0 | 22 ms | 0 |
| Fri 14 | 0 | 0.0 | 38 ms | 0 |
| Fri 16 | 0 | 0.0 | 41 ms | 0 |
| Fri 18 | 0 | 0.0 | 102 ms | 0 |
| Fri 20 | 0 | 0.0 | 73 ms | 0 |
| Fri 22 | 0 | 0.0 | 45 ms | 0 |
| Sat 00 | 0 | 0.0 | 68 ms | 0 |
| Sat 02 | 0 | 0.0 | 35 ms | 0 |
| Sat 04 | 0 | 0.0 | 39 ms | 0 |
| Sat 06 | 0 | 0.0 | 24 ms | 0 |
| Sat 08 | 0 | 0.0 | 40 ms | 0 |
| Sat 11 | 0 | 0.0 | 30 ms | 0 |
| Sat 14 | 0 | 0.0 | 33 ms | 0 |
| Sat 16 | 0 | 0.0 | 44 ms | 0 |
| Sat 18 | 0 | 0.0 | 18 ms | 0 |
| Sat 21 | 0 | 0.0 | 41 ms | 0 |
| Sat 23 | 0 | 0.0 | 17 ms | 0 |
| Sun 01 | 0 | 0.0 | 63 ms | 0 |
| Sun 04 | 0 | 0.0 | 35 ms | 0 |
| Sun 06 | 0 | 0.0 | 99 ms | 0 |
| Sun 08 | 0 | 0.0 | 27 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 10 days of data so far, so the 90-day numbers fill in over time.
No outages on record for OctoEverywhere 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 OctoEverywhere goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track OctoEverywhere (octoeverywhere.com) as part of the AI group. Cloud empower your OctoPrint, Klipper, Bambu Lab, & Elegoo 3D printers with free, secure, and unlimited remote access, next-gen AI failure detection, notifications, iPhone and Android apps, live streaming, and more!
OctoEverywhere publishes an official status page at status.octoeverywhere.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 38 ms average, 10–99 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public OctoEverywhere incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
38 ms on average over the last 24 hours (10–99 ms).
Yes, at https://status.octoeverywhere.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 OctoEverywhere here at once, the problem is on OctoEverywhere'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 OctoEverywhere. 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.