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

Stickied Incidents

Tuesday 3rd, March 2026

ONE Control Panel one.i3d.net Portal Outage

Access has been restored on One Portal (one.i3d.net). We apologize for any inconvenience caused by this.

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/

Past Incidents

Saturday 28th, May 2022

US: Chicago Backbone link between our Seattle and Chicago datacenters flapping

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

The cause of the incident is currently: Unknown

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 Seattle and Chicago 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. The vendor replaced the faulty card and services are fully restored.

  • The network vendor identified a broken linecard to be the cause of this incident. A new card has been picked-up and the engineer will arrive on location in ~3,5hours (16:00 UTC).

  • Friday 27th, May 2022

    PL: Warsaw 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 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. Given the ongoing situation in this region, we are unsure about the speed of repair for this incident and are expecting this to take longer than usual.

    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.

  • Traffic has been restored after the vendor located and repaired a fiber cut. As we have no official hands off yet, we will keep monitoring the link closely for now.

  • UAE: Dubai Backbone link between our Dubai and Mumbai datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Dubai and Mumbai datacenters down.

    The cause of the incident is currently: Unknown

    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 Dubai and Mumbai datacenters, impact could be visible in the form of 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.

  • Link is confirmed to be running again. RFO requested from Vendor.

  • Thursday 26th, May 2022

    US: Ashburn Backbone link between our Atlanta and Ashburn datacenters down

    At this moment we are experiencing problems with: Backbone link between our Atlanta and Ashburn datacenters down.

    The cause of the incident is currently: Unknown

    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 Atlanta and Ashburn datacenters, impact could be visible in the form of 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.

  • Link is restored

  • Wednesday 25th, May 2022

    GB: London 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 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: Unknown.

    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.

  • Tuesday 24th, May 2022

    IT: Milan Incident Milan datacenter

    At this moment we are experiencing problems with: Incident in our Milan datacenter.

    The cause of the incident is currently: Unknown

    Estimated time of repair: No ETR available

    Impact: We briefly lost connection to our Milan datacenter.

    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.

  • Monday 23rd, May 2022

    HK: Hong Kong Backbone link between our Hong Kong and Tokyo datacenters down

    At this moment we are experiencing problems with: Backbone link between our Hong Kong and Tokyo datacenters.

    The cause of the incident is currently: Unknown

    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: Unknown.

    Impact: Due to the current incident on our backbone link between our Hong Kong and Tokyo 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.

  • Traffic has been restored on the link. As we have no hands off from out vender just yet we will closely monitor this link.

  • This incident is caused by a fiber cut reported by our vendor. The communicated ETR is expected to 14:00 UTC.

  • Sunday 22nd, May 2022

    US: Chicago Backbone link between our Seattle and Chicago datacenters flapping

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

    The cause of the incident is currently: Unknown

    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 Seattle and Chicago 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.

  • DE: Frankfurt Backbone link between our Frankfurt and Rotterdam datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Frankfurt and Rotterdam datacenters*.

    The cause of the incident is currently: Unknown

    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: Unknown

    Impact: Due to the current incident on our backbone link between our Frankfurt and Rotterdam 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.

  • The link is operational again.

  • Our Vendor has located the fiber cut. It is caused by a fire. Cause of Fire unknown.

  • NL: Rotterdam Backbone link between our Paris and Rotterdam datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Paris and Rotterdam datacenters*.

    The cause of the incident is currently: Unknown

    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: Unknown

    Impact: Due to the current incident on our backbone link between our Paris and Rotterdam 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.

  • The link is operational again.

  • Our Vendor has located the fiber cut. It is caused by a fire. Cause of Fire unknown

  • GB: London Backbone link between our London and Rotterdam datacenters down

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

    The cause of the incident is currently: Unknown

    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: Unknown

    Impact: Due to the current incident on our backbone link between our London and Rotterdam 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.

  • The link is operational again

  • Our Vendor has located the fiber cut. It is caused by a fire. Cause of Fire unknown.