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
[Cooling Maintenance] Cooling Maintenance - Rotterdam – September 7 to October 7, 2026 - MCOM-454

Dear Client,

We would like to notify you of upcoming cooling maintenance activities that will affect services in our Rotterdam datacenter. The maintenance will take place on multiple dates between September 7 and October 7, 2026, as outlined below.

Location: Rotterdam, The Netherlands

Schedule:

Date

Maintenance window

September 7, 2026

05:00–14:00 UTC

September 9, 2026

05:00–14:00 UTC

September 11, 2026

05:00–14:00 UTC

September 14, 2026

05:00–14:00 UTC

September 16, 2026

05:00–14:00 UTC

September 18, 2026

05:00–14:00 UTC

September 23, 2026

05:00–14:00 UTC

September 25, 2026

05:00–14:00 UTC

September 28, 2026

05:00–14:00 UTC

September 30, 2026

05:00–14:00 UTC

October 2, 2026

05:00–14:00 UTC

October 5, 2026

05:00–14:00 UTC

October 7, 2026

05:00–14:00 UTC

Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: We will be performing maintenance on our Stulz cooling units to support continued reliability and stability.

Expected impact: Reduced cooling redundancy: No impact is expected to services, but cooling redundancy will be reduced while the cooling units are being serviced. Minor temperature fluctuations may occur during the maintenance activities.

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/

[Network Maintenance] Aggregation Switch Upgrade - Stockholm - September 8, 2026 - MCOM-456

Dear Client,

We would like to notify you of upcoming network maintenance activities that will affect services in our Stockholm datacenter. The network maintenance has been scheduled for September 8, 2026.

Location: Stockholm, Sweden

Schedule: Start time: September 8, 2026, 03:00 UTC End time: September 8, 2026, 07:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: We will be performing firmware upgrades on our aggregation switch(es) to improve quality and ensure long-term reliability.

Expected impact: Reduced redundancy: No impact expected, but there will be reduced redundancy during the maintenance window; aggregate switches will be upgraded one at a time to ensure minimum impact.

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

Saturday 8th, June 2024

No incidents reported

Friday 7th, June 2024

US: Ashburn Backbone link between Atlanta and Ashburn data centers down

At this moment, we are experiencing problems with: Backbone link between Atlanta and Ashburn data centers.

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 are in touch with our vendor regarding status updates.

Estimated time of repair: Unknown.

Impact: Due to the current incident on our backbone link between Atlanta and Ashburn data centers, 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.

  • Repairs have been completed and services has been restored.

  • Vendor discovered a underground cable was cut and have begun replacing the damage cable section.

  • Backbone link between our Milan and Bucharest data centers down

    At this moment, we are experiencing problems with: Backbone link between our Milan and Bucharest data centers.

    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 are in touch with our vendor regarding status updates.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our backbone link between our Milan and Bucharest data centers, 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 is resolved.

  • A fiber cut on private property has been identified as the cause of the outage. Technicians are currently on site digging out impacted fiber cable to relocate it away from private property.

  • Thursday 6th, June 2024

    Backbone link between our Bucharest and Kyiv data centers down

    At this moment, we are experiencing problems with: Backbone link between our Bucharest and Kyiv data centers.

    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 are in touch with our vendor regarding status updates.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our backbone link between our Bucharest and Kyiv data centers, 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 is resolved.

  • Wednesday 5th, June 2024

    Ticket system E-mails to our Ticketing System is processed with a delay

    At this moment we are experiencing problems with: Our Ticketing System experiences increased processing times for e-mails sent to our status@i3d.net address. Tickets opened via our Customer Portal are unaffected.

    The cause of the incident is currently: Unknown

    We have taken the following actions to resolve the incident: Our relevant team is investigating the issue.

    Estimated time of repair: Unknown

    Impact: Increased response time for tickets, that are opened via e-mail. Tickets opened via our Customer Portal are unaffected.

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

  • Tuesday 4th, June 2024

    ES: Madrid Backbone link between our Madrid and Johannesburg data centers down

    At this moment, we are experiencing problems with: Backbone link between our Madrid and Johannesburg data centers.

    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 are in touch with our vendor regarding status updates.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our backbone link between our Madrid and Johannesburg data centers, 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.

    FR: Paris Backbone link between our Dubai and Saint Denis data centers down

    At this moment, we are experiencing problems with: Backbone link between our Dubai and Saint Denis data centers.

    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 are in touch with our vendor regarding status updates.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our backbone link between our Dubai and Saint Denis data centers, 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 link has been restored. We have received the hands-off.

  • SG: Singapore Backbone link between our Tokyo and Singapore data centers down

    At this moment, we are experiencing problems with: Backbone link between our Tokyo and Singapore data centers.

    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 are in touch with our vendor regarding status updates.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our backbone link between our Tokyo and Singapore data centers, 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.

  • Our vendor has noticed a performance issue due to a faulty hardware, the link has been restored.

  • FR: Paris Backbone link between our Paris and Madrid data centers down

    At this moment, we are experiencing problems with: Backbone link between our Paris and Madrid data centers.

    The cause of the incident is currently: Our vendor is performing a hardware replacement.

    We have taken the following actions to resolve the incident: We are currently monitoring the situation and are in touch with our vendor regarding status updates.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our backbone link between our 1 and 2 data centers, 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.

  • Our vendor has noticed a performance issues due to faulty hardware, it recently came back online so the line has been restored.

  • Monday 3rd, June 2024

    Backbone link between our Warsaw and Moscow data centers down

    At this moment, we are experiencing problems with: Backbone link between our Warsaw and Moscow data centers.

    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 are in touch with our vendor regarding status updates.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our backbone link between our Warsaw and Moscow data centers, 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.

  • Our link has been restored. We have received the hands off from our vendor.

  • Sunday 2nd, June 2024

    No incidents reported

    Saturday 1st, June 2024

    RO: Bucharest Backbone link between our Bucharest and Kiyev data centers down

    At this moment, we are experiencing problems with: Backbone link between our Bucharest and Kiyev data centers.

    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 are in touch with our vendor regarding status updates.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our backbone link between our Bucharest and Kiyev data centers, 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.

  • Vendor has fixed the broken fiber. The link is up again.

  • Vendor has reported back and confirmed there was a fibre cut. They are in the process of having this issue repaired.