Checked 1s ago·4/4 regions returned data·every 5 min · HTTP probe·direct probe, not crowd-reported
Per-region results
🇺🇸US EastDOWN
—
ECONNRESET
🇺🇸US WestUP
410 msHTTP 301
🇬🇧EuropeUP
412 msHTTP 301
🇸🇬AsiaDOWN
—
ECONNRESET
HTTP details
HTTP status
301
Response time
410 ms
Region consensus
2/4 reachable
24h success rate
0% (0/1 probes)
Timing breakdown
DNS lookup
105 ms
TCP connect
92 ms
TLS handshake
100 ms
First byte
113 ms
Total
410 ms
Network
Host
telenor.se
Port
443
Transport
HTTPS
What this means
2/4 regions reported issues (US East, Asia).
The outage appears partial — users in healthy regions are unaffected. If you're in an affected region, try a VPN exit in a healthy one.
What to try next
Regional reroute
Affected region? A VPN exit node in a healthy region usually restores access.
Wait and retry
Partial outages often resolve within 10-15 minutes. Reload to re-check.
Report
If you're seeing the issue, you're not alone — others can find this page via search.
FAQ
Why is Telenor down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see Telenor's internal cause — we only confirm reachability from each monitoring region. If all 4 regions failed, it's a confirmed outage on Telenor's side. If only some failed, the impact is regional.
Is Telenor down for everyone or just me?
Look at the per-region grid above. If every region succeeded, the issue is local to your network — flush DNS, switch networks, or disable your VPN. If two or more regions failed, the outage is on Telenor's side.
How often does isitdown.io re-check Telenor?
Every 5 minutes via background HTTP probes from US East, US West, Europe, and Asia. You can also re-run on demand by reloading — the verdict above reflects the latest probe.
Status badge
Embed a live status badge on your site, README, or status page. Updates automatically — same status-aware SVG the rest of isitdown.io uses.
We send a GET request to the target URL from each region and time the full response.
Counts as DOWN
Every region fails the request (connect refused, DNS error, timeout, or HTTP 5xx).
Counts as DEGRADED
At least one region succeeds but at least one fails — the outage is partial or regional.
Detail
Per-region results include HTTP status code, response time, and best-effort DNS / connect / TLS / first-byte phase timings when the Node HTTP client exposes them.
Cadence
Every 5 minutes, in parallel across 4 monitoring regions (US East Virginia, US West Oregon, Europe London, Asia Singapore).
Rate-limited targets
If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status — we do not flood the target to confirm the outage.
Data source
Direct probes from our monitoring infrastructure. We do not aggregate crowd reports, Twitter mentions, or DownDetector signals — every result on this page is a live network request.