1) Quick answer

The most likely explanation is:

1. Your device connects to the plane's Wi‑Fi access point.
2. The airline network places you behind a captive portal / policy gateway.
3. That gateway allows some categories of traffic, such as messaging apps, while blocking general web browsing.
4. Telegram works because its traffic is recognized and permitted.
5. Safari fails because ordinary web requests are in the blocked category.

2) The main communication flow

The decision about what you can access is usually made before traffic becomes just “normal internet.” The gateway or policy system inspects or classifies your request and decides whether it is allowed.

3) What DNS is doing here

If DNS is unfamiliar, think of it like the internet's contact lookup system.

DNS flow

Airline networks can control DNS in several ways:

• force your device to use the airline's DNS servers
• return special answers for blocked domains
• redirect some requests to the captive portal
• allow resolution but still block the actual traffic later

4) What routing is doing here

Routing is the process of moving packets from one network hop to the next until they reach their destination.

Simple routing picture

In normal home internet, your traffic is usually just routed onward. On airline Wi‑Fi, the network is often much more opinionated:

• allow this traffic category
• drop that traffic category
• redirect web requests to a payment/auth page
• rate-limit large or expensive traffic

5) Why Telegram works

There are a few likely mechanisms, and more than one can be true at the same time.

Mechanism	What it means	How it helps Telegram work
Allowlist by domain/IP	The airline permits known Telegram endpoints.	Traffic to Telegram servers passes; other sites do not.
App-category policy	The network classifies traffic as messaging vs general browsing.	Messaging flows are allowed under a lower-cost plan.
Captive portal exception rules	Some apps bypass the normal web-login wall.	Telegram can keep sending/receiving while Safari is redirected or blocked.
Lower bandwidth tolerance	Messaging traffic is small and predictable.	Airlines are more willing to allow lightweight traffic.

6) Why Safari may fail

Safari is usually your most obvious “general internet” test, so it is often where the restriction becomes visible.

Possible visible outcomes:

• site never loads
• you get redirected to airline purchase page
• DNS appears flaky
• some sites hang at “connecting”
• HTTPS errors or endless retry behavior

7) Why a GitHub Pages link might work in Telegram but not in Safari

This is especially interesting, and there are several plausible explanations.

Explanation A: Telegram's in-app browser is treated differently

Links tapped inside Telegram may open in an in-app browser/webview rather than full Safari. The airline network or OS path may treat this differently, especially if Telegram already has an approved session path.

Explanation B: Telegram prefetches or previews link metadata

Telegram often fetches preview information for URLs. In some cases, enough of the content or route is already available that opening the link feels different from a fresh request in Safari.

Explanation C: partial allowlisting + static content luck

GitHub Pages is static hosting. It may pass through some policy edge cases more easily than arbitrary browsing, especially if only certain domains/CDN paths are blocked aggressively.

Explanation D: Safari is more tightly tied to captive-portal behavior

The OS may strongly associate Safari with the normal browsing path and captive-portal enforcement, while an in-app webview may slip through a slightly different route.

8) Does this have to do with different satellites?

Probably not in the way it feels from the user side.

Usually the main split is not:

• message traffic goes over one satellite
• Safari traffic goes over another satellite

More likely, it is:

• all traffic goes into the airline/provider network
• the network applies policy before or during forwarding
• only approved traffic is allowed onto the expensive shared backhaul path

Could satellites still matter indirectly?

Yes, indirectly:

• satellite bandwidth is limited and expensive
• latency is high compared with ground internet
• there may be provider-specific optimizations for light traffic
• the network operator may design messaging-only plans specifically because of those constraints

So the satellite affects the economics and policy, but the app difference is usually caused by network control policy, not by “Telegram has a different satellite.”

9) The likely policy diagram

10) A beginner's glossary

Term	Plain English meaning
DNS	The system that translates names like github.com into IP addresses.
IP address	The numeric network address a device or service uses.
Routing	The process of forwarding packets toward their destination.
Gateway	The network control point your traffic passes through on its way out.
Captive portal	The login/payment gate on public Wi‑Fi that intercepts web access.
Allowlist	A list of approved destinations or traffic types that are permitted.
Backhaul	The upstream connection from the plane to the wider internet, often via satellite or air-to-ground link.

11) Best current hypothesis for your exact experience

1. The plane Wi‑Fi allows messaging-class traffic.
2. Telegram is recognized and allowed.
3. Safari is treated as general web browsing and blocked.
4. Some links opened from inside Telegram may succeed because of in-app browser behavior, preview/prefetch behavior, or differences in policy handling.
5. The root cause is network policy, not a special “Telegram satellite.”

12) Follow-up report ideas

• DNS for humans: a beginner-friendly visual guide to DNS, IPs, ports, and TLS
• Routing for humans: how packets move across networks
• VPNs vs airline Wi‑Fi policy: comparing two gateway/policy systems
• In-app browser vs Safari: how webviews differ from full browsers in practice

Created in response to in-flight testing and discussion about Telegram, Safari, GitHub Pages, Cisco Secure Client, gateways, DNS, routing, and network policy enforcement.