bgpreport

Network · data from 2026-11-12

AS33921 Lebara-AS Lebara Ltd

Registry name: Lebara-AS Lebara Ltd, GB · not in PeeringDB

13IPv4 routes 100.0% RPKI valid · 84.6% with a route object
1IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS33921, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS33921, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
141.98.208.0/24 Valid None 673 100% 67
185.5.129.0/24 Valid None 673 100% 67
2a13:a380::/40 Valid None 635 100% 67
5.42.207.0/24 Valid RIR databaseRIPE 673 100% 67
84.246.112.0/24 Valid RIR databaseRIPE 673 100% 67
84.246.113.0/24 Valid RIR databaseRIPE 673 100% 67
84.246.114.0/24 Valid RIR databaseRIPE 673 100% 67
84.246.115.0/24 Valid RIR databaseRIPE 673 100% 67
91.208.59.0/24 Valid RIR databaseRIPE 673 100% 67
194.26.132.0/24 Valid RIR databaseRIPE 673 100% 67
194.213.108.0/24 Valid RIR databaseRIPE 673 100% 67
45.92.79.0/24 Valid RIR databaseRIPE 672 100% 66
185.221.60.0/24 Valid RIR databaseRIPE 671 100% 67
194.99.64.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS33921 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 3 are in fix.csv.

  • Route object: none3
ChangePrefix or setDetailFull-table peers
Route object: none141.98.208.0/24No route object for it. Add a route object with origin AS33921 in the RIR database for the space.673 of 673
Route object: none185.5.129.0/24No route object for it. Add a route object with origin AS33921 in the RIR database for the space.673 of 673
Route object: none2a13:a380::/40No route object for it. Add a route object with origin AS33921 in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS33921 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.