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
[Network Maintenance] Atlanta – Router Maintenance – January 9, 2025

Dear client,

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

Location: Atlanta, Georgia – United States

Schedule: Start time: January 9, 2025, 09:00 UTC End time: January 9, 2025, 13:00 UTC Planned downtime: Reduced redundancy (see below for details)

Reason for this maintenance: We will be performing a routine upgrade on our routers to improve quality and ensure long-term reliability.

Expected downtime/impact: No operational impact is expected. There will be reduced redundancy for up to 90 minutes as each router is rebooted and brought back into service.

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] Singapore - Router Maintenance - January 13, 2025

Dear client,

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

Location: Singapore

Schedule: Start time: January 13, 2025, 21:00 UTC End time: January 14, 2025, 01:00 UTC Planned impact: Reduced redundancy (see below for details)

Reason for this maintenance: We will be performing a routine upgrade on our routers to improve quality and ensure long-term reliability.

Expected impact: For servers in the data center no operational impact is expected. There will be reduced redundancy for up to 90 minutes as each router is rebooted and brought back into service.

[Network Maintenance] Frankfurt– Router Maintenance – January 21, 2025

Dear client,

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

Location: Frankfurt, Germany

Schedule: Start time: January 21, 2025, 03:00 UTC End time: January 21, 2025, 07:00 UTC Planned downtime: Reduced redundancy (see below for details)

Reason for this maintenance: We will be performing a routine upgrade on our routers to improve quality and ensure long-term reliability.

Expected downtime/impact: No operational impact is expected. There will be reduced redundancy for up to 90 minutes as each router is rebooted and brought back into service.

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/

You can find maintenance updates and the current situation at  https://status.i3d.net/

[Network Maintenance] London – Router Maintenance – January 30, 2025

Dear client,

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

Location: London, Great Britain

Schedule: Start time: January 30, 2025, 09:00 UTC End time: January 30, 2025, 11:00 UTC Planned downtime: Slight increase in latency (see below for details)

Reason for this maintenance: We will be performing a routine upgrade on our routers to improve quality and ensure long-term reliability.   Expected downtime/impact: There will be a slightly increased latency because of traffic rerouting during the maintenance window, up until the router is brought back into service.

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

Saturday 29th, June 2024

US: Dallas Backbone link between our Chicago and Dallas data centers down

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

  • Vendor reported back that this was the result of a fiber cut and have sent technicians to repair it. After repairs have been completed the services were restored immediately.

    • Friday 28th, June 2024

    US: Chicago Backbone link between our San Jose and Chicago data centers down

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

  • Equipment failure, faulty card has been replaced.

    • UA: Kyiv Backbone link between our Kyiv and Bucharest data centers down

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

    • US: Ashburn Backbone link between our Saint-Denis and Ashburn data centers down

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

  • Maintenance is completed and services were restored.

  • Per the vendor, this was the result of a maintenance in progress.

    • Thursday 27th, June 2024

    SG: Singapore Backbone link between our Saint-Denis and Singapore data centers down

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

  • Subsea cable fault has been repaired. This is a duplicate Incident of the https://status.i3d.net/incidents/1485.

  • Vendor reported back saying this link was affected due to ongoing SMW5 Subsea fault and repair operation.

    • DE: Frankfurt Backbone link between our Frankfurt and Heerlen data centers down

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

    • PL: Warsaw Backbone link between our Warsaw and Moscow data centers down

    At this moment, we are experiencing problems with: Backbone link between our Warsaw and Moscow 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 Warsaw and Moscow 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 incident is resolved.

    • DE: Frankfurt Backbone link between our Frankfurt and Heerlen data centers down

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

    Wednesday 26th, June 2024

    Backbone link between our Moscow and Hong Kong data centers down

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

    • RO: Bucharest Backbone link between our Milan and Bucharest data centers down

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

    • US: Dallas Backbone link between our Dallas and Chicago data centers down

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

    • US: Atlanta Backbone link between our Atlanta and Chicago data centers down

    At this moment, we are experiencing problems with: Backbone link between our Atlanta and Chicago 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 Atlanta and Chicago 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 incident was posted in error.

    • US: Chicago Backbone link between our Ashburn and Chicago data centers down

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

    • Tuesday 25th, June 2024

    ES: Madrid Backbone link between our Paris and Madrid data centers down

    At this moment, we are experiencing problems with: Backbone link between our Paris and Madrid data centers.

    The cause of the incident is currently: Our vendor is performing a hardware replacement.

    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 1 and 2 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 incident is resolved.

  • Our provider identified a card failure. Onsite personnel will shortly replace the faulty equipment.

    • PL: Warsaw Backbone link between our Warsaw and Moscow data centers down

    At this moment, we are experiencing problems with: Backbone link between our Warsaw and Moscow 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 Warsaw and Moscow 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 incident is resolved.

    • Monday 24th, June 2024

    Backbone link between our Bucharest and Kyiv data centers down

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

    • Sunday 23rd, June 2024

    US: Newark Backbone link between our Toronto and Newark data centers down

    At this moment, we are experiencing problems with: Backbone link between our Toronto and Newark 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 Toronto and Newark 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 incident is resolved.

  • Restoration work has been finished, but our provider is not yet hands of.

  • Vendor has confirmed there is a fiber cut and has sent their engineers to fix the issue now.