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] 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] Generator Maintenance - Heerlen – July 3, 2026

Dear Client,

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

Location: Heerlen, The Netherlands

Schedule: Start time: July 3, 2026, 05:00 UTC End time: July 3, 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 generators will undergo a power load test. This is only an inspection and no power outages are planned for this activity.

Expected impact: No Impact: No impact is expected for this maintenance, as there is no outage for the power systems.

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

Wednesday 21st, October 2020

US: Chicago Backbone link between Chicago and Saint Lorent datacenters down

At this moment we are experiencing problems with: Backbone link between Chicago and Saint Lorent 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 have reached out to our vendor for investigation.

Estimated time of repair: Unknown

Impact: Due to the current ongoing incident on our backbone link between our Chicago and Saint Lorent datacenters, users between these and surrounding regions may experience increased latency, although very minimal.

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.

  • Faults have been identified and repaired. Service is restored.

    • Tuesday 20th, October 2020

    No incidents reported

    Monday 19th, October 2020

    US: Santa Clara Santa Clara DC - Ports down

    At this moment we are experiencing problems with: We are seeing multiple ports down in our datacenter in the Santa Clara region.

    The cause of the incident is currently: Early investigations have indicated a possible fiber cut.

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

    Estimated time of repair: Unknown

    Impact: Due to the current ongoing incident in our Santa Clara datacenter, users connecting to this region and surrounding regions may experience increased latency and connection issues.

    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.

  • Repairs have been made and issue is resolved.

  • Temporary repairs are in place and circuit is active. Further repairs will be performed at a later time.

  • Our vendor reports that engineers on site are troubleshooting and making isolation efforts. Currently no ETR is known.

    • Sunday 18th, October 2020

    No incidents reported

    Saturday 17th, October 2020

    JP: Tokyo Backbone link between Tokyo and Singapore datacenters down

    At this moment we are experiencing problems with: Backbone link between our Tokyo 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 have reached out to our vendor for investigation.

    Estimated time of repair: Unknown

    Impact: Due to the current ongoing incident on our backbone link between our Tokyo and Singapore datacenters, users between these and surrounding regions may experience increased latency, although very minimal.

    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 completed the repairs. The backbonelink connection is restored.

  • The cable ship has completed initial splicing. The tentative repair completion date has been changed to February 25.

  • Our vendor has informed us that the cable ship has arrived at the repair ground and is on weather standby this morning due to adverse weather. The tentative repair completion date is expected on 24-Feb.

  • First incident on this backbone link: the repair works have been further pushed back to 12-22 February, pending permits and approval from Malaysian authorities

    Second incident: no update on the repair works.

  • First incident on this backbone link: the repair works have been further pushed back to 5-14 February, pending permits and approval from Japanese authorities.

    Second incident: no update on the repair works.

  • No update on the ETR for the initial incident.

    On January 1, 09:17 a second incident occurred on this submarine cable. The cable fault is located around Singapore and the initial ETR is 'at least 4-5 weeks'. This means that both cable faults need to be repaired before our backbone link between Tokyo and Singapore is restored. The impact of this remains the same, slightly increased latency between our Singapore and Tokyo datacenters.

  • The repair works has been further re-scheduled to January 14-23, 2021.

  • Our vendor has informed us that the tentative repair window is rescheduled to 15 – 20 Jan. 2021, subject to COVID-19 situation and permits approval from Japanese authorities.

  • Our vendor will start work on repairing this submarine cable. The repair window is from December 9 until December 18, subject to COVID-19 situation and permits approval from the Japanese authorities.

  • Our vendor has indicated that this repair is expected to take at least 3-4 weeks depending on the availability of a ship that is able to fix the submarine cable, permits/approvals from maritime authorities, COVID-19 restrictions and sea/weather conditions.

    The impact of this incident is limited to possible increased latency when connecting between our Tokyo and Singapore datacenters, although this increase is very minimal.

  • Our vendor reported that as per analysis of test results, the cause is likely located undersea near Toyohashi, Japan. This will require intervention of an repair vessel to perform the subsea operations/rectification works.

  • Engineers are send to the site. Joint investigations are ongoing as the cause is still unknown. No ETR is available at this point.

  • Our vendor has replied that they suspect a fault. No ETR is currently given.

    • Friday 16th, October 2020

    US: Santa Clara Backbone link between Chicago and Santa Clara datacenters down

    At this moment we are experiencing problems with: Backbone link between our Chicago and Santa Clara 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 have reached out to our vendor for investigation.

    Estimated time of repair: Unknown

    Impact: Due to the current ongoing incident on our backbone link between our Chicago and Santa Clara 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 affected fiber was repaired, restoring services to a stable state.

  • Service has been restored, however fiber splicing efforts continue. Services remain at-risk.

  • 18:28 UTC - Crews have identified the general location of the fiber damage and have begun excavating for access to the affected cables. Once excavation is complete and the fiber has been exposed, the splicing crew will be able to begin preparing the cable for splicing.

    • Thursday 15th, October 2020

    No incidents reported