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

Thursday 17th, December 2020

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

  • This issue has been resolved.

  • We see that the connection seems restored at this moment. Since the vendor did not yet gave the hands off notice we will be closely monitoring until further notice.

  • Our vendor has reported the ETR to be 14:00 UTC.

    • Wednesday 16th, December 2020

    DK: Copenhagen Backbone link between our Copenhagen and Moscow datacenters down

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

    The cause of the incident is currently: Our vendor reports a cable was damaged during excavation by local construction crews.

    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 Copenhagen 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 incident has now been resolved.

  • During final stage of works on repairing this cable, the cable closure was damaged resulting in a second interruption. The current ETR on restoration of the cable closure is 30 minutes.

    • Tuesday 15th, December 2020

    DK: Copenhagen Backbone link between our Copenhagen and Amsterdam datacenters

    At this moment we are experiencing problems with: Backbone link between our Copenhagen and Amsterdam 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: Not available at this time.

    Impact: Due to the current ongoing incident on our backbone link between our Copenhagen and Amsterdam 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 connection is restored and traffic is normalized.

  • Current ETR is reported to be Dec 16, 04:00 UTC.

  • Our vendor reports that field engineers found a fiber optic cut caused by a third-party drilling operation. An emergency team is already on-site and is currently excavating to restore the damaged area. More investigation will need to be done before an ETR can be provided.

    • API v3 i3D.net API unavailable

    At this moment we are experiencing problems with: the i3D.net and Smartdc API, resulting in one.i3d.net also being offline.

    The cause of the incident is currently: Unknown.

    We have taken the following actions to resolve the incident: We are currently investigating the root cause of this incident which became visible after the switch upgrade this morning (06:00 UTC).

    Estimated time of repair: Not available at this time.

    Impact: Due to the API being unavailable, all API calls as well as one.i3d.net are currently offline. The ONE Deployment Platform cannot be used for new calls, but existing capacity is unaffected.

    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 are now fully closing this incident.

  • The API has been stabilized. We will continue monitoring the situation before closing this incident.

    • Monday 14th, December 2020

    Backbone link between our Kyiv and Moscow datacenters

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

    Estimated time of repair: Not available at this time.

    Impact: Due to the current ongoing incident on our backbone link between our Kyiv 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 services have restored after they were switched to different optical fibers.

  • Our vendor has informed us that a fire in a cable collector has caused this incident. Their engineers are currently trying to switch services to other optical fibers. There is no ETR / ETA at this moment.

    • Sunday 13th, December 2020

    No incidents reported

    Saturday 12th, December 2020

    No incidents reported

    Friday 11th, December 2020

    No incidents reported

    Thursday 10th, December 2020

    US: Chicago Backbone link between our Chicago and Seattle datacenters

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

    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.

    • NL: Rotterdam Incident Ziggo/KPN network

    We are getting reports from customers having trouble connecting to our Rotterdam and Heerlen datacenters. These issues stem from an incident that occurs to start in the Ziggo and/or KPN network. The i3D.net/Smartdc networks are stable so as soon as this third-party incident has been resolved, all connectivity to our datacenter will also be back to normal.

  • It looks like Ziggo customers are no longer experiencing issues, but we do still see complaints coming in for KPN customers.