Live / Phenom / Incident
Phenom: Proactive Notification - Potential performance degradation with Phenom Scheduling Services due to Microsoft Teams Incident
Phenom · phenom.comMinor incidentResolved2026-09-25 00:55 UTC
Public — what happened
Summary
Phenom posted an advance warning on September 24, 2026 at 20:24 UTC that its Scheduling services might run slower than usual, which it linked to an incident at Microsoft Teams. Phenom said it kept watching the Microsoft situation, and that Microsoft later reported the problem was recovering and stable again. Phenom then said its Scheduling services were working normally with no further problems seen, and marked the matter resolved at 00:55 on September 25. Customers who still have trouble were asked to open a support ticket.
Timeline
- Started — 2026-09-24 20:24 UTC
- Resolved — 2026-09-25 00:55 UTC · 4h 30m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Phenom against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Phenom: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Phenom report →
More from Phenom
Covered in The Squid’s Ink, Week 40, 2026, our weekly internet health report.