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
[Software Maintenance] FlexMetal Backend Maintenance – August 27, 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 August 27, 2025.

Schedule: Start time: August 27, 2025, 09:00 UTC

End time: August 27, 2025, 18:00 UTC

Planned impact: No impact (see below for details)

Reason for this maintenance:

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

Expected impact:

No impact is expected during this maintenance.

All steps taken during this maintenance have been thoroughly tested in non-production environments prior to this announcement. During the maintenance window we will perform the changes step-by-step, separated by tests verifying the performed change as well as availability of the FlexMetal product.

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 4th, December 2020

SG: Singapore Backbone link between our St. Denis and Singapore datacenters

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

Estimated time of repair: Unknown

Impact: Due to the current ongoing incident on our backbone link between our St. Denis and Singapore datacenters, users in our Singapore datacenter might encounter increased latency due to re-routed traffic paths.

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 issue has been resolved and service is fully restored.

  • Thursday 3rd, December 2020

    US: Ashburn Backbone link between our Chicago and Newark datacenters

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

    Wednesday 2nd, December 2020

    US: Santa Clara Santa Clara DC - Multiple circuits down

    At this moment we are experiencing problems with: We are seeing multiple circuits down in our datacenter in the Santa Clara region.

    The cause of the incident is currently: Damage to dark fiber services.

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

    Estimated time of repair: Resolved.

    Impact: Due to the current ongoing incident in our Santa Clara datacenter, users connecting to this region and surrounding regions may experience increased latency and connection issues.

    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.

  • Repairs have been completed and crews are hands off.

  • Our vendor reports that repairs are over 50% complete, however there is still no ETR at this time. Services are gradually turning up as repairs progress, but stability is not assured until repairs are complete.

  • Our vendor reports technicians on site are working on repairs.

  • Our vendor has notified us that dark fiber technicians are onsite and inspecting for damage.

  • Our vendor has identified the issue as related to dark fiber services and is working to resolve the problem.

  • Moscow DC - Redundant path between PoP's is down

    At this moment we are experiencing problems with: One of the redundant paths between our PoP's in Moscow is down.

    The cause of the incident is currently: Our vendor reports an ongoing fire that is preventing access to the affected fiber. Our vendor reports the issue has been escalated to the highest level and a plan for backup and recovery is being rolled out.

    We have taken the following actions to resolve the incident: We have reached out to our vendor and they are keeping us updated.

    Estimated time of repair: Current ETA is unknown.

    Impact: No customer impact is expected.

    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.

  • Circuits have shown long-term stability. The situation is considered resolved.

  • Circuits seem recovered. Since there is no official hands off we will monitor the situation.

  • Tuesday 1st, December 2020

    No incidents reported

    Monday 30th, November 2020

    UA: Kyiv Backbone link between our Kiev and Warsaw datacenters

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

  • Restoration works have been completed.

  • Our vendor confirmed a fiber cut. Emergency teams are dispatched. ETA still unknown.

  • Sunday 29th, November 2020

    Backbone link between our Moscow and Warsaw datacenters

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

  • The cause of the fiber cut has been identified. Crews have begun repairs, but there is no ETR at this time.

  • Saturday 28th, November 2020

    No incidents reported

    Friday 27th, November 2020

    CA: Toronto Backbone link between our Toronto and Saint-Laurent datacenters

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

  • Connectivity was restored while the investigation was ongoing. Our vendor will continue to investigate the root cause of this incident.