Global Alerting Platform Outage History

Global Alerting Platform is up right now

Pingoru has recorded 45 incidents for Global Alerting Platform: 1 in the last 12 months and 0 in the last 90 days.

Source: status.globalalerting.com

45incidents recorded
1last 12 months
0last 90 days
7 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Global Alerting Platform in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 516 (0%)

Incidents, newest first

Major October 29, 2025 Microsoft Azure incident 6h 56m Customer Portal (Australia East), SMS, Customer Portal (US East), Customer Portal (UK South) and 25 more

Started Oct 29, 2025, 07:22 PM UTC· resolved Oct 30, 2025, 02:18 AM UTC

  1. monitoring Oct 29, 2025, 07:22 PM UTC

    Microsoft has experienced a worldwide outage for a subset of their services which has impacted GAP web applications, including the GAP Portal, GAP Insights, GAP Reports and the GAP Web API. Integrations with third parties that rely on HTTPS connectivity to GAP are also affected. Message processing for devices that do not use an HTTPS bearer are not affected. Microsoft is working to restore service and further updates will be provided in due course.

  2. monitoring Oct 29, 2025, 08:38 PM UTC

    Service is being restored however some regions may continue to experience intermittent connectivity over the coming hours. Further updates will be provided as required.

  3. monitoring Oct 29, 2025, 10:34 PM UTC

    Microsoft is continuing to work to restore full service and widespread connectivity issues are no longer being observed. Some performance degradation is present for inbound HTTPS requests, and this is being monitored closely. Further updates will be provided in due course.

  4. resolved Oct 30, 2025, 02:18 AM UTC

    This incident has been resolved.

Read the full incident report →