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
[Maintenance] 2025 Rotterdam Q3 quarterly on-load tests

Dear customer,

In the below overview you will find the date and time of our planned on-load tests in our  Smartdc Rotterdam datacenter for Q3 2025:

Location: Rotterdam, The Netherlands

On-load test Q3: Startdatum: 5 August 2025, 06:00 UTC Einddatum: 5 August 2025, 08:00 UTC

Expected downtime: None expected

Impact:  No impact expected

Reason for these maintenances: These on-load tests are routine and meant to test the back-up power systems of our Rotterdam facility. This is to ensure that everything remains fully operational in the event of a power outage in the facility.

Support: Our support department will be open during the maintenances. More details about how you can contact our support can be found on https://i3d.net/support/

[Network Maintenance] Router Component Reload - Paris – August 7, 2025

Dear Client,

We would like to notify you of upcoming network maintenance activities that will affect services in our Paris datacenter. The network maintenance has been scheduled for August 7, 2025.

Location: Paris, France

Schedule: Start time: August 7, 2025, 12:00 UTC End time: August 7, 2025, 14:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: The maintenance is required to address a potentially faulty component in the network switch.

Expected impact: During this maintenance there will be reduced redundancy. Prior to reloading the potentially faulty component, all traffic will be drained from the router.

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

Thursday 2nd, September 2021

Phone support Our phone support is currently offline

At this moment we are experiencing problems with: Our phone helpdesk is currently unavailable.

The cause of the incident is currently: unknown

Estimated time of repair: unknown

Impact: Customers are not able to get in contact with I3d.net customer support via the phone. The ticket system is still operational

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.

    • Wednesday 1st, September 2021

    API v3 i3D.net CDN/GLAD API down

    At this moment we are experiencing problems with: The CDN and GLAD APIs

    The cause of the incident is currently: Known

    Estimated time of repair: Unknown

    Impact: Connecting to the CDN and GLAD APIs is currently not possible.

    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.

    • Tuesday 31st, August 2021

    US: Newark Backbone link between our Montreal and Newark datacenters down

    At this moment we are experiencing problems with: Backbone link between our Montreal and Newark datacenters.

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    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 Montreal and Newark 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.

  • The fiber has been repaired and traffic is back to normal.

  • The cause has been identified as damaged fiber. Repair crews have been dispatched and are working to resolve the situation. No ETA at this time.

    • Monday 30th, August 2021

    NL: Rotterdam Smartdc Rotterdam - Power issue Suite 37, 38, 39 and 40

    At this moment we are experiencing problems with: Power issues in Suite 37, 38, 39 and 40

    The cause of the incident is currently: Unknown.

    We have taken the following actions to resolve the incident: We are investigating the root cause and in process of restoring power immediately

    Estimated time of repair: Unknown.

    Impact: Customers in these suites will experience an interruption in service.

    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 repair works have been completed and the power is back online on the impacted suites. Our datacenter team is hands off and this incident is fixed.

  • To repair the power we will need to replace a phase that will cause the A-feed of suites to go down starting around 10:45 UTC

  • The cause is known. We will work as hard as possible to restore the power and replace the broken phase. During the replacement the power will be interrupted once more.

  • Suite 40 is also affected.

    • Sunday 29th, August 2021

    No incidents reported

    Saturday 28th, August 2021

    No incidents reported

    Friday 27th, August 2021

    CA: Montreal Backbone link between our Montreal and Newark datacenters down

    At this moment we are experiencing problems with: Backbone link between our Montreal and Newark datacenters.

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    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 Montreal and Newark 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.

    • UA: Kyiv Backbone link between our Kiev and Warsaw datacenters down

    At this moment we are experiencing problems with: Backbone link between our Kiev and Warsaw datacenters.

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    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 Kiev and Warsaw 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.

    • Thursday 26th, August 2021

    US: Dallas Backbone link between our Chicago and Dallas datacenters down

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

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    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 Chicago and Dallas 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 has resolved this incident.

  • Our vendor reports they have identified a fiber cut. Further investigation is required. No ETR provided at this time.

    • CA: Montreal Backbone link between our Montreal and Newark datacenters down

    At this moment we are experiencing problems with: Backbone link between our Montreal and Newark datacenters.

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    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 Montreal and Newark 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 by our vendor, the link is back online.

    • US: Newark Backbone link between our London and Newark datacenters down

    At this moment we are experiencing problems with: Backbone link between our London and Newark datacenters.

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    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 London and Newark 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.

  • Field personnel have located the exact point of damage and determined the fiber was damaged due to rats. They are currently devising a repair plan.

  • The fiber technicians tested the fiber and are en route to an alternate location. Field personnel are expected to arrive at the alternate site at approximately 10:30 UTC

  • The outage is due to a fiber cut. A fiber team has been engaged but an ETA is unavailable at this time.