Princeton University Dashboard

The monitor is down in the following regions: us-east and us-west

We have completed our assessment of the impacted network equipment at the Equinix FR5 location in Frankfurt, DEU and now have a clear understanding of the scope of impact. We are making progress toward restoring connectivity and will be taking a phased approach to remediation. Customers with connections exclusively at this location will continue to experience packet loss until remediation is complete. Customers with multi-site or redundant configurations across other Direct Connect locations are not affected. We will provide another update by August 16 10:30 PM PDT, or sooner as new information becomes available.

Title: Users may be unable to sign in to OneNote using iOS devices User impact: Users may be unable to sign in to OneNote using iOS devices. More info: Impact is specific to users with OneNote build 16.112.717.0 or higher. Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote. Current status: We've identified that a code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact. We're deploying a code fix to correct this issue and expect that it'll complete deployment by the time of our next update. Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted. Start time: Monday, July 20, 2026, at 4:36 AM UTC Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact. Next update by: Tuesday, August 18, 2026, at 6:00 AM UTC

We're continuing to investigate an issue affecting a subset of channels with custom message retention settings. Custom channel retention settings have been restored for affected customers. Custom retention jobs remain on hold for some customers as we work to fully resolve the underlying cause regarding the custom message retention issues.