bgpreport

Network · data from 2026-11-12

AS34920 Simply-Romford Team Blue Carrier Limited

Registry name: Simply-Romford Team Blue Carrier Limited, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34920, 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.
31.172.240.0/20 No ROA RIR databaseRIPE 673 100% 67
37.220.96.0/21 No ROA RIR databaseRIPE 673 100% 67
46.231.112.0/21 No ROA RIR databaseRIPE 673 100% 67
78.40.32.0/21 No ROA RIR databaseRIPE 673 100% 67
80.241.48.0/21 No ROA RIR databaseRIPE 673 100% 67
94.102.144.0/20 No ROA RIR databaseRIPE 673 100% 67
95.172.0.0/19 No ROA RIR databaseRIPE 673 100% 67
109.109.224.0/19 No ROA RIR databaseRIPE 673 100% 67
130.193.80.0/20 No ROA RIR databaseRIPE 673 100% 67
185.32.200.0/22 No ROA RIR databaseRIPE 673 100% 67
185.77.64.0/22 No ROA RIR databaseRIPE 673 100% 67
185.77.80.0/22 No ROA RIR databaseRIPE 673 100% 67
185.77.172.0/22 No ROA RIR databaseRIPE 673 100% 67
2a01:7b8::/32 No ROA RIR databaseRIPE 633 100% 68

AS-SET

AS34920 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 14 are in fix.csv.

  • ROA: none14
ChangePrefix or setDetailFull-table peers
ROA: none31.172.240.0/20No ROA covers it. Add a ROA for AS34920, maxLength 20.673 of 673
ROA: none37.220.96.0/21No ROA covers it. Add a ROA for AS34920, maxLength 21.673 of 673
ROA: none46.231.112.0/21No ROA covers it. Add a ROA for AS34920, maxLength 21.673 of 673
ROA: none78.40.32.0/21No ROA covers it. Add a ROA for AS34920, maxLength 21.673 of 673
ROA: none80.241.48.0/21No ROA covers it. Add a ROA for AS34920, maxLength 21.673 of 673
ROA: none94.102.144.0/20No ROA covers it. Add a ROA for AS34920, maxLength 20.673 of 673
ROA: none95.172.0.0/19No ROA covers it. Add a ROA for AS34920, maxLength 19.673 of 673
ROA: none109.109.224.0/19No ROA covers it. Add a ROA for AS34920, maxLength 19.673 of 673
ROA: none130.193.80.0/20No ROA covers it. Add a ROA for AS34920, maxLength 20.673 of 673
ROA: none185.32.200.0/22No ROA covers it. Add a ROA for AS34920, maxLength 22.673 of 673
ROA: none185.77.64.0/22No ROA covers it. Add a ROA for AS34920, maxLength 22.673 of 673
ROA: none185.77.80.0/22No ROA covers it. Add a ROA for AS34920, maxLength 22.673 of 673
ROA: none185.77.172.0/22No ROA covers it. Add a ROA for AS34920, maxLength 22.673 of 673
ROA: none2a01:7b8::/32No ROA covers it. Add a ROA for AS34920, maxLength 32.633 of 636

Route objects not announced

Every route object with origin AS34920 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.