bgpreport

Network · data from 2026-11-12

AS6838 FLIRBLE-AS Christopher Luke

Registry name: FLIRBLE-AS Christopher Luke, GB · not in PeeringDB

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

Announced routes

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

212.134.0.0/24 No ROA Other IRR onlyRADB 673 100% 67
212.134.6.0/24 No ROA Other IRR onlyRADB 673 100% 67
212.134.7.0/24 No ROA Other IRR onlyRADB 673 100% 67
207.162.200.0/24 No ROA RIR databaseARIN, RADB, RIPE-NONAUTH 673 100% 67
212.134.0.0/21 No ROA RIR databaseRADB, RIPE 673 100% 67
212.134.1.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
212.134.2.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
212.134.3.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
212.134.4.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
2620:124:9001::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:9002::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:9003::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:9004::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:9005::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:9006::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:9008::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:9009::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:900a::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:900b::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:900c::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:900d::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:900e::/48 Valid Other IRR onlyRADB 609 96% 68
2620:124:9007::/48 Valid Other IRR onlyRADB 228 36% 59
2620:124:9000::/44 Valid RIR databaseARIN, RADB 609 96% 68

AS-SET

AS6838 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 30 are in fix.csv.

  • ROA: none9
  • Route object: RIR17
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none212.134.0.0/24No ROA covers it. Add a ROA for AS6838, maxLength 24.673 of 673
Route object: RIR212.134.0.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none212.134.6.0/24No ROA covers it. Add a ROA for AS6838, maxLength 24.673 of 673
Route object: RIR212.134.6.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none212.134.7.0/24No ROA covers it. Add a ROA for AS6838, maxLength 24.673 of 673
Route object: RIR212.134.7.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.162.200.0/24No ROA covers it. Add a ROA for AS6838, maxLength 24.673 of 673
ROA: none212.134.0.0/21No ROA covers it. Add a ROA for AS6838, maxLength 21.673 of 673
ROA: none212.134.1.0/24No ROA covers it. Add a ROA for AS6838, maxLength 24.673 of 673
ROA: none212.134.2.0/24No ROA covers it. Add a ROA for AS6838, maxLength 24.673 of 673
ROA: none212.134.3.0/24No ROA covers it. Add a ROA for AS6838, maxLength 24.673 of 673
ROA: none212.134.4.0/24No ROA covers it. Add a ROA for AS6838, maxLength 24.673 of 673
Route object: RIR2620:124:9001::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:9002::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:9003::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:9004::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:9005::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:9006::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:9008::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:9009::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:900a::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:900b::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:900c::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:900d::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:900e::/48Route object only in RADB. Add it in the RIR database for the space.609 of 636
Route object: RIR2620:124:9007::/48Route object only in RADB. Add it in the RIR database for the space.228 of 636

Route objects not announced

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

194.70.3.0/24RADB, RIPENo ROA
212.134.5.0/24RADB, RIPENo ROA
2620:124:9000::/48RADBValid
2620:124:900f::/48RADBValid

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.