TRAVEL-UP
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 120 blocks across 83 clusters |
| Cluster ID | 193734250 |
| 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 | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 212.169.62.160/30 | TRAVEL-UP | RIPE | ASSIGNED PA | ● low |
| 217.158.101.200/30 | TRAVEL-UP | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:3fd9::/48 | TRAVEL-UP | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a00:2381:f5da::/48 | TRAVEL-UP-LTD | RIPE | AGGREGATED-BY-LIR | ● low |
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 (2)
These blocks are registered to TRAVEL-UP 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.
| 2a00:2381:f5da::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
| 2a00:2381:3fd9::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
NIC Handles
AS8426-MNT
BTNET-MNT
DUMY-RIPE
DUMY-RIPE