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

Tuesday 31st, May 2022

ES: Madrid Backbone link between our Saint-Denis and Madrid datacenters flapping

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

    • SG: Singapore Backbone link between our Saint-Denis and Singapore datacenters down

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

  • This incident has been resolved.

    • IN: Mumbai Backbone link between our Mumbai and Singapore datacenters down

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

  • This incident has been resolved.

    • Monday 30th, May 2022

    HU: Budapest Backbone link between our Budapest and Bucharest datacenters down

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

  • The fibercut has been repaired, traffic is restored and vendor hands off.

  • This incident is caused by a fiber cut. Traffic has been restored, but no hands-off from vendor yet. We are watching the circuit closely until then.

    • Sunday 29th, May 2022

    No incidents reported

    Saturday 28th, May 2022

    US: Chicago Backbone link between our Seattle and Chicago datacenters flapping

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

  • This incident has been resolved. The vendor replaced the faulty card and services are fully restored.

  • The network vendor identified a broken linecard to be the cause of this incident. A new card has been picked-up and the engineer will arrive on location in ~3,5hours (16:00 UTC).

    • Friday 27th, May 2022

    PL: Warsaw Backbone link between our Kiev and Warsaw datacenters down

    At this moment we are experiencing problems with: Backbone link between our Kiev and Warsaw 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. Given the ongoing situation in this region, we are unsure about the speed of repair for this incident and are expecting this to take longer than usual.

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

  • Traffic has been restored after the vendor located and repaired a fiber cut. As we have no official hands off yet, we will keep monitoring the link closely for now.

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

    At this moment, we are experiencing problems with: Backbone link between our Dubai and Mumbai 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 Dubai and Mumbai datacenters, impact could be visible in the form of 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.

  • Link is confirmed to be running again. RFO requested from Vendor.

    • Thursday 26th, May 2022

    US: Ashburn Backbone link between our Atlanta and Ashburn datacenters down

    At this moment we are experiencing problems with: Backbone link between our Atlanta and Ashburn 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 Atlanta and Ashburn datacenters, impact could be visible in the form of 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.

  • Link is restored

    • Wednesday 25th, May 2022

    GB: London Backbone link between our London and Newark datacenters down

    At this moment we are experiencing problems with: Backbone link between our London and Newark 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 London and Newark 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 24th, May 2022

    IT: Milan Incident Milan datacenter

    At this moment we are experiencing problems with: Incident in our Milan datacenter.

    The cause of the incident is currently: Unknown

    Estimated time of repair: No ETR available

    Impact: We briefly lost connection to our Milan datacenter.

    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.