TRANSPORT FOR LONDON

Transport for London
GLEIF verified
LEI
213800FGQ9DJHGRLQZ89
Registered name
TRANSPORT FOR LONDON
Jurisdiction
GB
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks8 · 9,474 IPv4 addresses
All fragments 43 blocks across 4 clusters
Cluster ID209517705
RegistryBGP
Owner jurisdictionGB
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 213800FGQ9DJHGRLQZ89
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.79.208.0/20 Transport for London BGP ANNOUNCED ● high
80.79.216.0/23 Transport for London BGP ANNOUNCED ● high
80.79.222.0/24 Transport for London BGP ANNOUNCED ● high
80.79.222.0/23 Transport for London BGP ANNOUNCED ● high
80.79.208.0/20 Transport for London RIPE ALLOCATED PA ● low
194.75.138.152/29 TRANSPORT-FOR-LONDON RIPE ASSIGNED PA ● low
2a00:2381:2cf1::/48 TRANSPORT-FOR-LONDON RIPE AGGREGATED-BY-LIR ● low
2a04:da80::/29 Transport for London RIPE ALLOCATED-BY-RIR ● low

Network trust

what's this?
RPKI hygiene: D how networks compare →
25.0% of checked blocks have valid RPKI ROA coverage (2 of 8)
Possible discrepancies (1)

These blocks are registered to Transport for London 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:2cf1::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

AS196778 AS199262 BTNET-MNT DUMY-RIPE DUMY-RIPE ORG-TfL1-RIPE RIPE-NCC-HM-MNT mnt-guruprashant taskhan-mntner