User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
internetcomputer.org · Cloud & developer
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 33 min ago. Last stored result reached it in 578 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 10 | 0 | 0.0 | 635 ms | 0 |
| Mon 12 | 0 | 0.0 | 498 ms | 0 |
| Mon 14 | 0 | 0.0 | 669 ms | 0 |
| Mon 17 | 0 | 0.0 | 946 ms | 0 |
| Mon 19 | 0 | 0.0 | 401 ms | 0 |
| Mon 21 | 0 | 0.0 | 386 ms | 0 |
| Mon 23 | 0 | 0.0 | 610 ms | 0 |
| Tue 01 | 0 | 0.0 | 458 ms | 0 |
| Tue 03 | 0 | 0.0 | 698 ms | 0 |
| Tue 05 | 0 | 0.0 | 414 ms | 0 |
| Tue 07 | 0 | 0.0 | 575 ms | 0 |
| Tue 09 | 0 | 0.0 | 554 ms | 0 |
| Tue 12 | 0 | 0.0 | 379 ms | 0 |
| Tue 14 | 0 | 0.0 | 1350 ms | 0 |
| Tue 16 | 0 | 0.0 | 449 ms | 0 |
| Tue 18 | 0 | 0.0 | 792 ms | 0 |
| Tue 21 | 0 | 0.0 | 587 ms | 0 |
| Tue 23 | 0 | 0.0 | 1034 ms | 0 |
| Wed 01 | 0 | 0.0 | 499 ms | 0 |
| Wed 03 | 0 | 0.0 | 704 ms | 0 |
| Wed 05 | 0 | 0.0 | 644 ms | 0 |
| Wed 08 | 0 | 0.0 | 601 ms | 0 |
| Wed 10 | 0 | 0.0 | 635 ms | 0 |
| Wed 12 | 0 | 0.0 | 738 ms | 0 |
| Wed 14 | 0 | 0.0 | 937 ms | 0 |
| Wed 16 | 0 | 0.0 | 480 ms | 0 |
| Wed 19 | 0 | 0.0 | 420 ms | 0 |
| Wed 21 | 0 | 0.0 | 548 ms | 0 |
| Wed 23 | 0 | 0.0 | 637 ms | 0 |
| Thu 01 | 0 | 0.0 | 535 ms | 0 |
| Thu 03 | 0 | 0.0 | 424 ms | 0 |
| Thu 05 | 0 | 0.0 | 578 ms | 0 |
| Thu 07 | 0 | 0.0 | 754 ms | 0 |
| Thu 09 | 0 | 0.0 | 616 ms | 0 |
| Thu 11 | 0 | 0.0 | 612 ms | 0 |
| Thu 13 | 0 | 0.0 | 645 ms | 0 |
| Thu 16 | 0 | 0.0 | 663 ms | 0 |
| Thu 18 | 0 | 0.0 | 386 ms | 0 |
| Thu 20 | 0 | 0.0 | 425 ms | 0 |
| Thu 22 | 0 | 0.0 | 833 ms | 0 |
| Fri 00 | 0 | 0.0 | 716 ms | 0 |
| Fri 02 | 0 | 0.0 | 1843 ms | 0 |
| Fri 04 | 0 | 0.0 | 323 ms | 0 |
| Fri 05 | 0 | 0.0 | 397 ms | 0 |
| Fri 07 | 0 | 0.0 | 654 ms | 0 |
| Fri 09 | 0 | 0.0 | 545 ms | 0 |
| Fri 11 | 0 | 0.0 | 737 ms | 0 |
| Fri 13 | 0 | 0.0 | 578 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 InternetComputer 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 InternetComputer goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send InternetComputer alerts to Slack, Discord or a webhook — free.
We track InternetComputer (internetcomputer.org) as part of the Cloud & developer group. Sovereign serverless cloud for AIware apps, empowering agentic nations, enterprises, and people — created by an open, mathematical network
InternetComputer publishes an official status page at status.internetcomputer.org; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 658 ms average, 323–1843 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 InternetComputer incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
658 ms on average over the last 24 hours (323–1843 ms).
Yes, at https://status.internetcomputer.org.
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 InternetComputer here at once, the problem is on InternetComputer'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 InternetComputer. 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.