Live / Phenom / Incident
Phenom: Potential performance degradation with Phenom Scheduling Services
Phenom · phenom.comMinor incidentResolved2026-10-02 04:33 UTC
Public — what happened
Summary
Phenom reported a minor issue with its Phenom Scheduling Services starting on 2026-10-01 at 13:37 UTC, warning that customers who use Microsoft Teams might see small disruptions or slower performance. The company attributed the problem to a separate, ongoing service degradation at Microsoft Teams. By 18:35 UTC that day, Phenom said scheduling was working normally with no failures in the prior three hours, though it kept watching while awaiting confirmation that the outside problem was fully fixed. The incident was marked resolved on 2026-10-02 at 04:33.
Timeline
- Started — 2026-10-01 13:37 UTC
- Monitoring — 2026-10-01 13:37 UTC (2 updates)
- Resolved — 2026-10-02 04:33 UTC · 14h 56m 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 41, 2026, our weekly internet health report.