Brev - Notice history

https://app.brev.io - Operational

100.0% uptime
Sep 2026 · 100.0%Oct · 100.0%Nov · 100.0%
Sep 2026
Oct 2026
Nov 2026

Notice history

View current status

Nov 2026

Degraded performance for Databricks connections
ResolvedDegraded performance1 hour 6 minutes
  • ResolvedUTC

    The incident affecting Databricks, which caused slow or failed loading of workbooks and input tables using Databricks connections, has been resolved. Databricks has confirmed their service is operational, and we have verified that workbooks using Databricks connections are loading normally again. If you are still seeing issues, please contact Sigma Support.

  • MonitoringUTC

    Databricks has reported that the issue affecting their service has been mitigated. We are seeing workbooks and input tables that use Databricks connections recover, and we are continuing to monitor to confirm performance is back to normal. We will post another update once we have confirmed full recovery.

  • IdentifiedUTC

    Databricks has identified the issue and is rolling back a change to restore service. Our team is closely monitoring the situation and will provide updates as more information becomes available.

  • InvestigatingUTC

    We are currently seeing degraded performance and query timeouts for workbooks and input tables that use Databricks connections. Affected content may load slowly or fail to load. This is related to an ongoing incident reported by Databricks. Our team is closely monitoring the situation and will provide updates as more information becomes available.

Oct 2026

Incident with Actions, Issues, API Requests and Pull Requests
ResolvedDegraded performance8 minutes
  • ResolvedUTC

    On October 26, 2026, between 17:52 and 18:49 UTC, some customers experienced slower response times across the Checks API, Issues, Pull Requests, GraphQL, Notifications, and related services. Impact was limited to requests served from one of our datacenter sites. Some GraphQL requests failed, and some notifications were delayed. Among GraphQL requests served from the affected site, the average error rate was 5.68%, with a peak five-minute error rate of 14.32%.

    Unusually large requests for contribution history overwhelmed part of our database infrastructure, causing a backlog. Requests continued reaching the slow component rather than being redirected to healthy systems. Restarting the component restored its performance. The incident was marked mitigated at 18:46 UTC and resolved at 18:57 UTC.

    We are adding limits to these requests, improving alerts to detect overload sooner, and strengthening automatic redirection to healthy systems.

  • UpdateUTC

    We saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.

    We mitigated the issue and all services have recovered.

  • MonitoringUTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  • InvestigatingUTC

    We are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests

Sep 2026

Elevated errors on claude.ai, Claude Code, Claude Cowork and the Claude API
ResolvedPartial outage2 hours 5 minutes
  • ResolvedUTC

    The issue affecting Claude.ai, the Claude desktop and mobile apps, Claude Code, Claude Cowork, and the Claude API has been resolved, and services have been operating normally since recovery. Impact occurred from 07:00 PT / 14:00 UTC to 07:59 PT / 14:59 UTC.

  • UpdateUTC

    All services have been operating normally since 14:59 UTC. We are continuing to monitor.

  • MonitoringUTC

    Most services have recovered as of 14:59 UTC. Signing in, starting new chats, voice conversations, Claude Code and Cowork sessions, purchases and file uploads are working again. Some messages sent between 14:00 and 14:59 UTC may not have been saved. We are monitoring closely and will post another update within 30 minutes.

  • UpdateUTC

    The errors that began at 14:00 UTC were mitigated at 14:36 UTC, and existing conversations are mostly working again. A second issue is preventing many users from signing in (single sign-on and Sign in with Apple are unavailable), starting new chats, voice conversations and Claude Code or Cowork sessions, making purchases, and uploading files. If you're signed in, please don't sign out. We're working on a fix and will post another update within 30 minutes.

  • UpdateUTC

    We have applied a mitigation and error rates have dropped substantially. Some sign-in attempts, account actions and Claude Code and Cowork sessions are still failing. We are continuing to work on a full fix.

  • UpdateUTC

    We are investigating reports of degraded performance affecting claude.ai, platform.claude.com, the Claude API, Claude Code, and Claude Cowork. We will provide an update as soon as possible.

  • UpdateUTC

    We are investigating elevated error rates affecting Claude.ai (including the desktop and mobile apps), Claude Code and Claude Cowork. Some requests to the Claude API are also returning errors. We will provide an update as soon as possible.

  • InvestigatingUTC

    We are investigating elevated error rates affecting Claude.ai (including the desktop and mobile apps), Claude Code and Claude Cowork. Users may see failed requests, errors loading or sending conversations, or be asked to sign in again; retrying may succeed. We will provide an update as soon as possible.

