Skip2 had 22 outages in the last 2 years — averaging 0.9 incidents per month.
There were 22 Skip2 outages since May 17, 2025. Each is summarised below — incident details, duration, and resolution information.
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.
Type: Incident Duration: 2 hours and 43 minutes Affected Components: Content Delivery Network (CDN) May 8, 18:45:00 GMT+0 - Investigating - TLS certificates are unable to be provisioned. We are investigating this issue. May 8, 21:28:00 GMT+0 - Resolved - This incident has been resolved.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
Type: Maintenance Duration: 2 hours Affected Components: Dallas, TX, USA (DAL-1) Jul 30, 12:00:00 GMT+0 - Completed - Maintenance has completed successfully Jul 30, 10:00:00 GMT+0 - Identified - A vendor is conducting major system upgrades at this PoP. Traffic will be rerouted while the PoP is taken offline and upgrades conducted. Updates will be posted to status.skip2.net. Jul 30, 10:00:01 GMT+0 - Identified - Maintenance is now in progress
Type: Incident Duration: 21 minutes Affected Components: Content Delivery Network (CDN) Jul 14, 16:30:00 GMT+0 - Resolved - This incident has been resolved. Jul 14, 16:09:07 GMT+0 - Investigating - We are currently investigating this incident. Some users are receiving invalid DNS records. Jul 14, 16:16:55 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 17 hours and 3 minutes Affected Components: Amsterdam, Netherlands (AMS-1) Jul 6, 22:00:45 GMT+0 - Investigating - Our systems indicate an outage has begun. We are investigating. Traffic is rerouted away from the affected PoP. Jul 7, 15:03:24 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 day and 32 minutes Affected Components: Miami, FL, USA (MIA-5) South Jul 2, 16:30:58 GMT+0 - Investigating - We are currently investigating this incident. Jul 2, 15:58:18 GMT+0 - Investigating - Our systems indicate an outage has begun. We are investigating. Traffic is rerouted away from the affected PoP. Jul 3, 16:30:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 5 hours and 13 minutes Affected Components: Hillsboro, OR, USA (HIO-1) Jul 2, 09:13:00 GMT+0 - Investigating - Our systems indicate an outage has begun. We are investigating. Traffic is rerouted away from the affected PoP. Jul 2, 13:50:49 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 2, 14:25:46 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 23 hours and 23 minutes Affected Components: New York City, NY, USA (NYC-4) Jun 29, 16:10:37 GMT+0 - Identified - We have identified that the outage is due to an issue with an upstream vendor. We are engaging our support resources. Traffic remains rerouted. Jun 29, 18:34:24 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 30, 02:08:25 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 30, 15:34:02 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 30 days, 6 hours and 6 minutes Affected Components: Los Angeles, CA, USA (LAX-5) Downtown 2 Jun 30, 21:13:00 GMT+0 - Resolved - This incident has been resolved. Jun 29, 15:13:07 GMT+0 - Identified - This issue is due to a facility air conditioning system failure. The facility has dispatched building engineers to begin repairs. This PoP will remain rerouted until the cooling issue is resolved. Jun 29, 15:06:41 GMT+0 - Investigating - Our systems indicate an outage has begun. We are investigating. Traffic is rerouted away from the affected PoP.
Type: Incident Duration: 5 hours and 6 minutes Affected Components: Newark, NJ, USA (EWR-1) May 17, 18:36:00 GMT+0 - Resolved - This incident has been resolved. May 17, 13:30:00 GMT+0 - Investigating - Our systems indicate an outage has begun. We are investigating. Traffic is rerouted away from the affected PoP. May 17, 18:08:31 GMT+0 - Identified - We are continuing to work on a fix for this incident.