We Tracked Telegram Access Issues Across Nepal: Which ISPs Were Most Affected After India's Telegram Restrictions?

Recent access disruptions reported in Nepal showed a cross-border routing dependency issue affecting Telegram traffic, where many users experienced partial or complete failure depending on their ISP.

Instead of a simple “app outage,” the real pattern points to this:

If upstream international routing or filtering changes occur in a major transit region (like India), Nepali ISPs that rely on those routes can inherit the disruption.

This is why the issue looked like a “ban” to users - even when it was actually a network propagation problem across upstream providers.

What Users Saw vs What Was Happening

Common Belief	What Actually Happened in Nepal Network Layer
Telegram was banned in Nepal	No unified national ban signal observed
App stopped globally	Only specific routes to Telegram were affected
All ISPs blocked it intentionally	Some ISPs inherited upstream routing restrictions
VPN proves government ban	VPN only bypasses routing path issues

Key Technical Reality Observed

• Some ISPs completely lost Telegram connectivity

• Others had partial access (text worked, media failed)

• Mobile networks behaved differently from fiber in many cases

• DNS alone was not the only failure point - routing path degradation was stronger signal

What user said to us ?! about this issued.

“My friend in another ISP had Telegram working normally, but mine was completely stuck. I thought my phone was broken.”

“It worked on mobile data but not on WiFi at home. That made me think only my ISP was blocking it.”

“Channels loaded, but messages wouldn’t send. It felt inconsistent, not like a full shutdown.”

“Everyone started saying it’s banned, but it clearly wasn’t the same for all networks.”

This inconsistency is the key indicator that this was not a uniform national-level restriction event.

What Actually Broke

Telegram traffic relies on international routing paths that go through upstream transit networks.

What likely happened:

1. Upstream Route Change or Filtering

• A major transit region (commonly India-based routing paths) adjusted traffic rules or experienced filtering

• Telegram traffic became unstable or partially blocked on that route

2. Dependency Effect on Nepal ISPs

• Many Nepali ISPs rely on shared upstream providers

• If upstream path degrades → downstream ISP inherits issue automatically

3. Selective Service Breakdown

• Text packets may still pass

• Media/CDN requests fail first

• Full connection appears unstable

ISP Dependency Map

Think of Nepal internet like this:

Nepal ISPs → India/Regional Transit → Global Internet → Telegram Servers

So when:

• Transit layer changes → multiple ISPs affected at once

• Not because they “individually blocked Telegram”

• But because they rely on the same upstream path

Actionable Diagnostic Logic

Step 1: Check Cross-ISP Difference

If Telegram works on:

• Mobile data but not WiFi → ISP routing issue

• One WiFi works, another fails → upstream dependency issue

Step 2: Identify Partial Failure Pattern

• Text works → routing partially OK

• Media fails → CDN path disrupted

• App won’t connect → DNS or route break

Step 3: Confirm Not Device Issue

If multiple devices on same ISP fail → network-level problem confirmed

Final Insight

This event was not a clean “ban inside Nepal.”

It was closer to:

A regional routing or transit-layer disruption that cascaded into Nepal ISPs due to upstream dependency on shared international paths.

That’s why:

• Some users experienced full failure

• Some had partial access

• Some saw no issue at all