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

Past Incidents

Tuesday 3rd, August 2021

No incidents reported

Monday 2nd, August 2021

No incidents reported

Sunday 1st, August 2021

No incidents reported

Saturday 31st, July 2021

No incidents reported

Friday 30th, July 2021

PL: Warsaw Backbone link between Warsaw and Moscow is 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 reached out to our vendor for investigation.

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.

  • The situation has been resolved.

    • Thursday 29th, July 2021

    US: Chicago Backbone link between our Chicago and Dallas datacenters down

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

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    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 Chicago and Dallas 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 backbone link has returned to operation, but crews are still working and we have not received a hands off confirmation yet. We are continuing to monitor the situation.

  • Our vendor reports that they have identified a fiber cut and are working to get it repaired. No current ETR provided.

    • US: Dallas Backbone link between Dallas and Atlanta is down

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

    The cause of the incident is currently: Unknown. We have reached out to our vendor for investigation.

    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 Dallas and Atlanta 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 backbone link has returned to operation, but crews are still working and we have not received a hands off confirmation yet. We are continuing to monitor the situation.

  • Our vendor reports that they have identified a fiber cut and are working to get it repaired. No current ETR provided.

    • Wednesday 28th, July 2021

    No incidents reported

    Tuesday 27th, July 2021

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

    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.

  • The situation has been resolved.

  • Our vendor reports that a repair team is in transit to the fault site with an ETA of 19:30 UTC to continue work on isolating the fault source. Due to issues with access on-site, the current ETA for further updates is anticipated to be 23:00 UTC or later.

  • Our vendor has identified the fault location and has dispatched repair crews. No ETR at this time.