Header Image
All Systems Operational

Updated 3 hours ago

Locations

Uplynk Video Streaming

Normal Performance

Fast Purge

Normal Performance

HTTP Large Object CDN

Normal Performance

HTTP Small Object CDN

Normal Performance

Application Delivery Network

Normal Performance

CDN Storage

Normal Performance

Transact - PCI Compliant Network

Normal Performance

API

Normal Performance

CDN Control Center

Normal Performance

Logs & Reports

Normal Performance

Ticketing System

Normal Performance

Route DNS

Normal Performance

Real-Time Stats

Normal Performance

History (Last 2 days)

Incident Status

Possible Service Degradation


Components

API, CDN Control Center, Fast Purge


Locations

Global




February 23, 2017 6:23PM UTC
[Investigating] Engineers have have noticed intermittent timeouts in the MCC portal. Customers may experience slowness or timeouts while navigating within the portal. Engineers are investigating and actively working to mitigate the issue.

February 23, 2017 7:00PM UTC
[Monitoring] Engineers have mitigated intermittent timeouts experienced within the MCC Portal. Customers should experience normal response times while navigating within the portal.

February 24, 2017 5:25AM UTC
[Resolved] Engineers have resolved the timeouts experienced within the MCC Portal. Users should experience normal response times while navigating within the portal.
Purge Delay on Transact NetworkPossible Service Degradation

Incident Status

Possible Service Degradation


Components

Fast Purge


Locations

Global




February 23, 2017 6:19PM UTC
[Investigating] Verizon Engineers are investigating a purge delay on the Transact Network. Customers may experience aged assets being served.

February 23, 2017 7:09PM UTC
[Resolved] Verizon Engineers have confirmed that the purge delay has been resolved. Users should experience no further stale content being served on the Transact network.

Incident Status

Possible Service Degradation


Components

HTTP Large Object CDN, HTTP Small Object CDN


Locations

New York, NY, USA




February 23, 2017 3:51PM UTC
[Investigating] Verizon Engineers are investigating possible service degradation on the HTTP Large and HTTP Small platforms in the New York region. Customers may experience longer asset delivery times and timeouts.

February 23, 2017 4:30PM UTC
[Resolved] Verizon Engineers have resolved the issue and confirmed no further impact to HTTP Large and HTTP Small in the New York region. Users should experience normal asset delivery times with no timeouts.

Incident Status

Possible Service Degradation


Components

HTTP Large Object CDN


Locations

San Jose, CA, USA, Seattle, WA, USA




February 23, 2017 4:19AM UTC
[Investigating] Engineers are currently investigating service degradation affecting the HTTP Large Platform. Users may experience slow asset delivery and timeouts in the Seattle, WA (PAE) and San Jose, CA (RHV) region.

February 23, 2017 8:00AM UTC
[Monitoring] Verizon Digital Media Engineers have mitigated the service degradation affecting the HTTP Large platform in Seattle (SEA) and San Jose (RHV). All services are performing normally.

February 23, 2017 2:00PM UTC
[Resolved] Verizon Digital Media Engineers have resolved the service degradation affecting the HTTP Large platform in Seattle (SEA) and San Jose (RHV). All services are performing normally.
Notice of Possible Propagation DelayPossible Service Degradation

Incident Status

Possible Service Degradation


Components

CDN Control Center


Locations

Global




February 23, 2017 7:25AM UTC
[Investigating] We are currently investigating possible propagation delay affecting changes made on the CDN. Users will see configuration changes take longer than usual.

February 23, 2017 7:32AM UTC
[Monitoring] Verizon Digital Media Engineers have corrected the issue causing the delay and changes requested on the CDN are now propagating normally.

February 23, 2017 1:59PM UTC
[Resolved] The issue with possible propagation delays affecting changes made on the CDN has now been resolved