Skytap incident

Storage Degradation in US-Virginia-M-2

Major Resolved View vendor source →

Skytap experienced a major incident on August 12, 2026 affecting US-Virginia-M-2 Storage, lasting 5h 44m. The incident has been resolved; the full update timeline is below.

Started
Aug 12, 2026, 02:57 PM UTC
Resolved
Aug 12, 2026, 08:41 PM UTC
Duration
5h 44m
Detected by Pingoru
Aug 12, 2026, 02:57 PM UTC

Affected components

US-Virginia-M-2 Storage

Update timeline

  1. identified Aug 12, 2026, 02:57 PM UTC

    We have identified a storage issue in our US-Virginia-M-1 Region. Our Engineers are actively working on this issue with high priority. Symptoms for this issue may include: - Inability of some Virtual Machines in this region to change state (ie, run, suspend, shutdown) - Degraded disk read/write performance for some running Virtual Machines in this region - Deploying from templates in this region may fail - Saving templates in this region may fail - Copying environments or templates out of this region may fail - VM Imports and Exports out of this region may fail We will provide an additional update within one hour.

  2. identified Aug 12, 2026, 03:51 PM UTC

    We have identified a storage issue in our US-Virginia-M-2 Region. Our Engineers are continuing work on this issue with the highest priority. Symptoms for this issue may include: - Inability of some Virtual Machines in this region to change state (ie, run, suspend, shutdown) - Degraded disk read/write performance for some running Virtual Machines in this region - Deploying from templates in this region may fail - Saving templates in this region may fail - Copying environments or templates out of this region may fail - VM Imports and Exports out of this region may fail We will provide an additional update within one hour.

  3. identified Aug 12, 2026, 04:51 PM UTC

    We have identified a storage issue in our US-Virginia-M-2 Region. Our Engineers are continuing work on this issue with the highest priority. Symptoms for this issue may include: - Inability of some Virtual Machines in this region to change state (ie, run, suspend, shutdown) - Degraded disk read/write performance for some running Virtual Machines in this region - Deploying from templates in this region may fail - Saving templates in this region may fail - Copying environments or templates out of this region may fail - VM Imports and Exports out of this region may fail We will provide an additional update within one hour.

  4. identified Aug 12, 2026, 06:08 PM UTC

    We have identified a storage issue in our US-Virginia-M-2 Region. Our Engineers are continuing work on this issue with the highest priority. Symptoms for this issue may include: - Inability of some Virtual Machines in this region to change state (ie, run, suspend, shutdown) - Degraded disk read/write performance for some running Virtual Machines in this region - Deploying from templates in this region may fail - Saving templates in this region may fail - Copying environments or templates out of this region may fail - VM Imports and Exports out of this region may fail We will provide an additional update within one hour.

  5. identified Aug 12, 2026, 07:03 PM UTC

    We have identified a storage issue in our US-Virginia-M-2 Region. Our Engineers are continuing work on this issue with the highest priority. Symptoms for this issue may include: - Inability of some Virtual Machines in this region to change state (ie, run, suspend, shutdown) - Degraded disk read/write performance for some running Virtual Machines in this region - Deploying from templates in this region may fail - Saving templates in this region may fail - Copying environments or templates out of this region may fail - VM Imports and Exports out of this region may fail We will provide an additional update within one hour.

  6. identified Aug 12, 2026, 08:11 PM UTC

    We have identified a storage issue in our US-Virginia-M-2 Region. Our Engineers are continuing work on this issue with the highest priority. Symptoms for this issue may include: - Inability of some Virtual Machines in this region to change state (ie, run, suspend, shutdown) - Degraded disk read/write performance for some running Virtual Machines in this region - Deploying from templates in this region may fail - Saving templates in this region may fail - Copying environments or templates out of this region may fail - VM Imports and Exports out of this region may fail We will provide an additional update within one hour.

  7. resolved Aug 12, 2026, 08:41 PM UTC

    The storage issue in our US-Virginia-M-2 Region has now been resolved. The following symptoms should now be alleviated: - Inability of some Virtual Machines in this region to change state (ie, run, suspend, shutdown) - Degraded disk read/write performance for some running Virtual Machines in this region - Deploying from templates in this region may fail - Saving templates in this region may fail - Copying environments or templates out of this region may fail This disruption may have resulted in some running Virtual Machines being disconnected from their storage for a period of time. If you have a VM reporting an error or issue, or if you continue to experience any of the symptoms mentioned above, please contact Kyndryl Cloud Uplift Support ([email protected]) for immediate assistance.