Swank Outage History

Swank is up right now

Pingoru has recorded 3 incidents for Swank: 0 in the last 12 months and 0 in the last 90 days.

Source: swankmp.zendesk.com

3incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Swank in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 556 (0%)

Incidents, newest first

Major January 14, 2025 January 14, 2025: Outage with media1 CDN services 2h 22m Service Updates

Started Jan 14, 2025, 04:59 PM UTC· resolved Jan 14, 2025, 07:22 PM UTC

  1. resolved Jan 14, 2025, 07:22 PM UTC

    Date: 1/14/2025 Impact: Cloud Streaming Portal and Cloud API customers are facing 5XX errors accessing thumbnails, trailers, and other assets from the media1-swank-com.azureedge.net and media1.swank.com endpoints for our media asset CDN. Placeholder images display on the Cloud Streaming portals' UI. Content playback is not impacted Root Cause: Azure's migration of media1-swank-com from a deprecated CDN service to a new service created unexpected disruptions of content delivery from that new service. Resolution: Asset delivery via API and Cloud Web UI is restored with changing the media1-swank-com domain to a new secondary CDN service previously established. No changes required on the customer end. Slightly slower loading delays will remain for a few hours while the assets propagate across the CDN. Timeline: [8:00 am]: Customers reporting missing assets and placeholder images from the CDN. [9:30 am]: Service appears to be partially restored, with assets beginning to return as available. [10:30 am]: CDN service returns to unavailable status. Team begins investigating the redirect to a secondary CDN, media2-swank-com [11:30 am]: Team switched media1-swank-com endpoint to a new CDN endpoint to restore asset delivery. New certificates need to propagate over the CDN, as well as assets to the local endpoints. Cloud Streaming portals are displaying all available assets as expected, though with some longer load times that should continue to improve. Lessons Learned: Cloud Streaming Po

Read the full incident report →