Some systems are experiencing issues

About This Site

Welcome to the status page of i3D.net. Any known issues affecting any of our services will be tracked on this page. Potential impact may vary from customer to customer depending on the systems or services impacted.

All times used on this page will be in the UTC timezone.

You can subscribe to receive an email as soon as a status update has been published. You may consult our Privacy Statement for more information on the processing of your personal data.

Please reach out to our support team through our website or support@i3d.net if you have any questions or need help.

We are also available 24/7 by phone on the following phone numbers:

+31 (0)10 890 00 70

1-800-482-6910

Maintenance
[Infrastructure Maintenance] Cooling Maintenance - Heerlen – March 23, 2026

We would like to notify you of upcoming cooling maintenance activities that will affect services in our Heerlen datacenter. The cooling maintenance has been scheduled for March 23, 2026.

Location:

Heerlen, The Netherlands

Schedule:

Start time: March 23, 2026, 07:00 UTC

End time: March 23, 2026, 16:00 UTC

Planned impact: Reduced redundancy (see below for details)

Reason for Maintenance:

We will perform preventive maintenance on the cooling systems to ensure continued reliability and safe operation.

Expected Impact: During the maintenance the cooling units will be maintained one by one. Cooling will remain available, but redundancy will be temporarily reduced while the work is carried out.

Support: Our support department will be open during the maintenance. More details about how you can contact our support can be found here: https://i3d.net/support/

[Power Maintenance] Busbar Replacement - Rotterdam – March 31, 2026

Dear Client,

We would like to notify you of upcoming power maintenance activities that will affect services in our Rotterdam datacenter. The power maintenance has been scheduled for March 31, 2026.

Location: Rotterdam, The Netherlands

Schedule: Start time: March 31, 2026, 05:00 UTC End time: March 31, 2026, 16:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: The maintenance is required to address a faulty busbar. This critical replacement will enhance system reliability and ensure consistent performance moving forward.

Expected impact: Reduced redundancy: No impact expected but there will be no UPS backup. To ensure there is no impact we will run the generators in sync with the grid.

Support: Our support department will be open during the maintenance. More details about how you can contact our support can be found here: https://i3d.net/support/ You can find maintenance updates and the current situation at https://status.i3d.net/

[Network Maintenance] Router Software Upgrade - Oslo - April 1, 2026

Dear Client,

We would like to notify you of upcoming network maintenance activities that will affect services in our Oslo datacenter. The network maintenance has been scheduled for April 1, 2026.

Location: Oslo, Norway

Schedule: Start time: April 1, 2026, 04:00 UTC End time: April 1, 2026, 07:00 UTC Planned impact: No impact (see below for details)

Reason for this maintenance: We will be performing firmware upgrades on our router(s) to improve quality and ensure long-term reliability.

Expected impact: No Impact: No impact is expected for this maintenance, as the traffic will be routed via alternate paths.

Support: Our support department will be open during the maintenance. More details about how you can contact our support can be found here: https://i3d.net/support/ You can find maintenance updates and the current situation at https://status.i3d.net/

Past Incidents

Saturday 28th, August 2021

No incidents reported

Friday 27th, August 2021

CA: Montreal Backbone link between our Montreal and Newark datacenters down

At this moment we are experiencing problems with: Backbone link between our Montreal and Newark datacenters.

The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

We have taken the following actions to resolve the incident: We are currently monitoring the situation and are in touch with our vendor regarding status updates.

Estimated time of repair: No ETR available at this time.

Impact: Due to the current incident on our backbone link between our Montreal and Newark datacenters, users between these and surrounding regions may experience increased latency.

Support: Our support department is available for more information and personal updates. New updates will be posted here. More details about how you can contact our support can be found here.

