Telenor CDN Outage History

Telenor CDN is up right now

Telenor CDN had 2 outages in the last 2 years totaling 189h 24m of downtime — averaging 0.1 incidents per month.

There were 2 Telenor CDN outages since September 16, 2025 totaling 189h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://telenorcdn.statuspage.io

Major October 31, 2025

Internal system-related issue affecting rolling buffer recording

Detected by Pingoru
Oct 31, 2025, 09:30 AM UTC
Resolved
Oct 31, 2025, 02:40 PM UTC
Duration
5h 10m
Affected: Rolling buffer recording
Timeline · 2 updates
  1. identified Oct 31, 2025, 09:30 AM UTC

    An internal system-related issue has affected rolling buffer recordings since 31 October 2025, 00:00 UTC. The system is now resuming recording of older programmes, but some content recorded between 00:00 and the recovery period may be unavailable or lost. We are monitoring the system closely and will update this page when the backlog has been fully processed.

  2. resolved Oct 31, 2025, 02:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 16, 2025

Degraded performance on API

Detected by Pingoru
Sep 16, 2025, 03:56 PM UTC
Resolved
Sep 24, 2025, 08:11 AM UTC
Duration
7d 16h
Affected: API
Timeline · 6 updates
  1. investigating Sep 16, 2025, 03:56 PM UTC

    We are currently having issues with our backend system that affects API functionality like purge etc.

  2. investigating Sep 16, 2025, 08:46 PM UTC

    The API is now closed and under maintenance so that we are able to fix the issue.

  3. investigating Sep 17, 2025, 07:12 AM UTC

    API open again, but purge is currently closed.

  4. investigating Sep 19, 2025, 03:32 PM UTC

    We are still working on a fix for purge.

  5. identified Sep 23, 2025, 04:47 PM UTC

    The issue has been fixed and we opened up for purge for a short period, but had to close the service again due to the queues building up again.

  6. resolved Sep 24, 2025, 08:11 AM UTC

    This incident has been resolved.

Read the full incident report →