Service issues › PL1490629
Some users may see initial page loading failures and 500 errors within Microsoft Planner
- Started
- 28 Sep 2026 11:00 UTC
- Resolved
- 07 Oct 2026 18:04 UTC
- Status
- serviceRestored
- Origin
- microsoft
Timeline & resolution
07 Oct 2026 19:40 UTC · regular
Title: Some users may see initial page loading failures and 500 errors within Microsoft Planner
User impact: Users may have seen initial page loading failures and 500 errors within Microsoft Planner.
Final status: We've isolated a subset of Microsoft Planner service infrastructure that dropped below our manageable service performance thresholds due to a networking issue, resulting in impact. After rerouting service traffic to alternate available infrastructure, our telemetry has verified that the impact has been remediated.
Scope of impact: This issue could have caused any user to see initial page loading failures or 500 errors within Planner.
Start time: Monday, September 28, 2026, at 11:00 AM UTC
End time: Wednesday, October 7, 2026, at 6:04 PM UTC
Root cause: A subset of Microsoft Planner service infrastructure experienced a networking issue that produced initial page failures and 500 errors within Planner.
Next steps:
- We're further analyzing the source of the networking issue that led to the affected service infrastructure’s lower-than expected performance levels to help us prevent similar issues in the future.
This is the final update for the event.
07 Oct 2026 19:04 UTC · regular
Title: Some users may see initial page loading failures and 500 errors within Microsoft Planner
User impact: Users may have seen initial page loading failures and 500 errors within Planner.
Current status: We've investigated a problem with the Microsoft Planner service in which some users experienced initial page loading failures or 500 errors within Microsoft Planner, and we’ve confirmed that service is now restored. We'll provide additional information in a closure summary within the “History” section of the “Service health” dashboard shortly.
© Microsoft — archived from Microsoft 365 service health. Content notice