Unity Outage History

Unity's Relay service experienced a partial outage affecting allocation functionality in the South America East region. The issue lasted 28 minutes while the engineering team investigated and triaged the problem. Users in the affected region experienced difficulties with resource allocation during this period.

Unity's Build Automation service experienced degraded performance specifically affecting Mac builds in the Europe region for 4.6 hours. The incident was classified as major severity and impacted users' ability to perform automated Mac builds through the Unity Build Automation platform. The service team investigated and restored normal performance after the 4.6-hour outage period.

Unity's leaderboard service experienced elevated latencies and error responses for 40 minutes. The engineering team investigated and triaged the issue. The incident was resolved with minor impact to the service.

Unity's Commerce platform experienced a 7.2-hour outage where customer orders could not be fulfilled for purchases and cancellations due to a partner system being down. The engineering team identified and fixed the root cause, then reprocessed all pending events to restore normal order fulfillment functionality.

Unity's Build Automation service experienced a major incident lasting 4.2 hours, causing Project Statistics and Build Target errors that prevented users from accessing these features. The engineering team identified the root cause and deployed a fix, restoring normal functionality to the affected pages.

Unity experienced a major service incident where automation creation and pipeline triggering functionality was completely unavailable for 2.6 hours. Users also reported that the Unity website, particularly the Learn section, failed to load during this period. The engineering team investigated and resolved the issue.

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.