START TELECOM
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 11 blocks across 3 clusters |
| Cluster ID | 204717502 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
3 weekly snapshots · JSON
9
0 netblocks since 2026-07-05
2026-07-05
peak 9
2026-07-12
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.187.40.0/22 | AS269484 | BGP | ANNOUNCED | ● medium |
| 45.187.41.0/24 | START TELECOM | BGP | ANNOUNCED | ● medium |
| 2804:6558::/32 | AS269484 | BGP | ANNOUNCED | ● medium |
| 2804:6558::/33 | START TELECOM | BGP | ANNOUNCED | ● medium |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (4)
These blocks are registered to START TELECOM 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.
| 2804:6558::/32 /32 | authorized for AS269484 — AS269484 |
| 2804:6558::/33 /33 | authorized for AS269484 — AS269484 |
| 45.187.40.0/22 /22 | authorized for AS269484 — AS269484 |
| 45.187.41.0/24 /24 | authorized for AS269484 — AS269484 |
NIC Handles
AS269484