All Systems Operational

Website Operational
Portal (cloud.skytap.com) Operational
Corporate Site (skytap.com) Operational
Course Manager Operational
APAC-2 Operational
APAC-2 x86 Compute Operational
APAC-2 Network Operational
APAC-2 Services Operational
APAC-2 Storage Operational
AU-Sydney-M-1 Operational
AU-Sydney-M-1 POWER Compute Operational
AU-Sydney-M-1 x86 Compute Operational
AU-Sydney-M-1 Network Operational
AU-Sydney-M-1 Services Operational
AU-Sydney-M-1 Storage Operational
AU-Sydney-M-2 Operational
AU-Sydney-M-2 Power Compute Operational
AU-Sydney-M-2 x86 Compute Operational
AU-Sydney-M-2 Network Operational
AU-Sydney-M-2 Services Operational
AU-Sydney-M-2 Storage Operational
CA-Toronto-M-1 Operational
CA-Toronto-M-1 POWER Compute Operational
CA-Toronto-M-1 x86 Compute Operational
CA-Toronto-M-1 Network Operational
CA-Toronto-M-1 Services Operational
CA-Toronto-M-1 Storage Operational
CAN-Toronto Operational
CAN-Toronto x86 Compute Operational
CAN-Toronto Network Operational
CAN-Toronto Services Operational
CAN-Toronto Storage Operational
CN-HongKong-M-1 Operational
CN-HongKong-M-1 POWER Compute Operational
CN-HongKong-M-1 x86 Compute Operational
CN-HongKong-M-1 Network Operational
CN-HongKong-M-1 Services Operational
CN-HongKong-M-1 Storage Operational
DE-Frankfurt-I-1 Operational
DE-Frankfurt-I-1 x86 Compute Operational
DE-Frankfurt-I-1 Network Operational
DE-Frankfurt-I-1 Services Operational
DE-Frankfurt-I-1 Storage Operational
EMEA Operational
EMEA x86 Compute Operational
EMEA Network Operational
EMEA Services Operational
EMEA Storage Operational
IE-Dublin-M-1 Operational
IE-Dublin-M-1 POWER Compute Operational
IE-Dublin-M-1 x86 Compute Operational
IE-Dublin-M-1 Network Operational
IE-Dublin-M-1 Services Operational
IE-Dublin-M-1 Storage Operational
IN-Pune-M-1 Operational
IN-Pune-M-1 - POWER Compute Operational
IN-Pune-M-1 x86 Compute Operational
IN-Pune-M-1 Network Operational
IN-Pune-M-1 Services Operational
IN-Pune-M-1 Storage Operational
JP-Tokyo-M-1 Operational
JP-Tokyo-M-1 x86 Compute Operational
JP-Tokyo-M-1 Power Compute Operational
JP-Tokyo-M-1 Services Operational
JP-Tokyo-M-1 Storage Operational
JP-Tokyo-M-1 Network Operational
NL-Amsterdam-M-1 Operational
NL-Amsterdam-M-1 POWER Compute Operational
NL-Amsterdam-M-1 x86 Compute Operational
NL-Amsterdam-M-1 Network Operational
NL-Amsterdam-M-1 Services Operational
NL-Amsterdam-M-1 Storage Operational
SG-Singapore-M-1 Operational
SG-Singapore-M-1 POWER Compute Operational
SG-Singapore-M-1 x86 Compute Operational
SG-Singapore-M-1 Network Operational
SG-Singapore-M-1 Services Operational
SG-Singapore-M-1 Storage Operational
UK-London-M-1 Operational
UK-London-M-1 POWER Compute Operational
UK-London-M-1 x86 Compute Operational
UK-London-M-1 Networking Operational
UK-London-M-1 Services Operational
UK-London-M-1 Storage Operational
UK-London-M-2 Operational
UK-London-M-2 POWER Compute Operational
UK-London-M-2 x86 Compute Operational
UK-London-M-2 Networking Operational
UK-London-M-2 Services Operational
UK-London-M-2 Storage Operational
US-Central Operational
US-Central x86 Compute Operational
US-Central Network Operational
US-Central Services Operational
US-Central Storage Operational
US-East-2 Operational
US-East-2 x86 Compute Operational
US-East-2 Network Operational
US-East-2 Services Operational
US-East-2 Storage Operational
US-Texas-M-1 Operational
US-Texas-M-1 POWER Compute Operational
US-Texas-M-1 x86 Compute Operational
US-Texas-M-1 Networking Operational
US-Texas-M-1 Services Operational
US-Texas-M-1 Storage Operational
US-Virginia-M-1 Operational
US-Virginia-M-1 POWER Compute Operational
US-Virginia-M-1 x86 Compute Operational
US-Virginia-M-1 Network Operational
US-Virginia-M-1 Services Operational
US-Virginia-M-1 Storage Operational
US-Virginia-M-2 Operational
US-Virginia-M-2 POWER Compute Operational
US-Virginia-M-2 x86 Compute Operational
US-Virginia-M-2 Network Operational
US-Virginia-M-2 Services Operational
US-Virginia-M-2 Storage Operational
US-West Operational
US-West x86 Compute Operational
US-West Network Operational
US-West Services Operational
US-West Storage Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Maintenance in APAC-2 Region Feb 14, 2026 16:00-16:45 UTC

