Modern Campus Outage History

Modern Campus is up right now

Modern Campus had 3 outages in the last 2 years totaling 23h 4m of downtime — averaging 0.1 incidents per month.

There were 3 Modern Campus outages since October 1, 2025 totaling 23h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.presence.io

Major October 29, 2025

Azure Platform Outage

Detected by Pingoru
Oct 29, 2025, 07:09 PM UTC
Resolved
Oct 30, 2025, 12:49 PM UTC
Duration
17h 40m
Timeline · 1 update
  1. resolved Oct 30, 2025, 12:49 PM UTC

    Microsoft has confirmed that the issue causing latency, timeouts, and access errors for customers and Microsoft services has been resolved. Microsoft has completed mitigation efforts and continues to monitor node performance and overall connectivity to ensure full stability. We are observing the return of normal performance and load times across the Involve platform, and no ongoing impact is expected. This incident was global and limited to Microsoft Azure infrastructure, not specific to Involve. We apologize for any inconvenience this may have caused and appreciate your patience while Microsoft worked to resolve the issue.

Read the full incident report →

Major October 29, 2025

Microsoft Azure Platform Outage

Detected by Pingoru
Oct 29, 2025, 04:37 PM UTC
Resolved
Oct 29, 2025, 09:11 PM UTC
Duration
4h 33m
Timeline · 1 update
  1. resolved Oct 29, 2025, 09:11 PM UTC

    Microsoft has confirmed that the issue causing latency, timeouts, and access errors for customers and Microsoft services has been resolved. Microsoft has completed mitigation efforts and continues to monitor node performance and overall connectivity to ensure full stability. We are observing the return of normal performance and load times across the Involve platform, and no ongoing impact is expected. This incident was global and limited to Microsoft Azure infrastructure, not specific to Involve. We apologize for any inconvenience this may have caused and appreciate your patience while Microsoft worked to resolve the issue.

Read the full incident report →