Some systems are having problems. Open the status page
Keep your single getUpdates loop alive and your webhook port open: static IP, always on, full root access.
The Telegram Bot API delivers updates in two ways. With long polling your bot holds a getUpdates call open and Telegram keeps it waiting until something arrives; kill the process and the loop dies with it. Open a second getUpdates for the same token and Telegram answers 409 Conflict, so you cannot simply run the bot in two places. Moving it to a server settles that.
With a webhook the direction flips: Telegram calls you. That needs HTTPS with a valid certificate on one of the four ports Telegram supports, 443, 80, 88 or 8443. If you use a self-signed certificate you have to upload the public key through the certificate parameter of setWebhook. None of this works from behind a home connection; you need a host that is reachable from outside.
What grows the requirement is not the number of bots but what they process. A text-driven bot gets by on a few hundred megabytes. Media conversion, Redis-backed FSM state or your own local Bot API server change the picture: run tdlib's telegram-bot-api on your own machine and the upload limit goes from 50 MB to 2000 MB, with no size cap on downloads. That is one of the most concrete reasons to have a server of your own.
Setup guide How to Install and Use Docker on a VDS: Beginner Guide
Your server runs on redundant power and network in a data centre. Define the bot as a systemd service or a pm2 process and it comes back on its own after a crash. Schedule recurring work with python-telegram-bot's JobQueue, with APScheduler, or straight from cron and systemd timers.
You connect as root. Build on aiogram's Dispatcher and Router structure, on python-telegram-bot's Application and ConversationHandler, or on Telegraf or grammY in Node.js. If you would rather keep FSM state in Redis than in MemoryStorage, Redis goes on the same machine.
Your server comes with an IP that does not change, and the ports are yours to manage. Open 443, 80, 88 or 8443 for the webhook and verify with secret_token that the request really came from Telegram. When an external service whitelists by address, the fixed IP is already there.
The server is entirely yours, so run as many processes as you like. A Telegram bot, a Discord bot, scheduled scripts, a Redis instance and a small web panel coexist comfortably. Conflicting version requirements go into separate Docker containers.
The table assumes the bots run alone on the server. If a database, media processing or a local Bot API server shares the machine, pick one tier higher.
| Usage | Plan | Hardware | Monthly | Note | Order |
|---|---|---|---|---|---|
| 1-3 bots · long polling | ENT-1 | 2 vCPU · 2 GB DDR4 ECC · 30 GB NVMe | ₺160 | Telegram and the bot libraries publish no memory figure for this workload | Buy now |
| Webhook · FSM in Redis recommended | ENT-2 | 2 vCPU · 4 GB DDR4 ECC · 40 GB NVMe | ₺240 | setWebhook opens 40 simultaneous connections by default; lower it to limit load on your server | Buy now |
| Media-processing bot | ENT-3 | 4 vCPU · 6 GB DDR4 ECC · 60 GB NVMe | ₺320 | Headroom for the ffmpeg load; Telegram publishes no figure for this workload | Buy now |
| Local Bot API · scraping | ENT-5 | 8 vCPU · 10 GB DDR4 ECC · 100 GB NVMe | ₺480 | A local server raises uploads to 2000 MB and removes the download limit, so disk is what decides | Buy now |
Every plan includes a 10 Gbps uplink, DDR4 ECC memory and NVMe SSD storage. Upgrade any time.
The Xeon Enterprise line is more than enough for hosting bots and scripts. Media conversion and a local Bot API server benefit clearly from the Premium line.
A selection of technical articles from our blog.
Run your Telegram bot and scheduled scripts 24/7 on a VDS. Python virtual environments, systemd timers, cron, Docker isolation and log management.
Install Docker on a Linux VDS, run your first containers, orchestrate services with Docker Compose and deploy a web app, step by step.
New to Linux servers? Learn how to connect over SSH, run the essential commands, harden the firewall and lock down your VDS on day one.
Common questions
Your server is ready 60 seconds after payment. Use code W10 for 10% off your first order.
Our support team is here to assist you with any questions or issues you may have. Contact us via phone, email, or visit our office during business hours.
