Blue Canvas Outage History

Blue Canvas is up right now

Blue Canvas had 7 outages in the last 2 years totaling 70h 41m of downtime — averaging 0.3 incidents per month.

There were 7 Blue Canvas outages since October 21, 2025 totaling 70h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.bluecanvas.io

Major September 16, 2026

Salesforce Outage

Detected by Pingoru
Sep 16, 2026, 09:10 AM UTC
Resolved
Sep 16, 2026, 04:17 PM UTC
Duration
7h 6m
Affected: Metadata Sync (Inbound)Metadata Deploy (Outbound)Salesforce APIs
Timeline · 3 updates
  1. identified Sep 16, 2026, 09:10 AM UTC

    Salesforce is experiencing a platform-wide disruption affecting instances across all regions. As a result, some Blue Canvas syncs and deployments are failing or delayed, and some branches may show as disconnected. Follow Salesforce for updates: https://status.salesforce.com/incidents/20004433

  2. monitoring Sep 16, 2026, 11:21 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 16, 2026, 04:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 19, 2026

Sync servers crashing

Detected by Pingoru
Aug 19, 2026, 08:05 AM UTC
Resolved
Aug 20, 2026, 04:41 PM UTC
Duration
1d 8h
Affected: Metadata Sync (Inbound)Metadata Deploy (Outbound)
Timeline · 6 updates
  1. investigating Aug 19, 2026, 08:05 AM UTC

    Syncs and deploys are currently not happening. The underlying servers are crashing for various reasons. We're working on pinpointing the exact issue.

  2. monitoring Aug 19, 2026, 11:19 AM UTC

    We have identified the cause of the intermittent delays affecting branch synchronization and related processing over the past day. A fix has been deployed and the affected processing infrastructure has been replaced. All synchronization services are operating normally and we are monitoring closely to confirm the fix holds under full load. Synchronization jobs that were delayed during this period have resumed automatically — no action is required from customers, and no data was lost.

  3. investigating Aug 19, 2026, 01:06 PM UTC

    Unfortunately the system degraded again after ~1 hour.

  4. monitoring Aug 19, 2026, 01:58 PM UTC

    The "ring" that serves syncs and deploys is stable again. This should get the syncs and deploys running as usual. In the meantime we'll keep an eye out and act immediately if something changes.

  5. monitoring Aug 20, 2026, 09:00 AM UTC

    Earlier today we identified an issue where ~9% of branches experienced extra delay on both syncs and deploys. The fixes from yesterday helped containing the issue so the other 91% of branches could continue as normal. We've resolved this issue by scaling up the units that have to do the work. There are currently no known issues, but we are looking for a sustainable solution, which may involve one or more releases. In technical terms: The scaling and self-repair configuration we've used for the last year is no long viable. We've greatly optimized on CPU, to the point where it is no longer a reliable metric for scaling in or out. We've disabled the scaling, and manually put the system on a configuration that works right now, and continue to fine tune it while we work on a permanent and automated solution.

  6. resolved Aug 20, 2026, 04:41 PM UTC

    Systems are operational, no incidents since last update, we don't expect further downtime while we optimize the data center.

Read the full incident report →

Minor June 11, 2026

Queue Overloaded

Detected by Pingoru
Jun 11, 2026, 03:37 PM UTC
Resolved
Jun 11, 2026, 08:49 PM UTC
Duration
5h 12m
Affected: Metadata Deploy (Outbound)
Timeline · 3 updates
  1. identified Jun 11, 2026, 03:37 PM UTC

    A queue that processes background jobs has become overloaded, and is affecting the creation of deployment requests. We're currently working to resolve this issue.

  2. monitoring Jun 11, 2026, 04:23 PM UTC

    We identified the root cause. One of our queued jobs, scheduled to run every 10 seconds, began taking several minutes to complete. These long-running jobs accumulated and consumed all available worker capacity. We've deployed two fixes: - Concurrency limit, only one instance of this job can run at a time, preventing pile-up. - Rewritten algorithm, the job now resolves in ~1 second instead of minutes. We're continuing to monitor.

  3. resolved Jun 11, 2026, 08:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 9, 2026

All Branches Require Reconnection

Detected by Pingoru
Jun 09, 2026, 09:31 AM UTC
Resolved
Jun 10, 2026, 09:37 AM UTC
Duration
1d
Affected: Metadata Sync (Inbound)
Timeline · 2 updates
  1. monitoring Jun 09, 2026, 09:31 AM UTC

    Due to a recent, Salesforce-mandated security upgrade, all branches need to be reconnected.

  2. resolved Jun 10, 2026, 09:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 22, 2025

Branches not syncing

Detected by Pingoru
Dec 22, 2025, 12:07 PM UTC
Resolved
Dec 22, 2025, 01:06 PM UTC
Duration
59m
Affected: Metadata Sync (Inbound)
Timeline · 2 updates
  1. identified Dec 22, 2025, 12:07 PM UTC

    We have identified the root cause and implemented a fix. However, this fix requires a long-running database migration that is already in progress and running smoothly. Branch syncing is temporarily paused while the migration runs. No data will be lost, but new syncs will not start until the migration completes. We apologize for the disruption and expect normal service to resume shortly. We'll post another update once the migration finishes and syncing is restored.

  2. resolved Dec 22, 2025, 01:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 21, 2025

AWS Outage

Detected by Pingoru
Oct 21, 2025, 03:00 AM UTC
Resolved
Oct 21, 2025, 03:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 21, 2025, 08:15 AM UTC

    Between 20 Oct 2025, 07:11 UTC and 21 Oct 2025, 03:15 UTC, our services experienced degraded performance and partial unavailability due to a widespread AWS infrastructure outage affecting multiple regions. During this period, users may have encountered failed requests, timeouts, or intermittent service disruptions.

Read the full incident report →