Skytap will be performing maintenance in the APAC-2 region on:
February 15, 2026 12:00 AM Singapore time (February 14, 2026 16:00 UTC).

The maintenance duration is expected to be up to 45 minutes.

During this maintenance window:
12:00 AM Singapore time:
- Networking in the region will experience a disruption lasting from 1 to 15 minutes
- SRA connections to VMs in the region will experience disruptions
12:15 AM Singapore time: Additional non-customer impacting maintenance items will take place
12:45 AM Singapore time: Maintenance completed

Important Notes:
- As a point of clarification, Skytap will NOT be shutting down any VMs during this maintenance

If you have any questions about this maintenance, you can open a support request by sending an email to support@skytap.com
Posted on Jan 14, 2026 - 14:28 UTC

Maintenance in US-Texas-M-1 Region Feb 15, 2026 06:00-11:00 UTC

Skytap will be performing maintenance in the US-Texas-M-1 region on:
February 15, 2026 12:00 AM Texas time (February 15, 2026 06:00 UTC).

The maintenance duration is expected to be up to 5 hours, 0 minutes.

During this maintenance window:
12:00 AM Texas time:
- All LPARs in the region will be locked:
----- Locked LPARs are unable to change state (cannot be suspended, resumed, shutdown, powered off or powered on)
----- Environments or templates containing a locked LPAR are unable to be copied
- Public IPs attached to VMs and VPNs will experience disruptions between 1 and 5 minutes long per IP during the duration of the maintenance
- ExpressRoutes will experience a disruption in service lasting between 1 to 15 minutes
- SRA connections to all LPARs in the region will experience disruptions
4:20 AM Texas time: All LPARs in the region will be unlocked; the unlock process may take up to 15 minutes to complete
4:35 AM Texas time: Additional non-customer impacting maintenance items will take place
5:00 AM Texas time: Maintenance completed

Important Notes:
- As a point of clarification, Skytap will NOT be shutting down any LPARs or VMs during this maintenance
- Actions that are scheduled to occur during the maintenance window related to locked VMs or LPARs may fail
- Copy-to-Region operations during the maintenance window related to locked VMs or LPARs may fail

If you have any questions about this maintenance, you can open a support request by sending an email to support@skytap.com
Posted on Jan 14, 2026 - 14:45 UTC
Feb 10, 2026

No incidents reported today.

Feb 9, 2026

No incidents reported.

Feb 8, 2026
Maintenance in US-Virginia-M-2 Region
Completed - The scheduled maintenance has been completed.
Feb 8, 07:39 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 8, 05:00 UTC
Scheduled - Skytap will be performing maintenance in the US-Virginia-M-2 region on:
February 8, 2026 12:00 AM Virginia time (February 8, 2026 05:00 UTC).

The maintenance duration is expected to be up to 4 hours, 15 minutes.

During this maintenance window:
12:00 AM Virginia time:
- All LPARs in the region will be locked:
----- Locked LPARs are unable to change state (cannot be suspended, resumed, shutdown, powered off or powered on)
----- Environments or templates containing a locked LPAR are unable to be copied
- Public IPs attached to VMs and VPNs will experience disruptions between 1 and 5 minutes long per IP during the duration of the maintenance
- ExpressRoutes will experience a disruption in service lasting between 1 to 15 minutes
- SRA connections to all LPARs in the region will experience disruptions
3:45 AM Virginia time: All LPARs in the region will be unlocked; the unlock process may take up to 15 minutes to complete
4:00 AM Virginia time: Additional non-customer impacting maintenance items will take place
4:15 AM Virginia time: Maintenance completed

