Typhoon Communication
BGP inherited
Cluster stats
| Netblocks | 6 · 520 IPv4 addresses |
| Registered in | Russia (2) · India (1) · Netherlands (1) · Ukraine (1) |
| Cluster ID | 209236329 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 5 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-19
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.174.246.244/32 | Typhoon Communication | PEERINGDB | ASSIGNED | ● high |
| 2a0e:46c4:1806:2::244/128 | Typhoon Communication | PEERINGDB | ASSIGNED | ● high |
| 5.102.140.152/30 | Typhoon_Roertechniek | RIPE | ASSIGNED PA | ● low |
| 62.64.90.152/29 | TYPHOON-PLUS-GTUA | RIPE | ASSIGNED PA | ● low |
| 194.84.144.0/24 | TYPHOON-NET | RIPE | ASSIGNED PA | ● low |
| 195.5.143.0/24 | TYPHOON-SPB | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(4 of 6)
Possible discrepancies (1)
These blocks are registered to Typhoon Communication but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 195.5.143.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
NIC Handles
AS138276
DUMY-RIPE
DUMY-RIPE
GTUA-WO-MNT
MNT-MF-NWGSM
ROSPRINT-NCC
TRIBION_SP-MNT