Export Failures Incident
ResolvedPartial outage45 minutes
  • ResolvedUTC

    We've identified the root cause and applied a fix, and we're now monitoring the resolution.

    Scheduled exports should resume as expected, and users on orgs with password authentication should now be able to sign in.

    Our preliminary investigations indicate the following:
    Impacted Cloud Regions: Azure, AWS, GCP
    Incident Start Time: Approximately September 26, 2026, at 11:24 AM UTC

  • UpdateUTC

    We've identified the root cause and applied a fix, and we're now monitoring the resolution.

    Scheduled exports should resume as expected, and users on orgs with password authentication should now be able to sign in.

    Our preliminary investigations indicate the following:
    Impacted Cloud Regions: Azure, AWS, GCP
    Incident Start Time: Approximately September 26, 2026, at 11:24 AM UTC

  • InvestigatingUTC

    We are currently looking into reports that users with password authentication are unable to log in to Sigma, along with failures in scheduled report delivery.

    Both issues appear to stem from a disruption in the email service. We are actively investigating and will share an update as soon as more information is available.

    Our preliminary investigations indicate the following:
    Impacted Cloud Regions & Services: Azure, AWS, GCP
    Incident Start Time: Approximately September 26, 2026, at 11:24 AM UTC

    We will provide updates on this page when we have pertinent status updates.

Incident across several services
ResolvedDegraded performance18 hours 44 minutes
  • ResolvedUTC

    Starting at 07:57 UTC on September 23, GitHub experienced elevated 500 and 404 responses across several application pages. This caused failures when installing GitHub Apps, creating organizations, and making some organization membership changes. Customers also experienced delayed label updates and stale search results in Projects.

    The infrastructure failure was isolated to our Azure Central US region. The API errors were mitigated by 10:58 UTC on September 23. Projects' processing continued to recover while an accumulated backlog was drained, and full service was restored at 04:55 UTC on September 24.

    The incident was caused by a failed planned maintenance operation on a primary database. Automated recovery initiated an emergency database failover, after which several replicas in the affected region were unable to resume replication correctly. This reduced available database capacity and caused the API errors and downstream Projects processing delays.

    We have mitigated the immediate failure mode. We are also improving maintenance safety checks, database failover handling, post-failover replica validation, and downstream processing resilience to reduce the likelihood and impact of similar incidents.

  • MonitoringUTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  • UpdateUTC

    We are continuing to process the backlog of issue label updates for Projects. Label changes may still be delayed. All other services are operating normally.

  • UpdateUTC

    We are continuing to process the backlog of issue label updates for Projects. Users may still see delays before label changes are reflected in Projects. All other services are operating normally.

  • UpdateUTC

    We've deployed a change intended to accelerate processing of the backlog of issue label updates in Projects. A sizable backlog still remains and we continue working through it. All other services are operating normally. We will provide another update within the next hour.

  • UpdateUTC

    Updates to issue labels may be delayed in being reflected in Projects. We are continuing to deploy a change that will accelerate processing of the backlog of label updates. All other services are available. We will provide another update within the next hour.

  • UpdateUTC

    We are preparing to deploy a change that will mitigate the impact.

  • UpdateUTC

    Continuing to investigate the lag that may be experienced in issue labels being accurately reflected in Projects. We are working on alternate solutions to process the backlog of label updates.

  • UpdateUTC

    We will post another update in approximately one hour to share our progress.

  • UpdateUTC

    Updates to issue labels may be delayed in being reflected in Projects by about ~10 minutes. We have added some capacity to work through the backlog more quickly, but it'll likely be a few hours to complete processing the full backlog of messages. All other services are available.

  • UpdateUTC

    Users may experience stale Project search results. We are working to increase indexing speed. All other services are available.

  • UpdateUTC

    We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.

  • UpdateUTC

    The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.

  • UpdateUTC

    Database replicas have been restored. Org creation and the GitHub API are no longer degraded.

  • UpdateUTC

    Database replicas have detached. We're working to restore the database replicas. Users may experience issues beyond creating organizations and a degraded experience with the GitHub API and Projects.

  • InvestigatingUTC

    We are investigating reports of degraded performance for API Requests

Previous

Sep 2026 to Nov 2026

Next