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
[Power Maintenance] Generator Maintenance - Rotterdam – June 9, 2026

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 June 9, 2026.

Location: Rotterdam, The Netherlands

Schedule: Start time: June 9, 2026, 06:00 UTC End time: June 9, 2026, 09:00 UTC Planned impact: No impact (see below for details)

Reason for this maintenance: We are conducting tests of our generators to ensure ongoing reliability and compliance.

Expected impact: The generator tests will be done off-load, services will remain fully supported by both the grid and generators. Some noise from the generators can be heard when present in the datacenter

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/

[API Maintenance] ONE API Migration - June 15, 2026

Dear Customer,

We would like to notify you of upcoming API maintenance activities that will affect the ONE API. The API maintenance has been scheduled for June 15, 2026.

Schedule: Start time: June 15, 2026, 09:00 UTC End time: June 15, 2026, 11:00 UTC Planned impact: Impact expected (see below for details)

Reason for this maintenance: We will be migrating and upgrading our ONE portal backend. This migration is part of our ongoing effort to enhance performance, scalability, and long-term reliability. Migrations and upgrades will be carried subsequently to minimise degradation in service and ensure a seamless transition.

Expected impact: Degradation: Our ONE API will remain available while migrating, but brief disruptions are expected. Customers using the ONE API will experience quick disconnects, and some active connections may have HTTP requests fail briefly. In the unlikely event of a critical failure we will roll back to the previous stable version.

Services impacted: One.i3d.net Api.i3d.net

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/

[Cooling Maintenance] Cooling Maintenance - Rotterdam – June 22, 2026

Dear Client,

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

Location: Rotterdam, The Netherlands

Schedule: Start time: June 22, 2026, 05:00 UTC End time: July 10, 2026, 14:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: We will be performing a cooling maintenance on our cooling units to continue reliability and stability.

Expected impact:

Reduced redundancy: No impact expected, but there will be reduced redundancy during the maintenance window. There maybe some small temperature fluctuations as the units are being worked on.

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/

[Network Maintenance] Switch Software Upgrade - Rotterdam - June 24, 2026

Dear Client,

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

Location: Rotterdam, The Netherlands

Schedule: Start time: June 24, 2026, 03:00 UTC End time: June 24, 2026, 06:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: The maintenance is required in preparation for an upgrade to a new switch firmware. This will enhance system reliability and ensure consistent performance moving forward.

Expected impact: Reduced redundancy: No impact expected, but there will be reduced redundancy during the maintenance window.

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] Yearly Generator Maintenance - Rotterdam – July 7, 2026

We would like to notify you of upcoming backup generator maintenance activities. This maintenance will not affect services in our Rotterdam datacenter. The maintenance has been scheduled for July 7 until July 17, 2026.

Location: Rotterdam, The Netherlands

Schedule: Start time: July 7, 2026, 05:00 UTC End time: July 17, 2026, 14:00 UTC Planned impact: No impact (see below for details)

Reason for this maintenance: To ensure the proper functioning of our power infrastructure, our backup generators will undergo preventative maintenance.

Expected impact: No Impact: No impact is expected for this maintenance, as regular power systems will not be touched. Customers in the datacenter at the time of the maintenance could 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

Sunday 4th, December 2022

No incidents reported

Saturday 3rd, December 2022

No incidents reported

Friday 2nd, December 2022

US: Chicago 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 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 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 incident has been resolved. The fiber cut was repaired and vendor is hands off.

  • A fiber cut has been identified.

    • US: Los Angeles Backbone link between our Dallas and Los Angeles datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Dallas and Los Angeles 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 Dallas and Los Angeles 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 fiber was repaired, thus restoring all services.

  • A fiber cut has been found.

    • JP: Tokyo Network incident in our Tokyo Datacenter

    At this moment, we are experiencing problems with: our network in our Tokyo Datacenter

    The cause of the incident is currently: Known

    We have taken the following actions to resolve the incident: Our engineers are working on resolving this issue. Follow the updates to this incident for more information.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our network in our Tokyo Datacenter, 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 engineer rebooted the devices, and their service is restored.

  • This incident is caused by a bug with the brocade switches. The switch needs to be rebooted, after it run for a long updtime. The reason why these devices all failed at the same time, is because they have been upgraded at once, and the uptime is the same.

  • Our engineers have located the cause of this incident and are working hard to restore service for the affected racks.

    • PL: Warsaw Backbone link between our Warsaw and Moscow datacenters down

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

    The cause of the incident is currently: There was a fiber cut in the link between Warsaw and Moscow

    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 Warsaw 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.

  • The link has been restored and remained stable.

  • A fiber cut has been located in the section of Warsaw/Malkinia.

    A team is now working on this issue. You will be updated shortly.

    • Thursday 1st, December 2022

    No incidents reported

    Wednesday 30th, November 2022

    Backbone link between our Saint Petersburg and Moscow datacenters is down

    At this moment we are experiencing problems with: Backbone link between our Saint Petersburg and Moscow datacenters is down.

    The cause of the incident is currently: Unknown

    We have taken the following actions to resolve the incident: We have reached out to our vendor for more information.

    Estimated time of repair: No ETR at this time.

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

  • Our link has been restored. the maintenance has been completed.

  • Our vendor is performing maintenance.

    • IT: Milan Backbone link between our Milan and Bucharest datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Milan and Bucharest 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 Milan and Bucharest 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 identified a fiber cut and the cut has been repaired. The link has been restored.

    • Backbone link between our Saint Petersburg and Moscow datacenters is down

    At this moment we are experiencing problems with: Backbone link between our Saint Petersburg and Moscow datacenters is down.

    The cause of the incident is currently: Unknown

    We have taken the following actions to resolve the incident: We have reached out to our vendor for more information.

    Estimated time of repair: No ETR at this time.

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

  • Our link has remained stable.

  • Our link has restored. Awaiting to hear from our vendor.

    • Tuesday 29th, November 2022

    SG: Singapore Backbone link between our Paris and Singapore datacenters down

    At this moment we are experiencing problems with: Backbone link between our Paris and Singapore 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 Paris and Singapore 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 link has remained stable.

  • Link has been restored. We are waiting for hands-off

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

    At this moment, we are experiencing problems with: Backbone link between our Paris and Dubai 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 Dubai 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 link has remained stable.

  • Link is restored. Waiting for hands off

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

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

  • We have received a hands-off.

  • Link is back up. We are waiting for hands-off

    • IT: Milan Backbone link between our Milan and Bucharest datacenters down

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

    • Monday 28th, November 2022

    No incidents reported