All systems are operational.
This page provides general status updates and alerts for systems that i2m manages, either directly or on behalf of our clients. If you’re unable to access the internet from your site, check here. Hearing about a large-scale tech outage and wondering if it’s affecting you? Check here. Having issues accessing a cloud based resource? Check here. For issues that are specific to an individual client, the post will include that client’s three-letter i2m code. If you’re unsure of your client code, please contact support at support@i2m.solutions. This page displays only days with reported events from the past 30 days.
Last updated 2026-03-16 17:16:50
Last updated 2026-03-16 17:12:46
Last updated 2026-03-16 17:16:23
Last updated 2026-03-18 18:19:32
Last updated 2026-03-18 18:29:55
Last updated 2026-03-18 19:27:30
See below for specific component that is affected.
Following our earlier updates, recovery is continuing for customers hosted on our US-B grid. The team has made changes to DNS routing among several other mitigation steps with positive results. We are no longer seeing the elevated rate of DNS resolution errors. There may still be delays in email delivery as queued email clears per the retry schedule.
We will continue to closely monitor mail flow and application performance and will provide further updates as they become available.
We believe we have identified the issue affecting some customers hosted on our US-B grid who experienced temporary DNS record lookup errors. We are seeing a gradual decrease in temporary DNS resolution errors as mitigation steps take effect. Customers on the US-B grid should continue to see improvement in DNS resolution performance. We will provide further updates as they become available.
We are aware that some customers hosted on our US-B grid may be experiencing degraded deliverability due to increase in temporary DNS resolution failures. We are currently investigating the issue and updates will be posted here as they become available.
i2m has confirmed that clients are currently being affected by this outage/incident
We've concluded our extended period of monitoring and confirmed impact has not reoccurred.
Currently, the affected web client, office.com is still impacted. After applying configuration changes and rebalancing the request traffic, the previously impacted Microsoft 365 Copilot web-clients, office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft, have recovered as of Tuesday, March 17, 2026 at 12:05 PM EDT . We've identified additional configuration changes and are proceeding to roll these out to the affected infrastructure.
We've identified that impact associated with MO1253428 has started to reoccur. We're reviewing traffic pattern telemetry and applying configuration changes to optimize connections and remediate impact.
Work to optimize the traffic to the affected section of service infrastructure continues. MS has made additional configuration changes and are monitoring our service side telemetry to verify its effectiveness.
Issue ID: MO1253428 Affected services: Microsoft 365 Copilot Chat, Microsoft 365 suite, Microsoft Copilot (Microsoft 365) Status: Service degradation Issue type: Incident Start time: Mar 16, 2026, 10:23 AM EDT
User impact Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info The impacted web-client is office.com, and impacted Microsoft 365 Copilot web-clients are office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes, but is not limited to:
Scope of impact Impact is specific to some users who are served through the affected infrastructure.
Current status Mar 16, 2026, 10:28 AM EDT We've identified that a section of service infrastructure is not processing traffic efficiently. We're making configuration changes to remediate impact. Next update by: Monday, March 16, 2026 at 12:30 PM EDT
i2m has not recieved any reports of the outage affecting i2m clients.
Issue ID: MO1245624 Affected services: Microsoft 365 suite Status: Service degradation Issue type: Incident Start time: Mar 6, 2026, 10:18 AM EST
User impact Users in the North American region may be unable to access multiple Microsoft 365 services.
More info Impacted services include, but are not limited to:
Scope of impact Impact is specific to some users located in North American region attempting to access the Microsoft 365 admin center, Microsoft Teams and SharePoint Online.
i2m has recieved no reports yet on this issue affecting our clients