SharePoint Online outage on
March 6, 2026

Read more >

Improved SSO setup and
logging

Read more >

StatusGator logo
Schedule a Demo
StatusGator logo
Use cases

IT Teams

Stay informed of outages and reduce tickets

DevOps

One status page for all your providers

Education

Features designed specifically for K12

Enterprise

Advanced features designed for enterprise

Managed service providers

Impress clients with proactive monitoring

Competitive intelligence

Analyze and compare peer performance

Monitor dependencies to prevent revenue loss

Create and manage custom status pages for your product

Features

Status page

A status page with service, website, and custom monitors built-in

Status aggregation

Aggregate the status of all vendors to a single page

Cloud monitoring

Monitor all your cloud services from a single dashboard

Website monitoring

Monitor your website with uptime monitoring built-in

Monitor network connectivity

Control the status of custom monitors manually with incidents

Get notified of disruptions before they become public

Pricing

Business

From startup to enterprise and everything in between

Education

Special plans and discounts for K12 and higher ed

Integrations

Incident Management

Better Uptime
FireHydrant
Opsgenie
PagerDuty

Notifications

Private Status

AT&T status
AWS status
Azure status
Microsoft 365 status
Zendesk status

Status Pages

Atlassian Statuspage
StatusHub

Advanced

Sign In Sign Up

Microsoft Teams outage – December 10th, 2025

On the morning of December 10, 2025, Microsoft Teams experienced a service disruption affecting users across Australia. Although Microsoft 365 users reported issues across several apps, the hardest hit service was Microsoft Teams which became completely unusable for many organizations. While Microsoft did not acknowledge the incident until 03:46 UTC StatusGator identified the issue at 02:52 UTC through incoming outage reports and delivered an Early Warning Signal at 03:01 UTC. This gave StatusGator users a 45 minute advantage over those relying solely on the official Microsoft status page.

This case study shows how early detection from StatusGator helps organizations respond faster reduce downtime and stay informed even when providers are slow to acknowledge issues.

Timeline of events

02:52 UTC
First outage reports reach StatusGator from Australia.

02:56 to 03:12 UTC
Rapid escalation of reports describing frozen calls dropped sessions and reconnect failures

  • “Video call is frozen”
  • “Completely down”
  • “Current meeting everyone froze then the meeting ended. No one could get back in”

03:01 UTC
StatusGator issues an Early Warning Signal indicating likely Teams degradation.

03:12 UTC
Last major cluster of outage reports received as conditions begin to stabilize.

03:46 UTC
Microsoft publicly acknowledges the incident. On their X account, they state: “We’re investigating an issue impacting users in Australia attempting to access various Microsoft 365 services. We’re actively investigating the issue and we’ve observed some degrees of recovery. Further details can be found in your Microsoft 365 admin center under MO1193724.”

Impact on users

Although the broader Microsoft 365 ecosystem showed signs of instability according to external reporting Microsoft Teams took the brunt of the disruption. Users described

  • frozen or stalled video calls
  • inability to reconnect after being dropped
  • meetings ending abruptly for all participants
  • intermittent failure to load or join Teams sessions

The outage did not affect every region equally but in areas where it did hit the impact was severe and immediate especially for organizations relying on Teams for daily communication and live collaboration.

StatusGator insights

StatusGator provided a significant early detection advantage during this incident

  • user reports surfaced the issue at 02:25 UTC long before any official notice
  • the Early Warning Signal at 03:01 UTC delivered actionable insight 45 minutes before Microsoft confirmed the problem
  • real world telemetry highlighted a regional outage that Microsoft did not immediately acknowledge

Teams relying on StatusGator had the information needed to prepare communicate and reduce internal confusion well before the provider confirmed the issue. They could see exactly where outage reports were coming from on our outage map, and had a summary of the issue delivered by Early Warning Signals.

Lessons learned

  • Provider status pages often lag behind real user experience especially in geographically limited outages
  • User generated telemetry is one of the strongest early indicators of real world service instability
  • Proactive monitoring can save valuable time during critical service disruptions
  • Global teams benefit from multi region visibility since outages may not affect every geography equally

Stay ahead of the next outage

StatusGator helps thousands of teams detect outages early understand true service impact and stay informed through unified monitoring across every provider they depend on.

Try StatusGator today and stay ahead of your next incident
Start monitoring with StatusGator

Share this

Photo of author

Colin Bartlett

Colin Bartlett is co-founder of StatusGator and Nimble Industries, a seasoned Ruby engineer and entrepreneur who launched StatusGator in 2015 and later grew it into a full-fledged company.