Join.me incident

Pro and Central - Outlook and Microsoft 365

Major Resolved View vendor source →

Join.me experienced a major incident on January 22, 2026 affecting Grasshopper and Pro/Central and 1 more component, lasting 23h 53m. The incident has been resolved; the full update timeline is below.

Started
Jan 22, 2026, 10:19 PM UTC
Resolved
Jan 23, 2026, 10:13 PM UTC
Duration
23h 53m
Detected by Pingoru
Jan 22, 2026, 10:19 PM UTC

Affected components

GrasshopperPro/CentralAdministration Portal

Update timeline

  1. identified Jan 22, 2026, 10:10 PM UTC

    We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will continue to update this incident as more information becomes available.

  2. identified Jan 22, 2026, 10:19 PM UTC

    We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will continue to update this incident as more information becomes available.

  3. identified Jan 22, 2026, 10:19 PM UTC

    We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will continue to update this incident as more information becomes available.

  4. identified Jan 22, 2026, 10:21 PM UTC

    We are aware of an incident impacting Microsoft 365 and Microsoft Outlook users. Microsoft has acknowledged the incident and is actively investigating on their side. Microsoft's incident channel is https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect We will continue to update this incident as more information becomes available.

  5. identified Jan 23, 2026, 04:12 AM UTC

    Microsoft is continuing to address the ongoing Microsoft 365 service incident. Microsoft reports improvements in availability, but recovery efforts are still in progress, and some users may continue to experience intermittent impact. For the latest updates, please refer to Microsoft’s status page: https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect. We will continue to share updates as more information becomes available.

  6. monitoring Jan 23, 2026, 01:22 PM UTC

    Microsoft is confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.

  7. resolved Jan 23, 2026, 10:13 PM UTC

    We have confirmed that the issue has been resolved and that all systems are 100% operational. We will conduct an internal review of this issue and make appropriate improvements to our system to help prevent or minimize future recurrence.