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
[Vendor Power Maintenance] Vendor Maintenance - Sydney – July 14-20, 2025

We would like to notify you of upcoming emergency vendor maintenance activities that will affect services in our Sydney datacenter. The emergency vendor maintenance has been scheduled to start on July 14, 2025 and finish on July 20, 2025.

Location: Sydney, Australia

Schedule: Start time: July 14, 2025, 21:00 UTC End time: July 20, 2025, 08:00 UTC Planned impact: Impact expected (see below for details)

Reason for this maintenance:

The vendor is implementing improvements to the datacenter power delivery, requiring both the A- and B-feeds to be temporarily disconnected.

Expected impact: Full downtime / reduced redundancy.

During this emergency vendor power maintenance, our vendor will disconnect either the A- or B-feeds during daily maintenance windows from 21:00 - 08:00 UTC on July 14 until July 20.

If your server is connected redundantly this means one of the connected PSUs will be disconnected during these windows (reduced redundancy).

If your server is connected to a single power feed, this means full downtime for the duration of the maintenance works.

[Cooling Maintenance] Rotterdam – Data Center Air Supply Temperature Change – July 21, 2025

We would like to inform you of an upcoming cooling maintenance being performed in our Rotterdam datacenter. This maintenance is scheduled for July 22nd, 2025.

Location:

Rotterdam, The Netherlands

Schedule:

Start Time: July 21, 2025, 06:00 UTC

End Time: August 21, 2025, 18:00 UTC

Planned downtime:

No downtime is expected

Reason for this maintenance:

As part of our ongoing commitment to energy efficiency and environmental responsibility we will begin increasing the air supply temperature in our server rooms from 22°C to 24°C. This adjustment is being made to improve the overall energy efficiency of our facility, to ensure we continue complying with European regulatory guidelines and to reduce the load on our cooling systems.

Expected downtime/impact:

No downtime is expected.

[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/

Past Incidents

Saturday 22nd, April 2023

No incidents reported

Friday 21st, April 2023

US: Seattle Backbone link between our Seattle and Chicago datacenters down.

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

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 link has remained stable.

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

    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 Atlanta and Ashburn 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. Vendor is hands off.

  • Our link has been restored. We are still monitoring this link until we receive a hands-off from our vendor.

    • Thursday 20th, April 2023

    NL: Rotterdam Suite 23 - Cooling issues

    At this moment we are experiencing problems with: The cooling of Suite 23 in our Rotterdam datacenter

    The cause of the incident is currently: Known, broken fan

    We have taken the following actions to resolve the incident: Our engineers have compensated by increasing other fans

    Estimated time of repair: Fan has been replaced

    Impact: At this moment the temperatures in Suite 23 are slowly rising but are not yet reaching critical levels. After compensating for the failing fan temperatures stabilized.

    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.

  • Repairs have been completed. Broken fan was replaced and tested. We keep monitoring for temperature changes the following hours after which we will deem this incident as resolved.

  • Repair crew is currently replacing the broken fan. After replacement, tests will be performed to ensure correct operation where after fan balance will be restored and temperatures actively monitored.

  • Temperatures are stable. The increase as due to a broken cooling fan but we were able to utilize another unit to compensate. The broken fan will be repaired tomorrow as it is not doable now

  • Suite 23 is dropping to lower stable temperatures, however it is still higher than desired. Continued investigations may cause briefs temperatures increases for troubleshooting purposes.

    • UA: Kyiv 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.

  • Vendor identified services were caused by a fiber cut in Braila, Galati. Upon repairing the damaged cable, services were restored.

    • vCloud VM Portal unavailable

    At this moment, we are experiencing problems with: vCloud VM portal.

    The cause of the incident is currently: Unknown

    We have taken the following actions to resolve the incident: Our engineers are currently investigating the issue in order to resolve this incident.

    Estimated time of repair: Unknown.

    Impact: Due to the current incident on our vCloud environment customers are unable to access the VM portal.

    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 have identified the issue and are in progress of implementing the fix to resolve this incident.

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

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

  • Vendor identified a fault port on their OSP panel in Baltimore Maryland and upon repairing the damaged port, services were restored.

  • Vendor identified a possible fiber break in Baltimore MD and has sent a dispatch to investigate further.

    • Wednesday 19th, April 2023

    UA: Kyiv 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.

  • We have received confirmation from the vendor.

  • The link is up again and will be observed for stability. Awaiting hands-off.

    • Tuesday 18th, April 2023

    Backbone link between our Saint Petersburg and Stockholm datacenters is down

    At this moment we are experiencing problems with: Backbone link between our Saint Petersburg and Stockholm 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 Stockholm 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 has remained stable.

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

    At this moment, we are experiencing problems with: Backbone link between our Johannesburg and Madrid 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 Johannesburg and Madrid 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 see one of the links up, with confirmation from the vendor.

    • Monday 17th, April 2023

    NO: Oslo Backbone link between our Stockholm and Oslo datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Stockholm and Oslo datacenters.

    The cause of the incident is currently: our vendor has identified a complete cut on all fibers

    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 Stockholm and Oslo 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 is resolved

  • Services has been restored. Until then, we will be watching this link closely and update when we hear more from our vendor.

    • Sunday 16th, April 2023

    No incidents reported

    Saturday 15th, April 2023

    DE: Frankfurt Backbone link between our Frankfurt and Warsaw datacenters down

    At this moment, we are experiencing problems with: Backbone link between our Frankfurt and Warsaw 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 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 is resolved. We are in contact with our vendor for the root cause. Link has been stable for over 13-hours.