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 8th, January 2021

JP: Tokyo Network outage Japan Tokyo

At this moment we are experiencing problems with: We are experiencing a network outage in the Japan region.

The cause of the incident is currently: Linecard crash.

We have taken the following actions to resolve the incident: The linecard has since been recovered and we are watching it currently.

Estimated time of repair: Resolved.

Impact: Clients may experience outages with their services in the region.

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.

Thursday 7th, January 2021

JP: Tokyo Major network outage in Japan region

At this moment we are experiencing problems with: We are experiencing a major network outage in the Japan region.

The cause of the incident is currently: Linecard crash.

We have taken the following actions to resolve the incident: The linecard has since been recovered.

Estimated time of repair: Resolved.

Impact: Clients may experience outages with their services in the region.

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 issue was caused by a line card crash which has since been recovered. Traffic is back to normal.

  • This incident has escalated to a major outage. Our team is still investigating and working to resolve the situation as soon as possible.

    • Wednesday 6th, January 2021

    Nameservers i3D.net Nameserver issue (5.200.5.5 only)

    At this moment we are experiencing problems with: One of the anycasted nameserver IP addresses (5.200.5.5) was temporarily not working as expected, the other nameserver IP address remained operational (5.200.5.200)

    The cause of the incident is currently: Under investigation

    We have taken the following actions to resolve the incident: 5.200.5.5 is available again, the root cause is under investigation

    Estimated time of repair: The services have already recovered.

    Impact: During this incident, one of the two anycasted nameserver IP addresses was temporarily not available (5.200.5.5).

    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.

    Tuesday 5th, January 2021

    No incidents reported

    Monday 4th, January 2021

    No incidents reported

    Sunday 3rd, January 2021

    No incidents reported

    Saturday 2nd, January 2021

    No incidents reported