--- title: "EDM115 Telegram blog" canonical_url: "https://edm115.dev/blog/telegram/2022/10/25/peer-id-bug" last_updated: "2026-08-30T03:10:29.311Z" meta: description: "Find all infos about EDM115, my projects, blog posts, ..." "og:description": "[peer-id-bug-1] πŸ—žοΈ TELEGRAM NEWS πŸ—žοΈ Since few days, a weird behavior of the Telegram API have been reported (I also personally noticed it) Requesting to get infos through user ID may fail with some pr..." "og:title": "EDM115 Telegram blog" "twitter:title": "EDM115 Telegram blog" --- Home](https://edm115.dev/) ](https://edm115.dev/projects)](https://edm115.dev/blog)](https://edm115.dev/codex)](https://edm115.dev/unzip) ![peer-id-bug-1](https://edm115.dev/img/blog/2022/10-25-peer-id-bug-1.webp) πŸ—žοΈ TELEGRAM NEWS πŸ—žοΈ Since few days, a weird behavior of the Telegram API have been reported (I also personally noticed it) Requesting to get infos through user ID may fail with some profiles However, doing the same with the username works fine It also affects [Pyrogram](https://docs.pyrogram.org/api/types/User), no clue about Telethon yet It gets problematic with some users which don’t have usernames. Also bots can struggle with this, as shown here ![peer-id-bug-2](https://edm115.dev/img/blog/2022/10-25-peer-id-bug-2.webp) example πŸ‘†