Skip2 Outage History

Skip2 is up right now

Skip2 had 15 outages in the last 2 years totaling 3h 13m of downtime — averaging 0.6 incidents per month.

There were 15 Skip2 outages since August 4, 2025 totaling 3h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.skip2.net

Major July 30, 2026

DNS Errors

Detected by Pingoru
Jul 30, 2026, 02:04 AM UTC
Resolved
Jul 30, 2026, 05:17 AM UTC
Duration
3h 13m
Affected: Content Delivery Network (CDN)Domain Name System (DNS)Web Application Firewall (WAF)Static Storage
Timeline · 4 updates
  1. investigating Jul 30, 2026, 02:04 AM UTC

    Our systems indicate a high rate of DNS errors are occurring. We are investigating the issue. Updates will be posted to this page.

  2. identified Jul 30, 2026, 03:33 AM UTC

    A portion of our DNS zones have been deactivated in error. We are working on restoring the zones.

  3. monitoring Jul 30, 2026, 04:01 AM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Jul 30, 2026, 05:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 27, 2026

SSL/TLS Certificate Issue

Detected by Pingoru
Jul 27, 2026, 11:18 PM UTC
Resolved
Jul 27, 2026, 11:18 PM UTC
Duration
Timeline · 1 update
  1. resolved Jul 27, 2026, 11:18 PM UTC

    Type: Incident Duration: 5 hours and 35 minutes Affected Components: Content Delivery Network (CDN) Jul 28, 04:53:09 GMT+0 - Resolved - This incident has been resolved. Jul 27, 23:18:00 GMT+0 - Investigating - Incorrect/expired SSL/TLS certificates are being served for a subset of sites. We are investigating.

Read the full incident report →

Minor May 17, 2026

High Error Rates

Detected by Pingoru
May 17, 2026, 11:18 AM UTC
Resolved
May 17, 2026, 11:18 AM UTC
Duration
Timeline · 1 update
  1. resolved May 17, 2026, 11:18 AM UTC

    Type: Incident Duration: 1 day and 15 hours Affected Components: Content Delivery Network (CDN) May 17, 11:18:00 GMT+0 - Identified - Our systems indicate there are a high number of error responses or failed requests. We are investigating the issue. May 19, 02:18:00 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Major April 2, 2026

Major CDN Outage

Detected by Pingoru
Apr 02, 2026, 06:40 AM UTC
Resolved
Apr 02, 2026, 06:40 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 02, 2026, 06:40 AM UTC

    Type: Incident Duration: 5 hours and 18 minutes Affected Components: Content Delivery Network (CDN) Apr 2, 06:40:00 GMT+0 - Investigating - Our systems indicate that we are failing to respond to HTTP requests. We are investigating this urgently. Updates will be posted here. Apr 2, 11:57:44 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Major February 18, 2026

Partial CDN Outage

Detected by Pingoru
Feb 18, 2026, 02:24 PM UTC
Resolved
Feb 18, 2026, 02:24 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 18, 2026, 02:24 PM UTC

    Type: Incident Duration: 36 minutes Affected Components: Content Delivery Network (CDN), Las Vegas, NV, USA (LAS-2), New York City, NY, USA (NYC-4) Feb 18, 15:00:11 GMT+0 - Resolved - This incident has been resolved. Feb 18, 14:24:39 GMT+0 - Investigating - Our systems indicate that we are failing to respond to HTTP requests for a subset of regions. We are investigating this urgently. Updates will be posted here. Feb 18, 14:28:33 GMT+0 - Identified - This issue affects users in North America. We are continuing to work on a fix for this incident. Feb 18, 14:44:45 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.

Read the full incident report →

Minor February 12, 2026

Rolling Upgrades

Detected by Pingoru
Feb 12, 2026, 03:30 AM UTC
Resolved
Feb 12, 2026, 03:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Feb 12, 2026, 03:30 AM UTC

    Type: Maintenance Duration: 2 hours Affected Components: Content Delivery Network (CDN) Feb 12, 03:30:00 GMT+0 - Identified - We are performing a rolling upgrade of a portion of edge servers in our network. To minimize downtime, traffic will be rerouted away from each server during the upgrade. No downtime is expected. Feb 12, 03:30:01 GMT+0 - Identified - Maintenance is now in progress Feb 12, 05:30:00 GMT+0 - Completed - Maintenance has completed successfully

Read the full incident report →

Minor January 22, 2026

Frankfurt (FRA-4) is rerouted

Detected by Pingoru
Jan 22, 2026, 04:30 PM UTC
Resolved
Jan 22, 2026, 04:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Jan 22, 2026, 04:30 PM UTC

    Type: Incident Duration: 2 hours and 24 minutes Affected Components: Frankfurt, Germany (FRA-4) Jan 22, 16:30:00 GMT+0 - Investigating - Our systems indicate an outage has begun. We are investigating. Traffic is rerouted away from the affected PoP. Jan 22, 18:53:57 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor January 22, 2026

Strasbourg (SXB-2) is rerouted

