All systems are operational

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 16th, October 2020

US: Santa Clara Backbone link between 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 have reached out to our vendor for investigation.

Estimated time of repair: Unknown

Impact: Due to the current ongoing 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.

  • The affected fiber was repaired, restoring services to a stable state.

  • Service has been restored, however fiber splicing efforts continue. Services remain at-risk.

  • 18:28 UTC - Crews have identified the general location of the fiber damage and have begun excavating for access to the affected cables. Once excavation is complete and the fiber has been exposed, the splicing crew will be able to begin preparing the cable for splicing.

    • Thursday 15th, October 2020

    No incidents reported

    Wednesday 14th, October 2020

    No incidents reported

    Tuesday 13th, October 2020

    US: Chicago 23:20 UTC - Backbone link between Chicago and Dallas datacenters down

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

    Impact: Due to the current ongoing incident on our backbone link between our Chicago and Dallas 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 by our vendor.

    • Monday 12th, October 2020

    DE: Frankfurt Backbone link between Frankfurt and Rotterdam datacenters down

    At this moment we are experiencing problems with: Backbone link between our Frankfurt and Rotterdam 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: Unknown

    Impact: Due to the current ongoing incident on our backbone link between our Frankfurt 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 vendor has restored the service. Downtime was due to planned maintenance.

    • US: Chicago Backbone link between Chicago and Dallas datacenters down

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

    Impact: Due to the current ongoing incident on our backbone link between our Chicago and Dallas 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 was damaged and repaired. Service has been restored.

  • Our vendor has indicated that they see circuits restoring. We also receive traffic again and keep monitoring the connection.

  • Construction crews are working as efficiently as safety permits. Delays are caused due to locational difficulties. A further update is expected about 2 hours from now.

  • Our vendor indicates this issue is due to a fiber cut caused by local construction from a railroad crew. Teams have been dispatched to the site to review/repair the damage. We anticipate another update regarding repair status around 16:30 EST(20:30 UTC).

    • Sunday 11th, October 2020

    No incidents reported

    Saturday 10th, October 2020

    US: Ashburn 17:10 UTC - Backbone link between Ashburn and Dallas datacenters down

    At this moment we are experiencing problems with: Backbone link between our Ashburn and Dallas 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: Unknown

    Impact: Due to the current ongoing incident on our backbone link between our Ashburn and Dallas 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 was damaged and repaired. Service has been restored.