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

Thursday 14th, March 2024

SA: Johannesburg 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.

  • This link has remained stable. No further interruptions are expected.

  • We are seeing some traffic restored on the link. We are waiting for another update from our vendor on the status of the repairs.

  • According to WACS NOC, cable ship Sovereign is mobilized for repair operations. Repair is estimated tentatively between 18 – 28 Apr.

  • Repair ship has arrived as of April 8th and works have begun on to repair the SAT-3 cable (one of four major cables.) Two of the remaining cables (ACE and WACS) are expected to be restored on April 17th and April 28th, respectively. The fourth cable (MainOne) is projected to be the final cable to be repaired by May 9th.

  • Check out this article for more details. https://www.theguardian.com/technology/2024/mar/14/much-of-west-and-central-africa-without-internet-after-undersea-cable-failures

  • Our link is down related to a subsea cable fault. No ETR as of yet.

  • Past Incidents

    Thursday 26th, May 2022

    US: Ashburn Backbone link between our Atlanta and Ashburn datacenters down

    At this moment we are experiencing problems with: Backbone link between our Atlanta and Ashburn datacenters down.

    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 Atlanta and Ashburn datacenters, impact could be visible in the form of 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.

  • Link is restored

  • Wednesday 25th, May 2022

    GB: London 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 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 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.

  • Tuesday 24th, May 2022

    IT: Milan Incident Milan datacenter

    At this moment we are experiencing problems with: Incident in our Milan datacenter.

    The cause of the incident is currently: Unknown

    Estimated time of repair: No ETR available

    Impact: We briefly lost connection to our Milan datacenter.

    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 23rd, May 2022

    HK: Hong Kong Backbone link between our Hong Kong and Tokyo datacenters down

    At this moment we are experiencing problems with: Backbone link between our Hong Kong and Tokyo 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 Hong Kong and Tokyo 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.

  • Traffic has been restored on the link. As we have no hands off from out vender just yet we will closely monitor this link.

  • This incident is caused by a fiber cut reported by our vendor. The communicated ETR is expected to 14:00 UTC.

  • Sunday 22nd, May 2022

    US: Chicago Backbone link between our Seattle and Chicago datacenters flapping

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

  • DE: Frankfurt Backbone link between our Frankfurt and Rotterdam datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Frankfurt and Rotterdam 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 Frankfurt and Rotterdam 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 link is operational again.

  • Our Vendor has located the fiber cut. It is caused by a fire. Cause of Fire unknown.

  • NL: Rotterdam Backbone link between our Paris and Rotterdam datacenters down

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

  • Our Vendor has located the fiber cut. It is caused by a fire. Cause of Fire unknown

  • GB: London Backbone link between our London and Rotterdam datacenters down

    At this moment, we are experiencing problems with: Backbone link between our London and Rotterdam 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 London and Rotterdam 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 link is operational again

  • Our Vendor has located the fiber cut. It is caused by a fire. Cause of Fire unknown.

  • Saturday 21st, May 2022

    No incidents reported

    Friday 20th, May 2022

    HU: Budapest Backbone link between our Budapest and Bucharest datacenters down

    At this moment we are experiencing problems with: Backbone link between our Budapest 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 Budapest 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. The vendor is hands off

  • Our vendor reported a fiber cut. ETR is still unknown.

  • Thursday 19th, May 2022

    NL: Rotterdam Smartdc Rotterdam - Degraded cooling capacity Suite 23

    At this moment we are experiencing problems with: Degraded cooling capacity Suite 23.

    The cause of the incident is currently: Unknown.

    We have taken the following actions to resolve the incident: We are investigating the cause.

    Estimated time of repair: Unknown.

    Impact: Due to a difficulty with one of the cooling units, temperatures are fluctuating but still within norms. Colocation customers might see slightly higher temperatures than usual.

    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 has been completed. A new fan was installed and the cooling unit is operational again. We will monitor the temperatures closely this coming period. Our team is now hands off.

  • At this moment we are experiencing problems with: Degraded cooling capacity Suite 23.

    The cause of the incident is currently: Known, Faulty hardware component

    We have taken the following actions to resolve the incident: Replacement hardware has been ordered.

    Estimated time of repair: ETR is expected tomorrow May 20th, 2022.

    Impact: Due to a difficulty with one of the cooling units, temperatures are fluctuating but still within norms. Colocation customers might see slightly higher temperatures than usual.

  • RO: Bucharest Backbone link between our Budapest and Bucharest datacenters down

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

  • HK: Hong Kong Backbone link between our Hong Kong and Santa Clara datacenters down

    At this moment we are experiencing problems with: Backbone link between our Hong Kong and Santa Clara 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 Hong Kong and Santa Clara 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.