Skip2 experienced a minor incident on May 1, 2025, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved May 01, 2025, 10:39 PM UTC
Type: Incident Duration: 3 hours and 39 minutes Affected Components: Chicago, IL, USA (CHI-5) West Side, Las Vegas, NV, USA (LAS-2), Durham, NC, USA (DUR-1), Charlotte, NC, USA (CLT-1), Telemetry Loop, Web Application Firewall (WAF), Frankfurt, Germany (FRA-4), Los Angeles, CA, USA (LAX-5) Downtown 2, Ashburn, VA, USA (IAD-1), Dallas, TX, USA (DAL-1), Anycast, Tokyo, Japan (TYO-1), Static Storage, Istanbul, Turkey (IST-1), Image Proxy, Osasco, Sao Paulo, Brazil (OSA-1), Amsterdam, Netherlands (AMS-1), Riga, Latvia (RIX-1), New York City, NY, USA (NYC-4), Seattle, WA, USA (SEA-5) , Palo Alto, CA, USA (PAO-1), Miami, FL, USA (MIA-5) South, Denver, CO, USA (DEN-1), Los Angeles, CA, USA (LAX-1) Downtown 1, Miami, FL, USA (MIA-1) North, Hillsboro, OR, USA (HIO-1), Newark, NJ, USA (EWR-1), Chicago, IL, USA (CHI-1) South Side, Domain Name System (DNS), Configuration Plane, Strasbourg, France (SXB-2), Atlanta, GA, USA (ATL-1), Content Delivery Network (CDN) May 2, 02:17:56 GMT+0 - Resolved - This incident has been resolved. May 1, 22:47:36 GMT+0 - Investigating - We are implementing a fix and will monitor the result. May 1, 22:39:06 GMT+0 - Investigating - We are currently investigating this incident. May 2, 00:51:43 GMT+0 - Monitoring - We're continuing to work on finding the root cause of the issue. May 1, 22:55:29 GMT+0 - Monitoring - The fix seems to be working to reduce errors. We are continuing to monitor this issue. May 1, 23:03:45 GMT+0 - Monitoring - Most websites have recovered. We are continuing to monitor the progress of this fix.