Telegram Messenger NA
BGP inherited
Cluster stats
| Netblocks | 6 |
| Registered in | United States (2) · Brazil (1) |
| All fragments | 113 blocks across 2 clusters |
| Cluster ID | 213184807 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 187.16.209.180/32 | Telegram Messenger NA | PEERINGDB | ASSIGNED | ● high |
| 198.32.242.10/32 | Telegram Messenger NA | PEERINGDB | ASSIGNED | ● high |
| 206.41.108.63/32 | Telegram Messenger NA | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:6:0:5:9930:2/128 | Telegram Messenger NA | PEERINGDB | ASSIGNED | ● high |
| 2001:504:40:108::1:63/128 | Telegram Messenger NA | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::209:180/128 | Telegram Messenger NA | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(4 of 6)
No discrepancies found among checked blocks.
NIC Handles
AS59930