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/

[Network Maintenance] Switch Reboot – Ashburn – August 12, 2025

Dear Client,

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

Location: Ashburn, USA

Schedule: Start time: August 12, 2025, 06:00 UTC End time: August 12, 2025, 07:30 UTC Planned impact: Impact expected (see below for details)

Reason for this maintenance: We will be performing a corrective maintenance on one of our switches to prevent a possible failure in the future due to a known bug in the device.

Expected impact: We will be performing a device reboot. As the device will be power cycled, full loss of connectivity should be expected during the maintenance window.

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 21st, April 2022

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: No ETR available at this time.

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 vendor repaired the fiber break. This incident is now resolved as traffic has been restored and vendor reported hands off.

    • Wednesday 20th, April 2022

    DK: Copenhagen Backbone link between our Copenhagen and Amsterdam datacenters

    At this moment we are experiencing problems with: Backbone link between our Copenhagen and Amsterdam 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 have reached out to our vendor for investigation.

    Estimated time of repair: Not available at this time.

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

    • 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.

  • We are receiving traffic again. As we have no hands off yet we will monitor this link.

  • This incident is caused by vendor maintenance surpassing its maintenance window. We are following up with the vendor for details as traffic did not restore after the maintenance completion.

    • Tuesday 19th, April 2022

    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: Unknown

    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 has been resolved.

    • Monday 18th, April 2022

    ES: Madrid Backbone link between our Madrid and Johannesburg datacenters down

    At this moment we are experiencing problems with: Backbone link between our Madrid and Johannesburg 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 Madrid and Johannesburg 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 is stable for about 10 hours now, but we have still not received the hands off from our vendor. We are following up accordingly.

  • We see that traffic has been restored. As we have no hands off from our vendor, we will keep monitoring this link.

  • Our vendor reported the cause to be a fiber cut in Spain. No ETR has been shared yet.

    • Sunday 17th, April 2022

    No incidents reported

    Saturday 16th, April 2022

    IN: Mumbai Backbone link between our Mumbai and Singapore datacenters down

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

  • After monitoring restoration of services, we consider this issue cleared.

  • We see traffic has been restored. As we have no hands off from our vendor yet we will monitor this link until then.

    • Friday 15th, April 2022

    No incidents reported

    Thursday 14th, April 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: No ETR available at this time.

    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.

    • US: Santa Clara Connectivity issues Santa Clara

    At this moment we are experiencing problems with: Connectivity in our Santa Clara datacenter

    The cause of the incident is currently: Unknown

    We have taken the following actions to resolve the incident: Our engineers are working to resolve this incident

    Estimated time of repair: No ETR available at this time

    Impact: Due to the current incident services in our Santa Clara datacenter are currently unavailable

    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.