Skip2 incident

High Error Rates

Minor Resolved View vendor source →
Started
Feb 16, 2026, 06:05 PM UTC
Resolved
Feb 16, 2026, 06:05 PM UTC
Duration
Detected by Pingoru
Feb 16, 2026, 06:05 PM UTC

Update timeline

  1. resolved Feb 16, 2026, 06:05 PM UTC

    Type: Incident Duration: 3 hours and 3 minutes Affected Components: Content Delivery Network (CDN) Feb 16, 21:08:02 GMT+0 - Resolved - The websocket issue and resulting issues are resolved. Feb 16, 18:05:00 GMT+0 - Investigating - Our systems indicate there are a high number of error responses or failed requests. We are investigating the issue. Feb 16, 19:57:21 GMT+0 - Identified - We identified an issue with websocket connections and are working on a fix. Feb 16, 20:13:36 GMT+0 - Identified - The fix we implemented for the websocket issue has caused several locations to fail partially or entirely. We are rolling the fix back. Feb 16, 20:23:17 GMT+0 - Monitoring - A fix has been implemented.

Looking to track Skip2 downtime and outages?

Pingoru polls Skip2's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Skip2 reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Skip2 alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Skip2 for free

5 free monitors · No credit card required