BrickVerse Status - Incident history https://brickverse.instatus.com BrickVerse Thu, 21 May 2026 13:21:06 +0000 API is back up Type: Incident Affected Components: API May 21, 13:41:06 GMT+0 - Resolved - API is back up. This incident was automatically resolved by Instatus monitoring. May 21, 13:21:06 GMT+0 - Investigating - API is down at the moment. This incident was automatically created by Instatus monitoring. Type: Incident

Affected Components:

<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>13:41:06</var> GMT+0</small><br><strong>Resolved</strong> - API is back up. This incident was automatically resolved by Instatus monitoring..</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>13:21:06</var> GMT+0</small><br><strong>Investigating</strong> - API is down at the moment. This incident was automatically created by Instatus monitoring..</p> ]]> Thu, 21 May 2026 13:21:06 +0000 https://brickverse.instatus.com/incident/cmpfir9b1001jsd15til81d8i https://brickverse.instatus.com/incident/cmpfir9b1001jsd15til81d8i API is back up Type: Incident Affected Components: API May 6, 05:20:48 GMT+0 - Investigating - API is down at the moment. This incident was automatically created by Instatus monitoring. May 6, 05:30:55 GMT+0 - Resolved - API is back up. This incident was automatically resolved by Instatus monitoring. May 6, 05:39:07 GMT+0 - Postmortem - # 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. Type: Incident

Affected Components:

<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>05:20:48</var> GMT+0</small><br><strong>Investigating</strong> - API is down at the moment. This incident was automatically created by Instatus monitoring..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>05:30:55</var> GMT+0</small><br><strong>Resolved</strong> - API is back up. This incident was automatically resolved by Instatus monitoring..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>05:39:07</var> GMT+0</small><br><strong>Postmortem</strong> - # 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..</p> ]]> Wed, 6 May 2026 05:20:48 +0000 https://brickverse.instatus.com/incident/cmotlztfw00d4k56fzk66pk9w https://brickverse.instatus.com/incident/cmotlztfw00d4k56fzk66pk9w Maintenance Update – Guild Channels Type: Maintenance Duration: 2 hours Affected Components: API, Guild Channel Bots, Guild Channel Web Messaging Socket Apr 15, 16:00:00 GMT+0 - Identified - We are currently performing maintenance to address several issues reported with **Guild Channels**. Our team is actively working to resolve these problems and improve overall stability and performance. During this time, Guild Channels may be temporarily unavailable or experience intermittent disruptions. We appreciate your patience while we make these improvements to ensure a smoother and more reliable experience. Further updates will be provided as progress continues. — BrickVerse Team Apr 15, 16:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 15, 18:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 2 hours

Affected Components: , ,

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are currently performing maintenance to address several issues reported with **Guild Channels**. Our team is actively working to resolve these problems and improve overall stability and performance. During this time, Guild Channels may be temporarily unavailable or experience intermittent disruptions. We appreciate your patience while we make these improvements to ensure a smoother and more reliable experience. Further updates will be provided as progress continues. — BrickVerse Team.</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>16:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Wed, 15 Apr 2026 16:00:00 +0000 https://brickverse.instatus.com/maintenance/cmnzmux3d025vpdj3ohe28bjd https://brickverse.instatus.com/maintenance/cmnzmux3d025vpdj3ohe28bjd API is back up Type: Incident Affected Components: API Apr 15, 05:58:03 GMT+0 - Investigating - API is down at the moment. This incident was automatically created by Instatus monitoring. Apr 15, 07:28:10 GMT+0 - Resolved - API is back up. This incident was automatically resolved by Instatus monitoring. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>05:58:03</var> GMT+0</small><br><strong>Investigating</strong> - API is down at the moment. This incident was automatically created by Instatus monitoring..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>07:28:10</var> GMT+0</small><br><strong>Resolved</strong> - API is back up. This incident was automatically resolved by Instatus monitoring..</p> ]]> Wed, 15 Apr 2026 05:58:03 +0000 https://brickverse.instatus.com/incident/cmnzn2tr3000pl37uzywlql3r https://brickverse.instatus.com/incident/cmnzn2tr3000pl37uzywlql3r Service Maintenance Type: Maintenance Duration: 1 hour and 12 minutes Affected Components: Website, API, Asset Delivery Network, AI Vision Content Moderation, AI Speech Content Moderation Apr 11, 21:30:00 GMT+0 - Identified - We are performing maintenance on our Database and S3 Storage to optimize thumbnail storage and delivery for de-duplication. Backend will remain offline until services are restored. Apr 11, 21:30:01 GMT+0 - Identified - Maintenance is now in progress Apr 11, 22:42:05 GMT+0 - Completed - **Maintenance Completed** All scheduled maintenance on our Database and S3 storage systems has been successfully completed. Thumbnail de-duplication, storage optimizations, and infrastructure improvements have been fully implemented. All assets have been re-rendered and verified, and systems are now operating on the new shared file architecture. **Deployment Update** We are now deploying the updated backend services. During this phase, some features may come online gradually as systems warm up and caches are rebuilt. Full service availability will be restored shortly. Thank you for your patience while we rolled out these improvements to enhance performance, scalability, and reliability across the platform. Type: Maintenance