Important Notes:
- As a point of clarification, Skytap will NOT be shutting down any LPARs or VMs during this maintenance
- Actions that are scheduled to occur during the maintenance window related to locked VMs or LPARs may fail
- Copy-to-Region operations during the maintenance window related to locked VMs or LPARs may fail

If you have any questions about this maintenance, you can open a support request by sending an email to support@skytap.com
Jan 7, 15:12 UTC
Feb 7, 2026
Maintenance in CN-HongKong-M-1 Region
Completed - The scheduled maintenance has been completed.
Feb 7, 17:14 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 7, 16:00 UTC
Scheduled - Skytap will be performing maintenance in the CN-HongKong-M-1 region on:
February 8, 2026 12:00 AM HongKong time (February 7, 2026 16:00 UTC).

The maintenance duration is expected to be up to 2 hours, 40 minutes.

During this maintenance window:
12:00 AM HongKong time:
- All LPARs in the region will be locked:
----- Locked LPARs are unable to change state (cannot be suspended, resumed, shutdown, powered off or powered on)
----- Environments or templates containing a locked LPAR are unable to be copied
- ExpressRoutes will experience a disruption in service lasting between 1 to 15 minutes
- SRA connections to all LPARs in the region will experience disruptions
1:55 AM HongKong time: All LPARs in the region will be unlocked; the unlock process may take up to 15 minutes to complete
2:15 AM HongKong time: Additional non-impacting maintenance items will take place

Important Notes:
- As a point of clarification, Skytap will NOT be shutting down any LPARs or VMs during this maintenance
- Actions that are scheduled to occur during the maintenance window related to locked VMs or LPARs may fail
- Copy-to-Region operations during the maintenance window related to locked VMs or LPARs may fail

If you have any questions about this maintenance, you can open a support request by sending an email to support@skytap.com
Jan 7, 14:58 UTC
Feb 6, 2026

No incidents reported.

Feb 5, 2026

No incidents reported.

Feb 4, 2026

No incidents reported.

Feb 3, 2026

No incidents reported.

Feb 2, 2026

No incidents reported.

Feb 1, 2026
Maintenance in NL-Amsterdam-M-1 Region
Completed - The scheduled maintenance has been completed.
Feb 1, 03:55 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 31, 23:00 UTC
Scheduled - Kyndryl Cloud Uplift will be performing maintenance in the NL-Amsterdam-M-1 region on:
February 1, 2026 12:00 AM Amsterdam time (January 31, 2026 23:00 UTC).

The maintenance duration is expected to be up to 6 hours, 10 minutes.

During this maintenance window:
12:00 AM Amsterdam time:
- All LPARs in the region will be locked:
----- Locked LPARs are unable to change state (cannot be suspended, resumed, shutdown, powered off or powered on)
----- Environments or templates containing a locked LPAR are unable to be copied
- Public IPs attached to VMs and VPNs will experience disruptions between 1 and 5 minutes long per IP during the duration of the maintenance
- ExpressRoutes will experience a disruption in service lasting between 1 to 15 minutes
- SRA connections to all LPARs in the region will experience disruptions
5:40 AM Amsterdam time: All LPARs in the region will be unlocked; the unlock process may take up to 15 minutes to complete
5:55 AM Amsterdam time: Additional non-customer impacting maintenance items will take place
6:10 AM Amsterdam time: Maintenance completed

Important Notes:
- As a point of clarification, Kyndryl Cloud Uplift will NOT be shutting down any LPARs or VMs during this maintenance
- Actions that are scheduled to occur during the maintenance window related to locked VMs or LPARs may fail
- Copy-to-Region operations during the maintenance window related to locked VMs or LPARs may fail

If you have any questions about this maintenance, you can open a support request by sending an email to support@skytap.com
Dec 31, 02:11 UTC
Jan 31, 2026
Jan 30, 2026

No incidents reported.

Jan 29, 2026

No incidents reported.

Jan 28, 2026

No incidents reported.

Jan 27, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage