BCGov Outage History

Started Oct 18, 2026, 01:00 PM UTC· resolved Oct 22, 2026, 06:53 PM UTC

1. scheduled Oct 18, 2026, 01:00 PM UTC

2. resolved Oct 22, 2026, 06:53 PM UTC

   Work is complete.

Read the full incident report →

Started Oct 18, 2026, 01:00 PM UTC· resolved Oct 22, 2026, 06:55 PM UTC

1. scheduled Oct 18, 2026, 01:00 PM UTC

   This will upgrade the Emerald NSX cluster to OpenShift 4.20 Pre-upgrade work - Starting at 6am on Sunday, October 18th and finishing before 9am Upgrade - Starting at 9am on Monday, October 19th and finishing before 5pm on Friday the 23rd During the Sunday change, the Image Registry will be read-only for up to 15 minutes. On Monday morning the API and web console will be updated and may be briefly disrupted. This maintenance will involve draining and rebooting nodes to update the Openshift version as well as the firmware. It will be disruptive, so please monitor your applications. No action required other than the usual monitoring of your applications. The new web console combines the Admin and Developer perspectives and updates the UI styling.

2. resolved Oct 22, 2026, 06:55 PM UTC

   This work is complete.

Read the full incident report →

Started Sep 27, 2026, 01:00 PM UTC· resolved Oct 22, 2026, 01:16 AM UTC

1. scheduled Sep 27, 2026, 01:00 PM UTC

2. investigating Sep 28, 2026, 03:19 PM UTC

   Active work on OpenShift upgrades begins today, starting with the backplane (master/infra) nodes, then following up with worker nodes.

3. investigating Oct 08, 2026, 06:44 PM UTC

   The maintenance work on SILVER is now finished.

4. resolved Oct 22, 2026, 06:54 PM UTC

   Work is complete

Read the full incident report →

Started Sep 16, 2026, 12:01 AM UTC· resolved Sep 16, 2026, 12:01 AM UTC

1. resolved Sep 16, 2026, 12:01 AM UTC

   An unexpected hardware event caused one of the OpenShift GOLD worker nodes to reboot itself. It has been addressed by cordoning and draining the affected node while vendor support investigates further.

Read the full incident report →

Started Aug 31, 2026, 01:00 PM UTC· resolved Nov 05, 2026, 02:01 AM UTC

1. investigating Aug 31, 2026, 12:21 PM UTC

   This work was successfully completed.

2. scheduled Aug 31, 2026, 01:00 PM UTC

   We will update some software, firmware, and cluster settings and perform a rolling restart of all nodes in the cluster. We will apply the latest firmware on the physical servers. We will upgrade Trident to v26.06.0 and enable concurrency. This has shown great speed improvements to PVC mount/unmount operations in the LABs. Switch the container runtime from runc to crun , as it is the default for OpenShift now. When? Aug 31st to Sept 4th Trident will be upgraded at 6am on the first day of the change. At 9am on the first day of the change we will begin restarting the master nodes first, then the infra nodes, and start on the worker nodes last. Node reboots will continue until 5pm each day, and resume at 9am the next day. Silver will pause over the weekend. Will there be an impact on the Platform apps? As nodes are rebooted pods will be rescheduled to another node. We expect the past issues with Trident taking a long time to start up pods will be solved, but will continue to use slow manual node drains and monitoring of Trident health. Do I need to do anything? Monitor your apps health.

Read the full incident report →

Started Aug 18, 2026, 05:33 AM UTC· resolved Aug 18, 2026, 05:33 AM UTC

1. resolved Aug 18, 2026, 05:33 AM UTC

   This worker node rebooted itself due to hardware issues. The reboot event caused the node to enter a NotReady state which forced the cluster to evict the existing pods to other nodes. A manual cordon and drain afterward has ensured this node remains empty of workloads while we work with vendor support to troubleshoot the hardware.

Read the full incident report →

Started Jul 26, 2026, 01:00 PM UTC· resolved Jul 26, 2026, 01:38 PM UTC

1. resolved Jul 26, 2026, 01:38 PM UTC

   Completed