Duration: 1 hour and 12 minutes

Affected Components: , , , ,

<p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>21:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are performing maintenance on our Database and S3 Storage to optimize thumbnail storage and delivery for de-duplication. Backend will remain offline until services are restored..</p> <p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>21:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>22:42:05</var> GMT+0</small><br><strong>Completed</strong> - **Maintenance Completed** All scheduled maintenance on our Database and S3 storage systems has been successfully completed. Thumbnail de-duplication, storage optimizations, and infrastructure improvements have been fully implemented. All assets have been re-rendered and verified, and systems are now operating on the new shared file architecture. **Deployment Update** We are now deploying the updated backend services. During this phase, some features may come online gradually as systems warm up and caches are rebuilt. Full service availability will be restored shortly. Thank you for your patience while we rolled out these improvements to enhance performance, scalability, and reliability across the platform..</p> ]]> Sat, 11 Apr 2026 21:30:00 +0000 https://brickverse.instatus.com/maintenance/cmnuuu5ar03ido8twut8y4vqn https://brickverse.instatus.com/maintenance/cmnuuu5ar03ido8twut8y4vqn API is back up Type: Incident Affected Components: API Apr 8, 20:28:45 GMT+0 - Investigating - API is down at the moment. This incident was automatically created by Instatus monitoring. Apr 8, 21:08:46 GMT+0 - Resolved - API is back up. This incident was automatically resolved by Instatus monitoring. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>20:28:45</var> GMT+0</small><br><strong>Investigating</strong> - API is down at the moment. This incident was automatically created by Instatus monitoring..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>21:08:46</var> GMT+0</small><br><strong>Resolved</strong> - API is back up. This incident was automatically resolved by Instatus monitoring..</p> ]]> Wed, 8 Apr 2026 20:28:44 +0000 https://brickverse.instatus.com/incident/cmnqi3l6u01aog9sgljk8w2ky https://brickverse.instatus.com/incident/cmnqi3l6u01aog9sgljk8w2ky API is back up Type: Incident Affected Components: API Apr 8, 01:08:03 GMT+0 - Resolved - API is back up. This incident was automatically resolved by Instatus monitoring. Apr 8, 00:08:04 GMT+0 - Investigating - API is down at the moment. This incident was automatically created by Instatus monitoring. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>01:08:03</var> GMT+0</small><br><strong>Resolved</strong> - API is back up. This incident was automatically resolved by Instatus monitoring..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>00:08:04</var> GMT+0</small><br><strong>Investigating</strong> - API is down at the moment. This incident was automatically created by Instatus monitoring..</p> ]]> Wed, 8 Apr 2026 00:08:02 +0000 https://brickverse.instatus.com/incident/cmnpahr3909wyoasxf7ulmpf4 https://brickverse.instatus.com/incident/cmnpahr3909wyoasxf7ulmpf4