Network · data from 2026-11-12
AS44907 Telegram_Messenger_CDN Telegram Messenger Inc
Registry name: Telegram_Messenger_CDN Telegram Messenger Inc, VG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44907, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 91.108.20.0/23 | Valid | Nonecovered by 91.108.20.0/22 | 671 100% |
| 91.108.20.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2001:b28:f23c::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS44907 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 8 are in fix.csv.
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 91.108.20.0/23 | No route object for it. A route object for 91.108.20.0/22 with origin AS44907 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44907 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS44907 whose prefix no peer sees AS44907 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.108.36.0/23 | RIPE | No ROA |
| 91.108.38.0/23 | RIPE | No ROA |
| 95.161.84.0/22 | RIPE | No ROA |
| 95.161.84.0/23 | RIPE | No ROA |
| 95.161.86.0/23 | RIPE | No ROA |
| 2001:b28:f23b::/48 | RIPE | Invalid: origin |
| 2001:b28:f242::/48 | RIPE | Invalid: origin |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.