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
[Maintenance] 2025 Rotterdam Q3 quarterly on-load tests

Dear customer,

In the below overview you will find the date and time of our planned on-load tests in our  Smartdc Rotterdam datacenter for Q3 2025:

Location: Rotterdam, The Netherlands

On-load test Q3: Startdatum: 5 August 2025, 06:00 UTC Einddatum: 5 August 2025, 08:00 UTC

Expected downtime: None expected

Impact:  No impact expected

Reason for these maintenances: These on-load tests are routine and meant to test the back-up power systems of our Rotterdam facility. This is to ensure that everything remains fully operational in the event of a power outage in the facility.

Support: Our support department will be open during the maintenances. More details about how you can contact our support can be found on https://i3d.net/support/

[Network Maintenance] Router Component Reload - Paris – August 7, 2025

Dear Client,

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

Location: Paris, France

Schedule: Start time: August 7, 2025, 12:00 UTC End time: August 7, 2025, 14:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: The maintenance is required to address a potentially faulty component in the network switch.

Expected impact: During this maintenance there will be reduced redundancy. Prior to reloading the potentially faulty component, all traffic will be drained from the router.

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 Reboot – Ashburn – August 12, 2025

Dear Client,

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

Location: Ashburn, USA

Schedule: Start time: August 12, 2025, 06:00 UTC End time: August 12, 2025, 07:30 UTC Planned impact: Impact expected (see below for details)

Reason for this maintenance: We will be performing a corrective maintenance on one of our switches to prevent a possible failure in the future due to a known bug in the device.

Expected impact: We will be performing a device reboot. As the device will be power cycled, full loss of connectivity should be expected 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/

Past Incidents

Thursday 31st, March 2022

GB: London Our BBL between London and Saint Denis has flapped.

Our BBL between London and Saint Denis has flapped. We will be draining the link and we will be investigating a cause. A hit in latency can be expected in the surrounding area's

  • This incident has been resolved.

    • Wednesday 30th, March 2022

    US: Newark Backbone link between Newark and Montreal is down

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

    • Tuesday 29th, March 2022

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

    At this moment we are experiencing problems with: Backbone link between our Santa Clara and Chicago 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 Santa Clara and Chicago 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 issues have been resolved.

  • A fiber cut has been identified and repair crews have been dispatched. No ETR at this time.

    • Monday 28th, March 2022

    NL: Amsterdam Backbone link between our Amsterdam and Oslo datacenters down

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

    • Sunday 27th, March 2022

    No incidents reported

    Saturday 26th, March 2022

    SA: Johannesburg Connectivity issues Johannesburg

    At this moment we are experiencing problems with: Connectivity in our Johannesburg datacenter

    The cause of the incident is currently: Unknown

    We have taken the following actions to resolve the incident: Our engineers are working to resolve this incident

    Estimated time of repair: No ETR available at this time

    Impact: Due to the current incident services in our Johannesburg datacenter are currently unavailable

    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.

  • Services have restored.

    • 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 has indicated the fiber has been restored. The link is back online but we will continue monitoring for the rest of the day.

  • The link went down again, we are in contact with our vendor.

  • The fiber fault has been repaired and our vendor is hands off.

    • Friday 25th, March 2022

    UA: Kyiv Backbone link between our Kiev and Moscow datacenters down

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

    The cause of the incident is currently: Known, due to ongoing conflict between these regions.

    We have taken the following actions to resolve the incident: Due to the ongoing events, this circuit has been decommissioned and will be replaced by an alternative path between Kyiv and Bucharest.

    Estimated time of repair: Unknown.

    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.

  • The vendor is still working to finalize repairs for the affected circuit and we are awaiting further updates.