Affected
Operational from 5:20 AM to 5:20 AM, Major outage from 5:20 AM to 5:30 AM
- PostmortemPostmortem
Authentication & API Service Outage Postmortem
Incident Summary
On May 5, 2026, BrickVerse experienced a temporary platform outage affecting authentication services and multiple API routes. Users were unable to log in, authenticate sessions, and access several platform-dependent features during the incident window.
The outage lasted approximately 16 minutes and has since been fully resolved.
Impact
During the incident, the following systems experienced degraded functionality or were unavailable:
User authentication/login
Session validation
API routes dependent on backend service discovery
Game server communication endpoints
Some creator/developer platform functionality
Users may have experienced:
Login failures
Infinite loading states
“Unauthorized” or server-related API errors
Temporary inability to join or manage game sessions
No data loss or security compromise occurred as a result of this incident.
Root Cause
The outage was caused by a configuration issue within our internal game server VM daemon management service responsible for orchestrating and maintaining backend service state across virtual machine infrastructure.
A configuration change resulted in backend service instability which disrupted communication between authentication infrastructure and several internal API dependencies.
This caused cascading failures across authentication and related API routes until the affected daemon configuration was identified and corrected.
Resolution
Engineering identified the configuration issue and:
Patched the problematic daemon configuration
Restarted affected orchestration services
Revalidated API connectivity and authentication flows
Monitored recovery across production systems
Full platform functionality was restored approximately 16 minutes after the incident began.
Closing Notes
All systems are currently operating normally.
- ResolvedResolvedAPI is back up. This incident was automatically resolved by Instatus monitoring.
- InvestigatingInvestigatingAPI is down at the moment. This incident was automatically created by Instatus monitoring.

