BTK
BGP inherited
Cluster stats
| Netblocks | 6 |
| All fragments | 47 blocks across 8 clusters |
| Cluster ID | 206008562 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 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-13
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 88.255.155.0/27 | BTK | RIPE | ASSIGNED PA | ● low |
| 2a01:358:4014:600::/56 | BTK | RIPE | ASSIGNED | ● low |
| 2a01:358:4014:a00::/56 | BTK | RIPE | ASSIGNED | ● low |
| 2a01:358:4014:1400::/56 | BTK | RIPE | ASSIGNED | ● low |
| 2a01:358:5210::/48 | BTK-NET | RIPE | ASSIGNED | ● low |
| 2a03:5a00:38::/48 | BTK-NET | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
83.3%
of checked blocks have valid RPKI ROA coverage
(5 of 6)
Possible discrepancies (4)
These blocks are registered to BTK 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.
| 2a01:358:5210::/48 /48 | authorized for AS9121 — Turk Telekomunikasyon Anonim Sirketi |
| 2a01:358:4014:1400::/56 /56 | authorized for AS9121 — Turk Telekomunikasyon Anonim Sirketi |
| 2a01:358:4014:600::/56 /56 | authorized for AS9121 — Turk Telekomunikasyon Anonim Sirketi |
| 2a01:358:4014:a00::/56 /56 | authorized for AS9121 — Turk Telekomunikasyon Anonim Sirketi |
NIC Handles
AS9121-MNT
DUMY-RIPE
DUMY-RIPE
LIDERTELECOM-mnt