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 19th, June 2020

No incidents reported

Thursday 18th, June 2020

No incidents reported

Wednesday 17th, June 2020

No incidents reported

Tuesday 16th, June 2020

No incidents reported

Monday 15th, June 2020

US: Dallas Backbone incident between Ashburn and Dallas

At this moment we are experiencing problems with: Backbone link between our Ashburn and Dallas datacenters

The cause of the incident is currently: Known

We have taken the following actions to resolve the incident: We have engaged our vendor to investigate this incident.

Estimated end-time: Unknown

Impact: Due to the current ongoing incident on our backbone between Los Angeles and Dallas, our Dallas datacenter has now become isolated from the i3D.net network. This might increase latency for users to our Dallas datacenter.

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: https://customer.i3d.net/contact.php

  • Repairs have been completed. Service has been restored.

  • Construction crew have arrived on site and are digging to expose the damaged line.

    • US: Los Angeles Backbone incident between Los Angeles and Dallas

    At this moment we are experiencing problems with: Backbone link between our Los Angeles and Dallas datacenters

    The cause of the incident is currently: Known

    We have taken the following actions to resolve the incident: Our vendor estimates to have a replacement module in place at 19:30 UTC.

    Estimated end-time: Unknown

    Impact: Customers or end-users with traffic between Los Angeles and Dallas will experience higher latency due to a longer network path.

    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: https://customer.i3d.net/contact.php

  • This incident has now fully recovered.

  • A different incident on the same link has come to light. Once traffic is restored we will place another update.

  • The definitive cause of this incident has been found to be crossed fibers. This has been restored and traffic is expected to be back normal in 30-60 minutes.

  • The technicians are expected to arrive on site at 16:00 UTC.

  • The previous replacement module did not resolve this issue. Our transport vendor thinks they have now located the issue together with their equipment vendor to OSP fibers from a maintenance performed by the OSP fiber provider. Different technicians have been dispatched.

  • The previous replacement module did not resolve this issue. Our transport vendor thinks they have now located the issue together with their equipment vendor to OSP fibers from a maintenance performed by the OSP fiber provider. Different technicians have been dispatched.

  • The replacement module did not resolve this incident. Our transport vendor is in contact with their equipment vendor to provide a resolution. There is no current ETA on the services being restored.

  • The technician is onsite working on replacing the module. No ETR at this time.

  • The technician will arrive on location in ~10 minutes.

  • The technician is expected to arrive at 18:10 UTC.

    • Sunday 14th, June 2020

    No incidents reported

    Saturday 13th, June 2020

    No incidents reported

    Friday 12th, June 2020

    US: Ashburn Backbone incident between Ashburn and Dallas

    At this moment we are experiencing problems with: Dark-fiber connection between Ashburn and Dallas

    The cause of the incident is currently: Known

    We have taken the following actions to resolve the incident: We have contacted our vendor to have this incident investigated. Once we know more about the cause of this incident we will post an update.

    Estimated end-time: Resolved.

    Impact: Customers or end-users with traffic between Ashburn and Dallas might experience heightened latency at this time.

    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: https://customer.i3d.net/contact.php

  • The circuit has been repaired and is active again.

  • The fiber cut has been located. Estimated repair time is currently 23:00 UTC.

  • The restoration crew is on-site and is trying to locate the exact location of damage.

  • The restoration crew is on its way to the fiber cut and should be on-site shortly.