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 Maintenance - Rotterdam – September 17, 2025

Dear Client,

(An email or ticket has been sent to you if your services will be affected by this maintenance.)

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 September 17, 2025.

Location:
Rotterdam, The Netherlands

Schedule:
Start time: September 17, 2025, 01:00 UTC
End time: September 17, 2025, 03:00 UTC
Planned impact: Impact expected (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:
Impact expected, full downtime from start until the end of the maintenance window (An email or ticket has been sent to you if your services will be affected by this maintenance.)

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/

[Software Maintenance] FlexMetal Backend Maintenance – September 30, 2025

Dear Client,

We would like to notify you of upcoming FlexMetal backend maintenance activities that will affect backend services of our FlexMetal product. The maintenance has been scheduled for September 30, 2025.

Schedule: Start time: September 30, 2025, 10:00 UTC End time: September 30, 2025, 11:00 UTC Planned impact: Impact expected (see below for details)

Reason for this maintenance: During this maintenance we will be migrating some backend FlexMetal data to a new cluster. This change further increases reliability, ease of use and manageability for our engineers, ultimately providing a better FlexMetal service.

Expected impact: Service Impact: FlexMetal delivery service and related API endpoints will be unavailable during the maintenance. This does not affect servers deployed using FlexMetal, only deploying new servers.

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] Aggregation Switch Software Update - São Paulo – October 6, 2025

Dear Client,

We would like to notify you of upcoming network maintenance activities that will affect services in our São Paulo datacenter. The network maintenance has been scheduled for October 6, 2025.

Location: São Paulo, Brazil

Schedule: Start time: October 6, 2025, 08:00 UTC End time: October 6, 2025, 10:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: The maintenance is required to address difference in configuration behaviour 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 the time, there is no impact expected. During this maintenance there will be reduced redundancy. This is the first maintenance from a total of four aggregators.

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

Friday 3rd, June 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.

  • This incident has been resolved.

  • We see traffic has been restored. As we have no hands off from our vendor as of yet we keep monitoring this link.

    • Thursday 2nd, June 2022

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

    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.

  • This incident was due to planned maintenance by our vendor and has been completed. Connectivity has been stored since 4am UTC.

    • IT: Milan Backbone link between our Zurich and Milan datacenters down

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

    • FR: Paris Backbone link between our Saint-Denis and Madrid datacenters down

    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.

    • NL: Rotterdam A network incident in our Rotterdam datacenter

    At this moment we are experiencing problems with: A network incident in our Rotterdam datacenter

    The cause of the incident is currently: Unknown. (For the most up-to-date information, please check the below status updates)

    We have taken the following actions to resolve the incident: We are investigating the root cause of this incident closely with our hardware vendor.

    Estimated time of repair: Unknown. (For the most up-to-date information, please check the below status updates)

    Impact: Due to the current network incident in our Rotterdam datacenter, users between these and surrounding regions may experience increased latency or a loss of service.

    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. Please contact us via support@i3d.net if you wish to receive a RFO for this incident.

  • The site is operational, however it will take some time to complete our investigation. We will continue monitoring the situation.

  • We are still actively in contact with our hardware vendor to investigate the root cause. As we have no direct indication of re-occurrence we are watching connectivity closely and will keep you updated accordingly.

  • The incident was caused by crashing linecards. These have been restored and we are in contact with our vendor to investigate the cause of this incident.

    • Wednesday 1st, June 2022

    No incidents reported

    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.