Unity Outage History

Unity's Friends, Lobby, and Leaderboards services experienced degraded performance for 2.6 hours. The team identified the root cause and actively worked on a solution. All affected services returned to stable operation and the incident was resolved.

Unity DevOps experienced inaccurate reporting of Seats and Concurrency usage data in the Cost & Usage dashboard for March and April 2026, lasting 44.4 hours. While March invoices remained accurate, April invoices required correction before billing finalization. The incident was resolved with corrected usage reporting restored to the dashboard.

Unity's Windows Builders service became unresponsive for 4.8 hours, affecting build queue performance. The monitoring system detected the outage and the team investigated the issue. The service was restored after nearly 5 hours of downtime.

Unity's Windows Builders service became unresponsive, causing a service queue performance issue. The monitoring system detected the outage and the team began investigating immediately. The service was restored after 4 minutes.

Unity's Mac Builders service became unresponsive for 12 minutes, causing a major service disruption. The monitoring system detected the outage and the team investigated the issue. The service was restored after 12 minutes of downtime.

Unity's Matchmaker service experienced an issue that affected a small subset of users who were using cloud code to handle allocations. The incident lasted 40 minutes while the engineering team investigated and resolved the problem.

Unity's Cost & Usage dashboard displayed inflated Standard Storage usage values for March and April 2026, affecting usage reporting and potentially causing billing concerns for users. The issue was resolved by fixing the storage usage calculation method and recalculating data across all accounts, with corrected values appearing automatically in dashboards once the multi-day recalculation process completed. March invoices were ensured to reflect accurate storage usage and pricing.

Unity Player Authentication experienced a major issue where the sign-in callback failed to return users to their applications after browser authentication, primarily affecting new sign-ins while previously authenticated users could still access accounts through cached sessions. The incident lasted 22.1 hours and was resolved after local testing confirmed successful logins for both existing and new users.

Unity Login experienced a major service outage lasting 52 minutes. The incident prevented users from accessing Unity's authentication system. The service team worked to resolve the login issues during this period.

Unity's Issue Tracker experienced degraded performance for 2.3 hours due to high CPU usage, causing slow response times for users. The service remained operational but with reduced performance throughout the incident. A fix was deployed and the system was monitored until full recovery.