BrickVerse - Notice history

Experiencing partially degraded performance

Website - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

API - Operational

100% - uptime
Apr 2026 · 99.22%May · 99.93%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

Asset Delivery Network - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

AI Vision Content Moderation - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

AI Speech Content Moderation - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

Forum - Operational

100% - uptime
Apr 2026 · 100.0%May · 100.0%Jun · 100.0%
Apr 2026
May 2026
Jun 2026

Third Party: Cloudflare → Oceania → Auckland, New Zealand - (AKL) - Degraded performance

Third Party: Cloudflare → Africa → Abidjan, Ivory Coast - (ABJ) - Operational

Third Party: Cloudflare → Africa → Accra, Ghana - (ACC) - Operational

Third Party: Cloudflare → Asia → Agra, India - (AGR) - Operational

Third Party: Cloudflare → Asia → Ahmedabad, India - (AMD) - Operational

Third Party: Cloudflare → Cloudflare Sites and Services → Workers - Operational

Third Party: Cloudflare → Europe → Amsterdam, Netherlands - (AMS) - Operational

Third Party: Cloudflare → Europe → Athens, Greece - (ATH) - Operational

Third Party: Cloudflare → Latin America & the Caribbean → Americana, Brazil - (QWJ) - Operational

Third Party: Cloudflare → Middle East → Astara, Azerbaijan - (LLK) - Operational

Third Party: Cloudflare → North America → Anchorage, AK, United States - (ANC) - Operational

Third Party: Cloudflare → Middle East → Amman, Jordan - (AMM) - Operational

Third Party: Cloudflare → North America → Albuquerque, NM, United States - (ABQ) - Operational

Third Party: Cloudflare → North America → Ashburn, VA, United States - (IAD) - Operational

Third Party: Cloudflare → Cloudflare Sites and Services → R2 - Operational

Third Party: Cloudflare → Latin America & the Caribbean → Aracatuba, Brazil - (ARU) - Operational

Third Party: Cloudflare → Oceania → Adelaide, SA, Australia - (ADL) - Degraded performance

Notice history

Jun 2026

No notices reported this month

May 2026

API is back up
  • Postmortem
    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.

  • Resolved
    Resolved
    API is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    API is down at the moment. This incident was automatically created by Instatus monitoring.

Apr 2026

Apr 2026 to Jun 2026

Next