Live / Phenom / Incident
Phenom: Potential performance degradation with Phenom Scheduling Services due to Microsoft Exchange Incident
Phenom · phenom.comMajor incidentResolved2026-11-14 09:54 UTC
Public — what happened
Summary
Phenom said its Scheduling service, and later its CRM Messaging service, were disrupted for customers who use Microsoft Exchange, beginning around 19:01 UTC on 2026-11-12. The company attributed the problem to an ongoing Microsoft Exchange outage and said Outlook users could miss 1-1 emails and campaigns, while recruiters could have trouble sending interview invitations and candidates could have trouble booking slots. Phenom said Microsoft later reported sustained recovery but was still working through delayed emails, and the incident was marked resolved at 09:54 on 2026-11-14.
Affected
Scheduling_US, Scheduling-Staging_US, Scheduling-EU, Scheduling-Staging_EU, Scheduling-CA, Scheduling-Staging_CA, Scheduling-IN, Scheduling-Staging_IN, Scheduling-CR, Scheduling-Staging_CR
Timeline
- Started — 2026-11-12 19:01 UTC
- Monitoring — 2026-11-12 19:01 UTC (7 updates)
- Resolved — 2026-11-14 09:54 UTC · 38h 53m 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 47, 2026, our weekly internet health report.