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] Milan – Router Software Update – November 26, 2025

We would like to inform you of an upcoming network maintenance being performed in our Milan datacenter. This maintenance is scheduled for November 26, 2025.

Location:

Milan, Italy

Schedule:

Start Time: November 26, 2025, 03:00 UTC

End Time: November 26, 2025, 07:00 UTC

Planned downtime:

No impact expected

Reason for this maintenance:

We will be performing firmware upgrades on our router(s) to improve quality and ensure long-term reliability.

Expected downtime/impact:

Reduced redundancy: No impact expected, but there will be reduced redundancy during the maintenance window; routers will be upgraded one at a time to ensure minimum impact.

[Network Maintenance] Hong Kong – Router Software Update – November 26, 2025

We would like to inform you of an upcoming network maintenance being performed in our Hong Kong datacenter. This maintenance is scheduled for November 26, 2025.

Location:

Hong Kong

Schedule:

Start Time: November 26, 2025, 21:00 UTC

End Time: November 27, 2025, 01:00 UTC

Planned downtime:

No impact expected

Reason for this maintenance:

We will be performing firmware upgrades on our router(s) to improve quality and ensure long-term reliability.

Expected downtime/impact:

Reduced redundancy: No impact expected, but there will be reduced redundancy during the maintenance window; routers will be upgraded one at a time to ensure minimum impact.

[Network Maintenance] Router Software Update - Hong Kong - November 26, 2025

Dear Client,

We would like to notify you of upcoming network maintenance activities that will affect services in our Hong Kong datacenter. The network maintenance has been scheduled for November 26, 2025.

Location: Hong Kong, Hong Kong

Schedule: Start time: November 26, 2025, 21:00 UTC End time: November 27, 2025, 01: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: No impact expected, but 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: https://i3d.net/support/ You can find maintenance updates and the current situation at https://status.i3d.net

Past Incidents

Tuesday 21st, February 2023

US: Ashburn Backbone link between our Ashburn and Saint Denis datacenters is down

At this moment we are experiencing problems with: Backbone link between our Ashburn and Saint Denis 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 have reached out to our vendor for more information.

Estimated time of repair: Unknown

Impact: Due to the current incident on our backbone link between our Ashburn and Saint Denis 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 remained stable. Our vendor is hands-off.

  • Our link has been restored. We are still waiting to receive a hands-off from our vendor.

  • Monday 20th, February 2023

    No incidents reported

    Sunday 19th, February 2023

    No incidents reported

    Saturday 18th, February 2023

    No incidents reported

    Friday 17th, February 2023

    No incidents reported

    Thursday 16th, February 2023

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

  • It appears we received the hands off from the vendor and our link has remained stable for the past 2 hours.

  • The link has become stable and will set to watching.

  • NL: Heerlen 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.

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

  • Confirmed with the Vendor as the alert has been cleared.

  • Link has been restored but waiting for hands off from vendor.

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

  • The restoration work has been completed on this circuit.

  • Wednesday 15th, February 2023

    UAE: Dubai Backbone link between our Dubai and Fujairah datacenters is down

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

    The cause of the incident is currently: Unknown.

    We have taken the following actions to resolve the incident: We have reached out to our vendor for more information.

    Estimated time of repair: No ETR at this time.

    Impact: Due to the current incident on our backbone link between our Dubai and Fujairah 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 is incident is resolved.

  • JP: Tokyo Backbone link between our Tokyo and Shanghai datacenters down

    At this moment we are experiencing problems with: Backbone link between our Tokyo and Shanghai 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 Tokyo and Shanghai 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 link is up and stable for several hours at this time.

  • Tuesday 14th, February 2023

    SA: Johannesburg Backbone link between our Madrid and Johannesburg datacenters down

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

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

  • Fiber repairs are completed. The link is currently up and awaiting hands off from our vendor. Until then we will closely monitor the link.

  • A fiber cut has been identified.