Detected by Pingoru
Jan 22, 2026, 09:30 AM UTC
Resolved
Jan 22, 2026, 09:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Jan 22, 2026, 09:30 AM UTC

    Type: Incident Duration: 9 hours and 21 minutes Affected Components: Strasbourg, France (SXB-2) Jan 22, 09:30:00 GMT+0 - Investigating - Our systems indicate an outage has begun. We are investigating. Traffic is rerouted away from the affected PoP. Jan 22, 18:51:00 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor November 14, 2025

DNS Migration

Detected by Pingoru
Nov 14, 2025, 07:00 PM UTC
Resolved
Nov 14, 2025, 07:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Nov 14, 2025, 07:00 PM UTC

    Type: Maintenance Duration: 1 hour and 30 minutes Affected Components: Domain Name System (DNS), Content Delivery Network (CDN) Nov 14, 19:00:00 GMT+0 - Identified - We are migrating our DNS servers. Updates will be posted here. Nov 14, 19:00:00 GMT+0 - Identified - Maintenance is now in progress. Nov 14, 19:51:36 GMT+0 - Identified - We are confirming that the migration is complete. Nov 14, 20:30:00 GMT+0 - Completed - Maintenance has completed successfully.

Read the full incident report →

Minor November 3, 2025

Anycast Network Degraded

Detected by Pingoru
Nov 03, 2025, 04:33 PM UTC
Resolved
Nov 03, 2025, 04:33 PM UTC
Duration
Timeline · 1 update
  1. resolved Nov 03, 2025, 04:33 PM UTC

    Type: Incident Duration: 40 minutes Affected Components: Anycast Nov 3, 17:12:59 GMT+0 - Resolved - This incident has been resolved. Nov 3, 16:33:00 GMT+0 - Investigating - Our systems indicate that responses from our anycast IP addresses are slow or resulting in errors. We are investigating. Nov 3, 16:36:36 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.

Read the full incident report →

Minor October 16, 2025

Tokyo, Japan (TYO-1) is rerouted

Detected by Pingoru
Oct 16, 2025, 11:06 PM UTC
Resolved
Oct 16, 2025, 11:06 PM UTC
Duration
Timeline · 1 update
  1. resolved Oct 16, 2025, 11:06 PM UTC

    Type: Incident Duration: 56 minutes Affected Components: Tokyo, Japan (TYO-1) Oct 16, 23:06:25 GMT+0 - Investigating - Our systems indicate an outage has begun. We are investigating. Traffic is rerouted away from the affected PoP. Oct 17, 00:02:06 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor October 13, 2025

Configuration Plane Performance Issues

Detected by Pingoru
Oct 13, 2025, 01:30 PM UTC
Resolved
Oct 13, 2025, 01:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Oct 13, 2025, 01:30 PM UTC

    Type: Incident Duration: 1 hour and 36 minutes Affected Components: Configuration Plane Oct 13, 13:30:52 GMT+0 - Investigating - Our systems indicate that there is a synchronization issue across the configuration plane for our edge services. We are investigating. Oct 13, 14:45:40 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 13, 15:07:13 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor October 4, 2025

Los Angeles (LAX-5) is rerouted

Detected by Pingoru
Oct 04, 2025, 12:30 AM UTC
Resolved
Oct 04, 2025, 12:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Oct 04, 2025, 12:30 AM UTC

    Type: Incident Duration: 1 hour and 18 minutes Affected Components: Los Angeles, CA, USA (LAX-5) Downtown 2 Oct 4, 00:30:25 GMT+0 - Investigating - Our systems indicate an outage has begun. We are investigating. Traffic is rerouted away from the affected PoP. Oct 4, 01:48:00 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor September 8, 2025

Configuration Plane Disabled

Detected by Pingoru
Sep 08, 2025, 03:25 PM UTC
Resolved
Sep 08, 2025, 03:25 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 08, 2025, 03:25 PM UTC

    Type: Incident Duration: 3 hours and 7 minutes Affected Components: Configuration Plane Sep 8, 15:25:50 GMT+0 - Investigating - Due to an issue with our configuration plane infrastructure, all changes are paused. Sep 8, 16:37:20 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 8, 17:31:05 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 8, 18:25:03 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 8, 18:32:29 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor September 1, 2025

New York City (NYC-4), Las Vegas (LAS-2), Miami (MIA-5) and Bern (BRN-1) are rerouted

Detected by Pingoru
Sep 01, 2025, 02:30 PM UTC
Resolved
Sep 01, 2025, 02:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 01, 2025, 02:30 PM UTC

    Type: Incident Duration: 1 hour and 36 minutes Affected Components: Las Vegas, NV, USA (LAS-2), Miami, FL, USA (MIA-5) South, New York City, NY, USA (NYC-4) Sep 1, 14:30:00 GMT+0 - Identified - Our systems indicate that several locations are offline. We are rerouting traffic away from the affected PoPs. Sep 1, 15:09:31 GMT+0 - Monitoring - We've observed a return to normal connectivity. Traffic remains rerouted. Sep 1, 16:06:22 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →