i3Dnet logo

Is i3Dnet down?

Minor issues reported

From status.i3d.net · checked 1 minute ago · every 5 minutes

Get alerts for i3Dnet

An email when it goes down, and when it’s back.

As of 03:28 UTC on 12 November 2026, i3Dnet's status page reports minor issues.

Last problem
Going on now
Problems, last 30 days
10 (1 critical)
Typical incident
24 h 3 min
Longest in 90 days
10 days · 19 Oct

Backbone link down between Atlanta - usatl1 & Dallas - usdal3

Issue

Started 7 days ago, affecting Atlanta - usatl1, Dallas - usdal3, Dubai - aedxb1, London - gblon1, Milan - itmil1, Newark - usewr1.

Read the updates on status.i3d.net ↗

Uptime

i3Dnet, last 30 days

6.42 %

100%50%0%
Oct 14 Today

Biggest dip: i3Dnet, 261 h of critical on Oct 19.

Incidents

Started in the last 7 days

0

210
FSSMTWToday

This week Week before

No incidents this week. The last one: i3Dnet, issue on Nov 5.

Recovery

Median time back online

17 h 40 min

10 days0
30 days ago Today

2 of 9 were over within an hour. Each dot is one incident; the dashed line is the median.

Components 74

6 with issues, 2 under maintenance

General Systems 9 parts
  • Email Support
  • i3D.net API
  • i3D.net Portal
  • Nameservers
  • NTP Servers
  • Phone Support
  • Smartdc API
  • Smartdc Portal
  • Ticket Portal (external)
Anti-DDoS 2 parts
  • GLAD
  • GLAD - API
Backup 1 part
  • Acronis backup
Websites 2 parts
  • i3D.net Website
  • Smartdc Website
Datacenters 55 parts
  • Amsterdam - nlams1
  • Amsterdam - nlams2
  • Ashburn - usqas1
  • Ashburn - usqas2
  • Atlanta - usatl1 Issue
  • Bucharest - robuh1
  • Budapest - hubud1
  • Buenos Aires - arbue1
  • Chicago - uschi1
  • Chicago - uschi3
  • Copenhagen - dkcph1
  • Shanghai - cnsgh1
  • Dallas - usdal1
  • Dallas - usdal3 Issue
  • Dubai - aedxb1 Issue
  • Frankfurt - defra1
  • Fujairah - aefjr1
  • Heerlen - nlhen1
  • Hong Kong - hkhkg1
  • Johannesburg - zajnb1
  • Kyiv - uaiev1
  • London - gblon1 Issue
  • Los Angeles - uslax1
  • Madrid - esmad1
  • Milan - itmil1 Issue
  • Montreal - camtr4 Maintenance
  • Montreal - camtr5
  • Montreal - camtr6
  • Mumbai - inbom1
  • Newark - usewr1 Issue
  • Oslo - noosl1
  • Paris - frpar1
  • Paris - frstd1
  • Paris - frmtl1
  • Paris - fravs1
  • Phoenix - usphx1
  • Rotterdam - nlrtm1 Maintenance
  • San Jose - usscz1
  • Santiago - clscl1
  • São Paulo - brbri1
  • São Paulo - brcoa1
  • Seattle - ussea1
  • Singapore - sgsin1
  • Sofia - bgsof1
  • Stockholm - sesto1
  • Stockholm - sesto2
  • Sydney - ausyd2
  • Tokyo - jptyo1
  • Tokyo - jptyo2
  • Tokyo - jptyo3
  • Toronto - cator1
  • Vienna - atvie1
  • Warsaw - plwaw1
  • Warsaw - plwaw2
  • Zurich - chzrh1
CDN 2 parts
  • CDN
  • CDN - API
Compute 2 parts
  • FlexMetal
  • FlexVM
One Deployment Platform 1 part
  • One Deployment Platform

Last 90 days

13 incidents in 47 days tracked · no reported issues 16.2% of the time · typical incident 24 h 3 min

Aug 15 Today (UTC)

Recent incidents

Times in UTC

  1. Maintenance
    [Power Maintenance] Vendor Power Maintenance - Pointe-Claire – October 26-November 12, 2026 - MCOM-500 3 h 50 min
  2. Issue
    Backbone link down between Ashburn - usqas1 & Atlanta - usatl1 18 h
  3. Maintenance
    [Power Maintenance] Vendor Power Maintenance - Pointe-Claire – October 26-November 12, 2026 - MCOM-500 2 h 55 min
  4. Issue
    Dallas - usdal3 and Phoenix - usphx1 are degraded 20 min
  5. Maintenance
    [Power Maintenance] Vendor Power Maintenance - Pointe-Claire – October 26-November 12, 2026 - MCOM-500 9 h 45 min
  6. Issue
    Backbone link down between Buenos Aires - arbue1 & Santiago - clscl1 17 h 40 min
  7. Maintenance
    [Power Maintenance] Vendor Power Maintenance - Pointe-Claire – October 26-November 12, 2026 - MCOM-500 2 days
  8. Issue
    Backbone link down between Buenos Aires - arbue1 & São Paulo - brbri1 3 h 10 min
  9. Maintenance
    [Power Maintenance] Vendor Power Maintenance - Pointe-Claire – October 26-November 12, 2026 - MCOM-500 35 min
  10. Issue
    Backbone link down between Bucharest - robuh1 & Kyiv - uaiev1 16 h 13 min
All incidents on status.i3d.net ↗

Where this comes from

Stackpulse reads i3Dnet’s official status page at status.i3d.net every 5 minutes and keeps 90 days of what changed. We don’t test i3Dnet ourselves, so a problem shows here once i3Dnet reports it.

Stackpulse isn’t affiliated with i3Dnet. Names and logos belong to their owners.

For agents and scripts

The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.