bgpreport

Network · data from 2026-11-12

AS34282 UKNOC-AS Team Blue Carrier Limited

Registry name: UKNOC-AS Team Blue Carrier Limited, GB · not in PeeringDB

5IPv4 routes 20.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
5No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
34Route objects not announced registered with origin AS34282, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS34282, 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.

85.92.72.0/24 No ROA Other IRR onlyRADB 672 100% 67
81.19.176.0/20 No ROA RIR databaseRIPE 673 100% 67
5.134.8.0/21 No ROA RIR databaseRIPE 670 100% 67
85.92.64.0/19 No ROA RIR databaseRIPE 670 100% 67
2a00:b0e0::/32 No ROA RIR databaseRIPE 633 100% 68
193.117.57.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS34282 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 40 are in fix.csv.

  • ROA: none5
  • Route object: RIR1
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
ROA: none85.92.72.0/24No ROA covers it. Add a ROA for AS34282, maxLength 24.672 of 673
Route object: RIR85.92.72.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none81.19.176.0/20No ROA covers it. Add a ROA for AS34282, maxLength 20.673 of 673
ROA: none5.134.8.0/21No ROA covers it. Add a ROA for AS34282, maxLength 21.670 of 673
ROA: none85.92.64.0/19No ROA covers it. Add a ROA for AS34282, maxLength 19.670 of 673
ROA: none2a00:b0e0::/32No ROA covers it. Add a ROA for AS34282, maxLength 32.633 of 636

Route objects not announced

Route objects with origin AS34282 whose prefix no peer sees AS34282 announce. Many are kept on purpose (backup routes, space announced only in some places).

85.92.64.0/24RADBNo ROA
85.92.65.0/24RADBNo ROA
85.92.66.0/24RADBNo ROA
85.92.67.0/24RADBNo ROA
85.92.68.0/24RADBNo ROA
85.92.69.0/24RADBNo ROA
85.92.70.0/24RADBNo ROA
85.92.71.0/24RADBNo ROA
85.92.73.0/24RADBNo ROA
85.92.74.0/24RADBNo ROA
85.92.75.0/24RADBNo ROA
85.92.76.0/24RADBNo ROA
85.92.77.0/24RADBNo ROA
85.92.78.0/24RADBNo ROA
85.92.79.0/24RADBNo ROA
85.92.80.0/24RADBNo ROA
85.92.81.0/24RADBNo ROA
85.92.82.0/24RADBNo ROA
85.92.83.0/24RADBNo ROA
85.92.84.0/24RADBNo ROA
85.92.85.0/24RADBNo ROA
85.92.86.0/24RADBNo ROA
85.92.87.0/24RADBNo ROA
85.92.88.0/24RADBNo ROA
85.92.89.0/24RADBNo ROA
85.92.90.0/24RADBNo ROA
85.92.91.0/24RADBNo ROA
85.92.92.0/24RADBNo ROA
85.92.93.0/24RADBNo ROA
85.92.94.0/24RADBNo ROA
85.92.95.0/24RADBNo ROA
185.203.12.0/22RIPENo ROA
193.53.36.0/24RIPENo ROA
194.1.151.0/24RIPENo ROA

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.