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

Sunday 5th, February 2023

US: Santa Clara Backbone link between our 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 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 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.

  • Vendor reported this service was affected by an Event earlier:

    Final ~ Salt Lake City, UT ~ Transport Unprotected Network Event ~ Minor ~

    • US: Newark Backbone link between our Newark and Montreal datacenters 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: Unknown.

    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.

  • Our vendor is hands-off. Our link has remained stable.

  • The link is up and stable for a while. As we have no hands off yet we will keep this link under close monitoring.

  • Vendor reports 3rd party is aware of the manhole fire and problems as they have circuits and services affected by it as well. They are currently de-energizing the manhole feeders and will be working overnight to work on the trouble in an attempt to have access available for carriers by early afternoon on Sunday, 2/5/23

    • Saturday 4th, February 2023

    ONE Deployment Platform i3D DNS service down.

    At this moment, we are experiencing problems with: Our DNS service.

    The cause of the incident is currently: Unknown

    We have taken the following actions to resolve the incident: Our team is already working on it, and we see recovery.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our DNS, our i3d.net domain is down.

    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.

  • Service is fully operative.

  • Our team has restored the DNS service, and the domain is online again. We continue observing it.

    • Friday 3rd, February 2023

    No incidents reported

    Thursday 2nd, February 2023

    US: Seattle Backbone link between our Seattle and Santa Clara datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Seattle and Santa Clara datacenters.

    The cause of the incident is currently: Maintenance works from our vendor

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

    UA: Kyiv Backbone link between our Bucharest and Kyiv datacenters down

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

  • Emergency work is completed. Service is restored.

  • Our vendor reports this incident was caused by a fiber cut during works on the water infrastructure

    • Wednesday 1st, February 2023

    DE: Frankfurt Backbone link between our Heerlen and Frankfurt datacenters down

    At this moment we are experiencing problems with: Backbone link between our Heerlen and Frankfurt 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 Heerlen and Frankfurt 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 link has been restored.

    • ES: Madrid Backbone link between our Madrid and Milan datacenters down

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

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

  • The link has been restored.

    • Tuesday 31st, January 2023

    No incidents reported

    Monday 30th, January 2023

    SG: Singapore 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: Unknown.

    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

  • Reaching out to Vendor now.

    • NL: Rotterdam Backbone link between our Amsterdam and Rotterdam datacenters down

    This was the result of a maintenance and we are reaching out to vendor this link hasn't come back up. At this moment, we are experiencing problems with: Backbone link between our Amsterdam and Rotterdam datacenters.

    The cause of the incident is currently: After a planned maintenance the link didn't came back up.

    We have taken the following actions to resolve the incident: We reached out to the vendor to investigate and 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 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 link has been restored.

  • Our vendor reports that their engineer arrived on site to trouble shoot the incident.