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 here 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 by phone on the following phone numbers:

+31 (0)10 890 00 70

+1 800 482 6910

Support open:

Mon - Fri 00:00 - 00:00 UTC

Sat - Sun 08:00 - 16:00 UTC

Maintenance
[Network Maintenance] Montreal – WAN Router Upgrade – October 14th, 2021

Start of maintenance: October 14th, 13:00 UTC

End of maintenance: October 14th, 17:00 UTC

Reason of maintenance: i3D.net will be performing planned network maintenance in our Montreal datacenter to upgrade the WAN router and migrating circuits to this new router. This maintenance is necessary to facilitate further growth of the Montreal datacenter, as well as serving to make the aggregation core more resilient and flexible.

Expected downtime/impact: There will be reduced backbone redundancy and capacity between Montreal and Paris. There may be increased latency between Montreal and Toronto.

Support: During this maintenance, our support department will be available to assist you with any questions you may have. 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.

Past Incidents

Tuesday 19th, October 2021

No incidents reported

Monday 18th, October 2021

RU: Moscow Backbone link between our Moscow and Kiev datacenters down

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

The cause of the incident is currently: Known, fibercut

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

Sunday 17th, October 2021

No incidents reported

Saturday 16th, October 2021

No incidents reported

Friday 15th, October 2021

No incidents reported

Thursday 14th, October 2021

DK: Copenhagen Network incident Copenhagen datacenter

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

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

Impact: Due to the current incident on our router in our Copenhagen datacenter, 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 issue has been resolved.

    • Wednesday 13th, October 2021

    PL: Warsaw Backbone link between our Warsaw and Moscow datacenters down

    At this moment we are experiencing problems with: Backbone link between our Warsaw and Moscow 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 Warsaw and Moscow 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 reported this issue is resolved and we can confirm service has returned.

    • RU: Moscow Backbone link between our Moscow and Kiev datacenters down

    At this moment we are experiencing problems with: Backbone link between our Moscow and Kiev 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 Moscow and Kiev 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 reported this issue is resolved and we can confirm service has returned.