Subscribe for the latest updates. You may consult our Privacy Statement for more information on the processing of your personal data.

  • This incident has been resolved.

    • UA: Kyiv Backbone link between our Kiev and Warsaw datacenters down

    At this moment we are experiencing problems with: Backbone link between our Kiev and Warsaw datacenters.

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    We have taken the following actions to resolve the incident: We are currently monitoring the situation and are in touch with our vendor regarding status updates.

    Estimated time of repair: No ETR available at this time.

    Impact: Due to the current incident on our backbone link between our Kiev and Warsaw datacenters, users between these and surrounding regions may experience increased latency.

    Support: Our support department is available for more information and personal updates. New updates will be posted here. More details about how you can contact our support can be found here.

    Subscribe for the latest updates. You may consult our Privacy Statement for more information on the processing of your personal data.

  • This incident has been resolved.

    • Thursday 26th, August 2021

    US: Dallas Backbone link between our Chicago and Dallas datacenters down

    At this moment we are experiencing problems with: Backbone link between our Chicago and Dallas datacenters.

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    We have taken the following actions to resolve the incident: We are currently monitoring the situation and are in touch with our vendor regarding status updates.

    Estimated time of repair: No ETR available at this time.

    Impact: Due to the current incident on our backbone link between our Chicago and Dallas datacenters, users between these and surrounding regions may experience increased latency.

    Support: Our support department is available for more information and personal updates. New updates will be posted here. More details about how you can contact our support can be found here.

    Subscribe for the latest updates. You may consult our Privacy Statement for more information on the processing of your personal data.

  • Our vendor has resolved this incident.

  • Our vendor reports they have identified a fiber cut. Further investigation is required. No ETR provided at this time.

    • CA: Montreal Backbone link between our Montreal and Newark datacenters down

    At this moment we are experiencing problems with: Backbone link between our Montreal and Newark datacenters.

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    We have taken the following actions to resolve the incident: We are currently monitoring the situation and are in touch with our vendor regarding status updates.

    Estimated time of repair: No ETR available at this time.

    Impact: Due to the current incident on our backbone link between our Montreal and Newark datacenters, users between these and surrounding regions may experience increased latency.

    Support: Our support department is available for more information and personal updates. New updates will be posted here. More details about how you can contact our support can be found here.

    Subscribe for the latest updates. You may consult our Privacy Statement for more information on the processing of your personal data.

  • This incident has been resolved by our vendor, the link is back online.

    • US: Newark Backbone link between our London and Newark datacenters down

    At this moment we are experiencing problems with: Backbone link between our London and Newark datacenters.

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    We have taken the following actions to resolve the incident: We are currently monitoring the situation and are in touch with our vendor regarding status updates.

    Estimated time of repair: No ETR available at this time.

    Impact: Due to the current incident on our backbone link between our London and Newark datacenters, users between these and surrounding regions may experience increased latency.

    Support: Our support department is available for more information and personal updates. New updates will be posted here. More details about how you can contact our support can be found here.

    Subscribe for the latest updates. You may consult our Privacy Statement for more information on the processing of your personal data.

  • This incident has been resolved.

  • Field personnel have located the exact point of damage and determined the fiber was damaged due to rats. They are currently devising a repair plan.

  • The fiber technicians tested the fiber and are en route to an alternate location. Field personnel are expected to arrive at the alternate site at approximately 10:30 UTC

  • The outage is due to a fiber cut. A fiber team has been engaged but an ETA is unavailable at this time.

    • Wednesday 25th, August 2021

    No incidents reported

    Tuesday 24th, August 2021

    US: Santa Clara Backbone link between our Santa Clara and Seattle datacenters down

    At this moment we are experiencing problems with: Backbone link between our Santa Clara and Seattle datacenters.

    The cause of the incident is currently: Unknown

    We have taken the following actions to resolve the incident: We have contacted our vendor to investigate this incident.

    Estimated time of repair: No ETR available at this time.

    Impact: Due to the current incident on our backbone link between our Santa Clara and Seattle datacenters, users surrounding these datacenters may experience an increased latency.

    Support: Our support department is available for more information and personal updates. New updates will be posted here. More details about how you can contact our support can be found here.

    Subscribe for the latest updates. You may consult our Privacy Statement for more information on the processing of your personal data.

  • Our vendor has informed us that a device reset has resolved this incident.

  • Our vendor has informed us that they are still investigating the cause of this incident.

  • The link is back online but we have not yet received an update from our vendor. We will be watching this link until we get handsoff from our vendor.

    • Monday 23rd, August 2021

    No incidents reported

    Sunday 22nd, August 2021

    No incidents reported

    Saturday 21st, August 2021

    NL: Amsterdam Backbone link between our Amsterdam and Montréal datacenters down

    At this moment we are experiencing problems with: Backbone link between our Amsterdam and Montréal datacenters.

    The cause of the incident is currently: Known, a train derailment has caused a fiber break.

    We have taken the following actions to resolve the incident: We are currently monitoring the situation and are in touch with our vendor regarding status updates.

    Estimated time of repair: No ETR available at this time.

    Impact: Due to the current incident on our backbone link between our Amsterdam and Montréal datacenters we curently have reduced redundancy and possibly a slightly increased latency.

    Support: Our support department is available for more information and personal updates. New updates will be posted here. More details about how you can contact our support can be found here.

    Subscribe for the latest updates. You may consult our Privacy Statement for more information on the processing of your personal data.

  • The fiber has been restored. Although we have not yet received a final hands-off notification, we are hereby closing this incident.

  • The splicing teams are currently awaiting permission from Canadian National Railway to start work on resolving this incident. At the moment CN Railway is prioritizing freight train traffic which passes too close to the handhole to start work safely. At the moment there we have no ETR.

  • A technician is on-site to work on an alternative solution to restore services by installing a 1km cable to restore services, no ETR.