Read the full incident report →

Started Jul 22, 2026, 01:00 AM UTC· resolved Jul 22, 2026, 02:00 AM UTC

1. resolved Jul 22, 2026, 02:00 AM UTC

   Completed

Read the full incident report →

Started Jul 08, 2026, 12:01 AM UTC· resolved Jul 08, 2026, 12:23 AM UTC

1. resolved Jul 08, 2026, 12:23 AM UTC

   Resolved

Read the full incident report →

Started Jun 15, 2026, 04:00 PM UTC· resolved Jun 19, 2026, 10:33 PM UTC

1. resolved Jun 19, 2026, 10:33 PM UTC

   Complete

Read the full incident report →

Started Jun 14, 2026, 01:41 PM UTC· resolved Jun 14, 2026, 01:41 PM UTC

1. resolved Jun 14, 2026, 01:41 PM UTC

   Completed

Read the full incident report →

Started Jun 08, 2026, 04:00 PM UTC· resolved Jun 14, 2026, 01:19 PM UTC

1. resolved Jun 14, 2026, 01:19 PM UTC

   Completed

Read the full incident report →

Started Jun 03, 2026, 04:04 PM UTC· resolved Jun 03, 2026, 04:38 PM UTC

1. resolved Jun 03, 2026, 04:38 PM UTC

   Resolved

Read the full incident report →

Started Jun 01, 2026, 03:30 PM UTC· resolved Jun 03, 2026, 04:41 PM UTC

1. resolved Jun 03, 2026, 04:41 PM UTC

   Completed

Read the full incident report →

Started May 31, 2026, 12:00 PM UTC· resolved May 31, 2026, 03:29 PM UTC

1. resolved May 31, 2026, 03:29 PM UTC

   Completed

Read the full incident report →

Started May 27, 2026, 11:00 AM UTC· resolved May 31, 2026, 11:54 AM UTC

1. resolved May 31, 2026, 11:54 AM UTC

   Completed

Read the full incident report →

Started May 25, 2026, 12:00 PM UTC· resolved May 29, 2026, 08:59 PM UTC

1. resolved May 29, 2026, 08:59 PM UTC

   Upgrade completed

Read the full incident report →

Started May 20, 2026, 11:00 AM UTC· resolved May 20, 2026, 03:35 PM UTC

1. resolved May 20, 2026, 03:35 PM UTC

   Completed

Read the full incident report →

Started May 13, 2026, 01:00 AM UTC· resolved May 14, 2026, 06:12 PM UTC

1. resolved May 14, 2026, 06:12 PM UTC

   Completed

Read the full incident report →

Started May 03, 2026, 11:00 AM UTC· resolved May 06, 2026, 09:19 PM UTC

1. resolved May 06, 2026, 09:19 PM UTC

   Completed

Read the full incident report →

Started Apr 21, 2026, 04:00 PM UTC· resolved Apr 21, 2026, 07:24 PM UTC

1. resolved Apr 21, 2026, 07:24 PM UTC

   Node is back in service

Read the full incident report →

Started Apr 20, 2026, 04:00 PM UTC· resolved Apr 29, 2026, 09:52 PM UTC

1. resolved Apr 29, 2026, 09:52 PM UTC

   The migration to OVN is now complete. Previously reported connectivity issues between pods have all been resolved.

Read the full incident report →

Started Apr 19, 2026, 11:00 AM UTC· resolved Apr 19, 2026, 11:58 AM UTC

1. resolved Apr 19, 2026, 11:58 AM UTC

   Change has been completed and the Calgary clusters are back online.

Read the full incident report →

Started Apr 13, 2026, 04:00 PM UTC· resolved May 06, 2026, 09:19 PM UTC

1. resolved May 06, 2026, 09:19 PM UTC

   Completed

Read the full incident report →

Started Apr 07, 2026, 04:00 PM UTC· resolved Apr 07, 2026, 10:35 PM UTC

1. resolved Apr 07, 2026, 10:35 PM UTC

   Migration to OVN completed successfully.

Read the full incident report →