User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Email Support Temporarily Unavailable – Microsoft Outlook Outage | Backbone link down between Paris - frstd1 & Rotterdam - nlrtm1 | Backbone link down between São Paulo - brcoa1...
Source: the vendor's status page · We are not affiliated with i3Dnet.
Estimated fix: Not enough i3Dnet history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–10 h; 81 outages).
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.
Our checks can't reach i3Dnet right now
i3Dnet is blocking or timing out our automated checks, so we can't test it directly. We still count user reports and watch the official status page.
Last checked 8 min ago. Last stored result reached it in 49 ms.
Critical incident
Email Support Temporarily Unavailable – Microsoft Outlook Outage | Backbone link down between Paris - frstd1 & Rotterdam - nlrtm1 | Backbone link down between São Paulo - brcoa1 & São Paulo - brbri1 | Backbone link down between Dubai - aedxb1 & Milan - itmil1 Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 189 ms | 0 |
| Mon 21 | 0 | 0.0 | 183 ms | 0 |
| Mon 23 | 0 | 0.0 | 88 ms | 0 |
| Tue 01 | 0 | 0.0 | 35 ms | 0 |
| Tue 03 | 0 | 0.0 | 150 ms | 0 |
| Tue 05 | 0 | 0.0 | 112 ms | 0 |
| Tue 07 | 0 | 0.0 | 102 ms | 0 |
| Tue 09 | 0 | 0.0 | 15 ms | 0 |
| Tue 12 | 0 | 0.0 | 59 ms | 0 |
| Tue 14 | 0 | 0.0 | 80 ms | 0 |
| Tue 16 | 0 | 0.0 | 35 ms | 0 |
| Tue 18 | 0 | 0.0 | 173 ms | 0 |
| Tue 20 | 0 | 0.0 | 98 ms | 0 |
| Tue 23 | 0 | 0.0 | 87 ms | 0 |
| Wed 01 | 0 | 0.0 | 69 ms | 0 |
| Wed 03 | 0 | 0.0 | 130 ms | 0 |
| Wed 05 | 0 | 0.0 | 249 ms | 0 |
| Wed 08 | 0 | 0.0 | 105 ms | 0 |
| Wed 10 | 0 | 0.0 | 60 ms | 0 |
| Wed 12 | 0 | 0.0 | 83 ms | 0 |
| Wed 14 | 0 | 0.0 | 48 ms | 0 |
| Wed 16 | 0 | 0.0 | 133 ms | 0 |
| Wed 18 | 0 | 0.0 | 171 ms | 0 |
| Wed 21 | 0 | 0.0 | 49 ms | 0 |
| Wed 23 | 0 | 0.0 | 102 ms | 0 |
| Thu 01 | 0 | 0.0 | 115 ms | 0 |
| Thu 03 | 0 | 0.0 | 64 ms | 0 |
| Thu 05 | 0 | 0.0 | 184 ms | 0 |
| Thu 07 | 0 | 0.0 | 142 ms | 0 |
| Thu 09 | 0 | 0.0 | 164 ms | 0 |
| Thu 11 | 0 | 0.0 | 45 ms | 0 |
| Thu 13 | 0 | 0.0 | 85 ms | 0 |
| Thu 15 | 0 | 0.0 | 58 ms | 0 |
| Thu 18 | 0 | 0.0 | 95 ms | 0 |
| Thu 20 | 0 | 0.0 | 179 ms | 0 |
| Thu 21 | 0 | 0.0 | 38 ms | 0 |
| Thu 23 | 0 | 0.0 | 178 ms | 0 |
| Fri 01 | 0 | 0.0 | 56 ms | 0 |
| Fri 04 | 0 | 0.0 | 84 ms | 0 |
| Fri 06 | 0 | 0.0 | 35 ms | 0 |
| Fri 08 | 0 | 0.0 | 150 ms | 0 |
| Fri 09 | 0 | 0.0 | 92 ms | 0 |
| Fri 11 | 0 | 0.0 | 120 ms | 0 |
| Fri 13 | 0 | 0.0 | 124 ms | 0 |
| Fri 15 | 0 | 0.0 | 58 ms | 0 |
| Fri 17 | 0 | 0.0 | 134 ms | 0 |
| Fri 18 | 0 | 0.0 | 114 ms | 0 |
| Fri 20 | 0 | 0.0 | 49 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.
MCOM-503 [Cooling Maintenance] Cooling Maintenance - Rotterdam – November 9, 2026
Maintenance is now in progress
[Infrastructure Maintenance] Server Migration - Phase 5 - Dallas - November 13, 2026 - MCOM-518
Maintenance is now in progress
MCOM-534 | [Emergency Power Maintenance] UPS Maintenance - Newark, USA – November 14th, 2026
Dear Client, We would like to notify you of upcoming vendor power maintenance activities that will affect services in our Newark datacenter. The vendor power maintenance has been scheduled for November 14th, 2026. Location: Newark, USA Schedule: Start time:November 14, 2026, 12:…
MCOM-519 [Infrastructure Maintenance] Server Migration - Phase 6 - Dallas – November 16, 2026
We would like to notify you of upcoming infrastructure maintenance activities that will affect services in our Dallas datacenter. The infrastructure maintenance has been scheduled for November 16, 2026. Location Dallas, The United States Schedule Start time: November 16, 2026, 1…
MCOM-520 | [Infrastructure Maintenance] Server Migration - Phase 7 - Dallas – November 17, 2026
We would like to notify you of upcoming infrastructure maintenance activities that will affect services in our Dallas datacenter. The infrastructure maintenance has been scheduled for November 17, 2026. Location Dallas, The United States Schedule Start time: November 17, 2026, 1…
MCOM-521 | [Infrastructure Maintenance] Server Migration - Phase 8 - Dallas – November 18, 2026
We would like to notify you of upcoming infrastructure maintenance activities that will affect services in our Dallas datacenter. The infrastructure maintenance has been scheduled for November 18, 2026. Location Dallas, The United States Schedule Start time: November 18, 2026, 1…
MCOM-522 | [Infrastructure Maintenance] Server Migration - Phase 9 - Dallas – November 19, 2026
We would like to notify you of upcoming infrastructure maintenance activities that will affect services in our Dallas datacenter. The infrastructure maintenance has been scheduled for November 19, 2026. Location Dallas, The United States Schedule Start time: November 19, 2026, 1…
MCOM-523 | [Infrastructure Maintenance] Server Migration - Phase 10 - Dallas – November 20, 2026
We would like to notify you of upcoming infrastructure maintenance activities that will affect services in our Dallas datacenter. The infrastructure maintenance has been scheduled for November 20, 2026. Location Dallas, The United States Schedule Start time: November 20, 2026, 1…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
One report per service every 10 minutes from this network. No account.
Get an email when i3Dnet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send i3Dnet alerts to Slack, Discord or a webhook — free.
i3Dnet, at i3d.net, is one of the Cloud & developer services we monitor. i3D.net removes the trade‑offs between cloud and self‑managed infrastructure with a managed private cloud and global network built for consistent high performance.
i3Dnet publishes an official status page at status.i3d.net; 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. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 95 ms average, 35–178 ms range across 13 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Email Support Temporarily Unavailable – Microsoft Outlook Outage | Backbone link down between Paris - frstd1 & Rotterdam - nlrtm1 | Backbone link down between São Paulo - brcoa1...
The most recent public incident we recorded started 2026-11-06 and lasted 3 days 16 h. 1 incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
95 ms on average over the last 24 hours (35–178 ms).
Yes, at https://status.i3d.net.
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 i3Dnet here at once, the problem is on i3Dnet'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 i3Dnet. 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.