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

Stickied Incidents

Tuesday 3rd, March 2026

ONE Control Panel one.i3d.net Portal Outage

Access has been restored on One Portal (one.i3d.net). We apologize for any inconvenience caused by this.

Maintenance
[Emergency Maintenance] CDN Origin Maintenance - Rotterdam - March 5, 2026

Dear Client,

We would like to notify you of upcoming emergency maintenance activities that will affect services in our Rotterdam datacenter. The emergency maintenance has been scheduled for March 5, 2026.

Location: Rotterdam, Netherlands

Schedule: Start time: March 5, 2026, 11:00 UTC End time: March 5 , 2026, 11:30 UTC Planned impact: Impact expected (see below for details)

Reason for this maintenance: Due to a performance degradation observed in CDN downloads this emergency maintenance is required to be carried out. In order to implement the solution, equipment is required to be rebooted which will stop processes for a brief moment.

Expected impact: Full downtime: Full downtime is expected for the duration of the maintenance. During this maintenance it is not possible to upload new files to CDN origins hosted in our Rotterdam datacenter.

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/

[Infrastructure Maintenance] Cooling Maintenance - Heerlen – March 23, 2026

We would like to notify you of upcoming cooling maintenance activities that will affect services in our Heerlen datacenter. The cooling maintenance has been scheduled for March 23, 2026.

Location:

Heerlen, The Netherlands

Schedule:

Start time: March 23, 2026, 07:00 UTC

End time: March 23, 2026, 16:00 UTC

Planned impact: Reduced redundancy (see below for details)

Reason for Maintenance:

We will perform preventive maintenance on the cooling systems to ensure continued reliability and safe operation.

Expected Impact: During the maintenance the cooling units will be maintained one by one. Cooling will remain available, but redundancy will be temporarily reduced while the work is carried out.

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 11th, October 2019

DE: Frankfurt Router Frankfurt, Germany

At this moment we are experiencing problems with: Our router in Frankfurt, Germany

The cause of the incident is currently: Unknown, we are investigating

We have taken the following actions to resolve the incident: Ongoing

Estimated time of repair: Unknown

Impact: You may experience packetloss or loss when traffic goes through Frankfurt

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://www.i3d.net/contact/).

Subscribe for the latest updates. You may consult our Privacy Statement for more information on the processing of your personal data.

  • The root cause of the event, was a linecard in one of the DE-CIX Frankfurt switches that was malfunctioning. DE-CIX talked to Nokia TAC and they recommended to reload this linecard. After that things normalized. One of the two ports that we have at DE-CIX Frankfurt was connected to this linecard and therefore 50% of the traffic through DE-CIX could have been affected by this problem.

    The incident has been investigated and has been resolved.

  • One of the uplinks towards the DE-CIX is malfunctioning. This uplink is disabled, which removed the impact. We will work on resolving this permanently.

    More updates to come.

    • Thursday 10th, October 2019

    No incidents reported

    Wednesday 9th, October 2019

    No incidents reported

    Tuesday 8th, October 2019

    No incidents reported

    Monday 7th, October 2019

    No incidents reported

    Sunday 6th, October 2019

    No incidents reported

    Saturday 5th, October 2019

    No incidents reported

    Friday 4th, October 2019

    NL: Rotterdam Rotterdam datacenter network

    At this moment we are experiencing problems with: The i3D.net network in our Rotterdam Datacenter because an important network provider (NL-ix) is experiencing issues.

    The cause of the incident is currently: Known, NL-ix reported issues on their side.

    We have taken the following actions to resolve the incident: We will disable the NL-ix port if the issue persists.

    Estimated time of repair: Unknown

    Impact: You may experience packetloss or loss of connection to your servers.

    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.

  • NL-ix port is enabled again and operates as normal. Hereby we close this incident.

  • We have been informed that NL-ix has found the cause of the problem and resolved it. Our network department will consult on which moment we will enable our NL-ix ports again.

  • We have disabled the NL-ix port and will wait for further notice from NL-ix when to enable the connection again. This should return the stability in our network.