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
[Network Maintenance] Router Software Update - Montreuil - December 11, 2025

Dear Client,

We would like to notify you of upcoming network maintenance activities that will affect services in our Montreuil datacenter. The network maintenance has been scheduled for December 11, 2025.

Location: Montreuil, France

Schedule: Start time: December 11, 2025, 00:00 UTC End time: December 11, 2025, 05:00 UTC Planned impact: Reduced redundancy (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: Reduced redundancy: There will be reduced redundancy during the maintenance window; routers will be upgraded one at a time to ensure minimum impact.

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

[Network Maintenance] Aggregation Switch Software Update - Newark – January 6, 2026

Dear Client,

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

Location: Newark, America

Schedule: Start time: January 6, 2026, 09:00 UTC End time: January 6, 2026, 13:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: The maintenance is required to address difference in configuration behavior in newer software releases. This will prevent potential issues and ensure we can maintain stability.

Expected impact: Reduced Redundancy: As the activity will be executed by one aggregation switch at a time, there is no impact expected. During this maintenance there will be reduced redundancy.

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

[Network Maintenance] Aggregation Switch Software Update - Newark – January 7, 2026

Dear Client,

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

Location: Newark, United States

Schedule: Start time: January 7, 2026, 09:00 UTC End time: January 7, 2026, 13:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: The maintenance is required to address difference in configuration behavior in newer software releases. This will prevent potential issues and ensure we can maintain stability.

Expected impact: Reduced Redundancy: As the activity will be executed by one aggregation switch at a time, there is no impact expected. During this maintenance there will be reduced redundancy.

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

Vendor Cooling Maintenance – Rotterdam – January 19th, 2026

Dear Client,

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

Location: Rotterdam, Netherlands

Schedule: Start time: January 19, 2026, 7:00 UTC End time: January 22, 2026, 16:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: We will be performing a cooling maintenance on our two cooling pumps of both A and B line to ensure continued performance, efficiency, and reliability of the system. We will adjust the start-up procedure so that both pumps start simultaneously

Expected impact: During the maintenance window the redundancy of the cooling system will be reduced

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

Past Incidents

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

    Wednesday 14th, October 2020

    No incidents reported

    Tuesday 13th, October 2020

    US: Chicago 23:20 UTC - Backbone link between 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 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 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 by our vendor.

    • Monday 12th, October 2020

    DE: Frankfurt Backbone link between 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 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 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 vendor has restored the service. Downtime was due to planned maintenance.

    • US: Chicago Backbone link between 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 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 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.

  • Fiber was damaged and repaired. Service has been restored.

  • Our vendor has indicated that they see circuits restoring. We also receive traffic again and keep monitoring the connection.

  • Construction crews are working as efficiently as safety permits. Delays are caused due to locational difficulties. A further update is expected about 2 hours from now.

  • Our vendor indicates this issue is due to a fiber cut caused by local construction from a railroad crew. Teams have been dispatched to the site to review/repair the damage. We anticipate another update regarding repair status around 16:30 EST(20:30 UTC).