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
[Fire System Maintenance] Fire System Maintenance - Smartdc Rotterdam - May 26, 2026

Dear Client, We would like to notify you of upcoming Fire System maintenance that will take place at Smartdc Rotterdam, May 26 -29, 2026.

Location: Rotterdam, The Netherlands

Schedule: Start time: May 26, 2026, 07:00 UTC End time: May 29, 2026, 16:00 UTC

Planned impact: No Impact (see below for details)

Reason for this maintenance: Our vendor will be performing preventative annual maintenance work to improve the performance, reliability and integrity of the Fire Suppression System.

Expected impact: No Impact is expected. During this maintenance, the Fire System alarm might go off.

Support: Our support department will be open during the maintenance. More details about how you can contact our support can be found here: Support

Past Incidents

Thursday 1st, December 2022

No incidents reported

Wednesday 30th, November 2022

Backbone link between our Saint Petersburg and Moscow datacenters is down

At this moment we are experiencing problems with: Backbone link between our Saint Petersburg and Moscow datacenters is down.

The cause of the incident is currently: Unknown

We have taken the following actions to resolve the incident: We have reached out to our vendor for more information.

Estimated time of repair: No ETR at this time.

Impact: Due to the current incident on our backbone link between our Saint Petersburg and Moscow 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.

  • Our link has been restored. the maintenance has been completed.

  • Our vendor is performing maintenance.

  • IT: Milan Backbone link between our Milan and Bucharest datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Milan and Bucharest 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 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 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.

  • Our vendor identified a fiber cut and the cut has been repaired. The link has been restored.

  • Backbone link between our Saint Petersburg and Moscow datacenters is down

    At this moment we are experiencing problems with: Backbone link between our Saint Petersburg and Moscow datacenters is down.

    The cause of the incident is currently: Unknown

    We have taken the following actions to resolve the incident: We have reached out to our vendor for more information.

    Estimated time of repair: No ETR at this time.

    Impact: Due to the current incident on our backbone link between our Saint Petersburg and Moscow 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.

  • Our link has remained stable.

  • Our link has restored. Awaiting to hear from our vendor.

  • Tuesday 29th, November 2022

    SG: Singapore Backbone link between our Paris and Singapore datacenters down

    At this moment we are experiencing problems with: Backbone link between our Paris and Singapore 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 are in touch with our vendor regarding status updates.

    Estimated time of repair: No ETR available at this time.

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

  • Our link has remained stable.

  • Link has been restored. We are waiting for hands-off

  • UAE: Dubai Backbone link between our Paris and Dubai datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Paris and Dubai 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 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 Paris and Dubai 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.

  • Our link has remained stable.

  • Link is restored. Waiting for hands off

  • UAE: Dubai Backbone link between our Dubai and Milan datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Dubai and Milan 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 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 Milan 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.

  • We have received a hands-off.

  • Link is back up. We are waiting for hands-off

  • IT: Milan Backbone link between our Milan and Bucharest datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Milan and Bucharest 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 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 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

  • Monday 28th, November 2022

    No incidents reported

    Sunday 27th, November 2022

    No incidents reported

    Saturday 26th, November 2022

    No incidents reported

    Friday 25th, November 2022

    RO: Bucharest Backbone link between our Bucharest and Kyiv datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Bucharest and Kyiv 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 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 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 issue has been resolved.