CLOUD-IP // v2026.05
UPDATED 2026-05-26 PROVIDERS 24 LIVE
// TELEGRAM / NGINX

Telegram · Nginx

Nginx allow/deny config for Telegram. Drop into your server block or http context. 14 CIDRs, refreshed daily.

// nginx_telegram_allow.conf

DOWNLOAD ↓  · 
# Telegram IP Ranges
# Updated: 2026-02-11 17:28:49
# Source: https://github.com/rezmoss/cloud-provider-ip-addresses
# License: https://github.com/rezmoss/cloud-provider-ip-addresses/LICENSE
# This file is generated automatically. Do not edit it directly.
# Updates daily at 00:00 UTC
# To restrict access to only these IPs in nginx,
# add the following line to your server block in your nginx configuration file (e.g., /etc/nginx/nginx.conf or /etc/nginx/sites-available/default):
# include /path/to/nginx_telegram_allow.conf;

allow 91.108.56.0/22;
allow 91.108.4.0/22;
allow 91.108.8.0/22;
allow 91.108.16.0/22;
allow 91.108.12.0/22;
allow 149.154.160.0/20;
allow 91.105.192.0/23;
allow 91.108.20.0/22;
allow 185.76.151.0/24;
allow 2001:b28:f23d::/48;
allow 2001:b28:f23f::/48;
allow 2001:67c:4e8::/48;
allow 2001:b28:f23c::/48;
allow 2a0a:f280::/32;
deny all;

// nginx_telegram_deny.conf

DOWNLOAD ↓  · 
# Telegram IP Ranges
# Updated: 2026-02-11 17:28:49
# Source: https://github.com/rezmoss/cloud-provider-ip-addresses
# License: https://github.com/rezmoss/cloud-provider-ip-addresses/LICENSE
# This file is generated automatically. Do not edit it directly.
# Updates daily at 00:00 UTC
# To deny access from these IPs in nginx,
# add the following line to your server block in your nginx configuration file (e.g., /etc/nginx/nginx.conf or /etc/nginx/sites-available/default):
# include /path/to/nginx_telegram_deny.conf;

deny 91.108.56.0/22;
deny 91.108.4.0/22;
deny 91.108.8.0/22;
deny 91.108.16.0/22;
deny 91.108.12.0/22;
deny 149.154.160.0/20;
deny 91.105.192.0/23;
deny 91.108.20.0/22;
deny 185.76.151.0/24;
deny 2001:b28:f23d::/48;
deny 2001:b28:f23f::/48;
deny 2001:67c:4e8::/48;
deny 2001:b28:f23c::/48;
deny 2a0a:f280::/32;
allow all;