---
title: "Telegram: what it connects to on a Mac, which ports it uses, and whether to block it · Kilobat"
url: "https://kilobat.app/processes/telegram"
description: "Telegram documents TCP, WebSocket and HTTP transports on ports 80, 443 and 5222, plus regional data centres. What breaks if you block it on a Mac."
---

# What is Telegram?

Telegram is a messaging app. On a Mac, it keeps connections open to Telegram's data centres. Telegram documents the transports, ports and data centres for developers.

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

I want to know what Telegram is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/telegram.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Process: `Telegram` · Made by Telegram · Applies to: The Telegram app for macOS 10.13 and later. Checked on 8 November 2026 against Telegram's protocol documentation and an installed copy of the app. · Checked: 8 November 2026

## Short answer

The Telegram desktop app. Telegram documents TCP connections on ports 80, 443 and 5222 to regional data centres, plus separate connections for media.

Block with care

Blocking Telegram's ports stops messages, but the app may retry on other ports. Block it only on a network where you do not use it.

Path

`/Applications/Telegram.app/Contents/MacOS/Telegram`

Signing identifier

`ru.keepcoder.Telegram`

## What it is

Telegram's protocol documentation says that its servers sit in several data centres around the world. Each client uses the one nearest to it for its main requests.

The client gets the list of access points with a call named `help.getConfig`. Telegram says that the IP address and port of each access point can change often.

Telegram's transport page lists the ways that a client can connect. They are plain TCP, WebSocket, WebSocket over HTTPS, HTTP and HTTPS.

Plain TCP uses ports 80, 443 and 5222, or another port that the server names. If a server sets the `this_port_only` flag, the client must use only that port.

WebSocket over HTTPS and plain HTTPS use port 443. Telegram recommends WebSocket instead of plain HTTP for browser clients.

Telegram's documentation also describes media-only data centres, and encrypted CDN nodes for media from public channels with more than 100,000 members.

On this Mac, the app is `Telegram.app` with the bundle ID `ru.keepcoder.Telegram`.

## Why it uses the network

- **Messages and updates.** The main connection goes to your home data centre. Telegram says that each session belongs to the app and to your account, not to one connection.
- **Files, photos and video.** Telegram says that large file transfers should use separate sessions and connections to media-only data centres. They carry no updates.
- **Public channel media.** Telegram says that encrypted CDN nodes cache media from public channels with more than 100,000 members.
- **Moving between data centres.** Telegram says that a file is available only from the data centre that holds it. The client opens a new encrypted connection to that centre to download it.

## How much is normal

Telegram does not publish figures for idle traffic. You should expect small, steady traffic from the open connection when nobody writes.

Telegram says that the client may open several connections to a data centre. The count of parallel main sessions is set by the server.

Traffic grows with what you read. Opening a busy channel loads media from media data centres or from CDN nodes.

## When it uses a lot, and why

- **Large files.** Telegram's documentation mentions files up to 4 GB. Uploading or downloading them uses parallel media connections.
- **Busy public channels.** Media from large public channels loads from CDN nodes, which may be in a different region from your home data centre.
- **Blocked ports.** Telegram lists several ports and transports, and the server can name another port. Blocking one may not stop the app.

## Is it safe to block?

Block with care

Blocking Telegram's ports stops messages, but the app may retry on other ports. Block it only on a network where you do not use it.

What breaks if you block it

- Messages and updates stop when the main connection to your data centre is blocked.
- Photos, video and files fail to load when media data centres are blocked.
- Sign-in fails when the client cannot reach any data centre.

Blocking means a firewall rule that refuses its connections. Don’t quit or disable a macOS process to save data: macOS starts it again, and other features depend on it.

## Reduce its use

1. Leave channels that you do not read. Large public channels load media from CDN nodes.
2. Avoid downloading large files that you do not need. Telegram's documentation mentions files up to 4 GB.
3. Quit Telegram when you are not using it, if you do not need notifications.

## See how much it uses

1. Open Activity Monitor and search for Telegram. Open the Network tab to see the bytes that the app moved.

## With Kilobat

1. In the Kilobat app list, search for `Telegram`.
2. Ask the same question in Terminal.

   ```
   kilobat explain Telegram
   ```

The live view and the explanations are free. History in the app needs Kilobat Pro. Blocking needs Pro and the network filter: see the [network filter](https://kilobat.app/docs/blocking#filtering), [Protection](https://kilobat.app/docs/blocking#protection) and the [hotspot data saver](https://kilobat.app/save-hotspot-data).

## What isn’t documented

Telegram's protocol pages are written for developers. They do not list the helper processes of the Mac app or the exact addresses that the app contacts.

The pages do not say which of the listed transports the Mac app uses first. They do not say how much data an idle app uses.

Telegram does not say in these pages how the Mac app updates itself.

## Questions

**Which ports does Telegram use?**

Telegram documents TCP on ports 80, 443 and 5222, WebSocket on port 80, and HTTPS and WebSocket over HTTPS on port 443. The server may name another port.

**Does Telegram use a CDN?**

Telegram says that it uses encrypted CDN nodes to cache media from public channels with more than 100,000 members.

## Sources

- [Telegram: MTProto transports](https://core.telegram.org/mtproto/transports)
- [Telegram: Working with different data centers](https://core.telegram.org/api/datacenter)
- [Telegram: FAQ for the technically inclined](https://core.telegram.org/techfaq)
- [Kilobat docs: Connections](https://kilobat.app/docs)

Checked on 8 November 2026.
