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
[Cooling Maintenance] Water Cooling Pump Maintenance - Rotterdam – May 4, 2026

Dear Client,

We would like to notify you of upcoming cooling maintenance activities that will affect services in our Rotterdam datacenter. The water cooling pump maintenance has been scheduled for May 4, 2026.

Location: Rotterdam, The Netherlands

Schedule: Start time: May 4, 2026, 07:00 UTC End time: May 4, 2026, 15:30 UTC Planned impact: No impact (see below for details)

Reason for this maintenance: Our vendor will be performing a maintenance on the water pumps in our Rotterdam datacenter.

Expected impact: No Impact: No impact is expected, as maintenance activities will be performed on each water pump individually, with the team waiting for each pump to return to operation before proceeding to the next.

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/

[Power Maintenance] Generator On-load Test - Rotterdam – May 5, 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 May 5, 2026

Location: Rotterdam, The Netherlands

Original window: Start time: May 5, 2026, 06:00 UTC End time: May 5, 2026, 09:00 UTC Planned impact: No impact (see below for details)

Reason for this maintenance: To ensure the proper functioning of our power infrastructure, our generators will undergo an on-load test run.

Expected impact: No Impact: No impact is expected for this maintenance, as there is no outage for the power systems. Customers in the datacenter at the time of the maintenance can hear loud noises.

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/

Past Incidents

Friday 16th, July 2021

No incidents reported

Thursday 15th, July 2021

No incidents reported

Wednesday 14th, July 2021

UA: Kyiv Backbone link between Kiev and Moscow is down

At this moment we are experiencing problems with: Backbone link between our Kiev and Moscow 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 Kiev and Moscow 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 issue has been resolved.

    • US: Dallas Backbone link between Atlanta and Dallas is down

    At this moment we are experiencing problems with: Backbone link between our Atlanta and Dallas 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 Atlanta 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 reports that this issue has been resolved.

    • Tuesday 13th, July 2021

    UA: Kyiv Backbone link between Kiev and Warsaw is 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.

    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 issue has been resolved.

    • Backbone link between Moscow and Warsaw is down

    At this moment we are experiencing problems with: Backbone link between our Moscow 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.

    Impact: Due to the current incident on our backbone link between our Moscow 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 issue has been resolved.

    • Monday 12th, July 2021

    US: Chicago Backbone link between Chicago and Dallas is 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 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.

  • This issue has been resolved.

    • Sunday 11th, July 2021

    US: Newark Backbone link between Montreal and Newark is 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 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 is resolved

    • US: Dallas Backbone link between our Atlanta and Dallas datacenters down

    At this moment we are experiencing problems with: Backbone link between our Atlanta and Dallas 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 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.

  • This incident has been resolved.

  • We can see traffic restoring to normal levels but we have not heard back from our vendor about a fix yet. We will be waiting on an update from our vendor before fully closing this incident.

    • US: Chicago Backbone link between our Chicago and Toronto datacenters down

    At this moment we are experiencing problems with: Backbone link between our Chicago and Toronto 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 Chicago and Toronto 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.

    • Saturday 10th, July 2021

    Backbone link between our Moscow and Kyiv datacenters down

    At this moment we are experiencing problems with: Backbone link between our Moscow and Kyiv 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 Moscow and Kyiv 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