Parsec Outage History

Parsec'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.

Parsec experienced a major service disruption where automation creation and pipeline triggering functionality became completely unavailable for 2.6 hours. The incident affected users' ability to create new automations and trigger existing pipelines within the platform. The service team investigated and resolved the issue, restoring full functionality to the affected automation systems.

Parsec's Friends, Lobby, and Leaderboards services experienced degraded performance for 2.6 hours due to an identified root cause issue. The technical team worked actively on a solution and successfully restored stable operation to all affected services. The incident was resolved with continued monitoring to ensure service stability.

Parsec experienced inaccurate reporting of Seats and Concurrency usage data in their Cost & Usage dashboard for March and April 2026. The issue affected dashboard display values but did not impact March invoice accuracy, and April invoices were corrected before charges were finalized. The incident lasted 44.4 hours and was classified as minor severity.

Parsec's Windows Builders service became unresponsive, causing service queue performance issues. The monitoring system detected the outage and the team investigated the problem. The service was restored after 4.8 hours.

Parsec's Windows Builders service became unresponsive for 4 minutes, causing a minor service disruption. The monitoring system detected the issue and the team investigated the problem. The service was restored to normal operation within the brief 4-minute timeframe.

Parsec'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.

A minor incident affected a small subset of Parsec Matchmaker users who were using cloud code to handle allocations. The engineering team investigated and resolved the issue within 40 minutes.

Parsec's Cost & Usage dashboard displayed inflated Standard Storage usage values for March and April 2026, affecting usage reporting and potentially causing customer billing concerns. The issue was resolved by fixing the storage usage calculation method, ensuring March invoices reflected accurate usage and pricing. A multi-day recalculation process was initiated to correct historical data across all accounts, with corrected values appearing automatically in dashboards once complete.

Unity Player Authentication experienced a sign-in callback issue where users were not returned to the application after browser authentication, primarily affecting new sign-ins while previously authenticated users could still access accounts through cached sessions. The incident lasted 22 hours and was resolved after engineering teams conducted successful local testing for both existing and new user logins.