bgpreport

Network · data from 2026-11-12

AS199018 Xkrme Network

Registry name: ASXKRME Xkrme Network LLC, US · PeeringDB

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

Announced routes

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

2a0f:1cc5:350::/44 Invalid: origin None 9 1%low visibility 9
2a0f:1cc5:300::/44 Invalid: origin None 2 0%low visibility 2
2a0f:1cc5:310::/46 Invalid: origin None 2 0%low visibility 2
2a0f:1cc5:320::/44 Invalid: origin None 2 0%low visibility 2
2a0f:1cc5:318::/46 Invalid: origin None 1 0%low visibility 1
2a0f:1cc5:31c::/46 Invalid: origin None 1 0%low visibility 1
2a0f:1cc5:330::/44 Invalid: origin None 1 0%low visibility 1
2a0f:1cc5:360::/44 Invalid: origin None 1 0%low visibility 1
2a14:67c1:920::/44 Valid RIR databaseRIPE 636 100% 69
2a14:67c1:900::/48 Valid RIR databaseRIPE 635 100% 67
2a14:67c1:9c0::/42 Valid RIR databaseRIPE 632 99% 69
2a14:67c1:901::/48 Valid RIR databaseRIPE 627 99% 67
2a14:67c1:902::/48 Valid RIR databaseRIPE 2 0%low visibility 3
2a14:67c1:900::/44 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS199018's PeeringDB record names no 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 18 are in fix.csv.

  • ROA: origin8
  • Route object: none8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin2a0f:1cc5:350::/44ROAs covering it name AS31898, AS218167, not AS199018. If AS199018 should announce it, add a ROA for AS199018.9 of 636
Route object: none2a0f:1cc5:350::/44No route object for it. Add a route object with origin AS199018 in the RIR database for the space.9 of 636
ROA: origin2a0f:1cc5:300::/44ROAs covering it name AS218167, not AS199018. If AS199018 should announce it, add a ROA for AS199018.2 of 636
Route object: none2a0f:1cc5:300::/44No route object for it. Add a route object with origin AS199018 in the RIR database for the space.2 of 636
ROA: origin2a0f:1cc5:310::/46ROAs covering it name AS218167, not AS199018. If AS199018 should announce it, add a ROA for AS199018.2 of 636
Route object: none2a0f:1cc5:310::/46No route object for it. Add a route object with origin AS199018 in the RIR database for the space.2 of 636
ROA: origin2a0f:1cc5:320::/44ROAs covering it name AS218167, not AS199018. If AS199018 should announce it, add a ROA for AS199018.2 of 636
Route object: none2a0f:1cc5:320::/44No route object for it. Add a route object with origin AS199018 in the RIR database for the space.2 of 636
ROA: origin2a0f:1cc5:318::/46ROAs covering it name AS218167, not AS199018. If AS199018 should announce it, add a ROA for AS199018.1 of 636
Route object: none2a0f:1cc5:318::/46No route object for it. Add a route object with origin AS199018 in the RIR database for the space.1 of 636
ROA: origin2a0f:1cc5:31c::/46ROAs covering it name AS218167, not AS199018. If AS199018 should announce it, add a ROA for AS199018.1 of 636
Route object: none2a0f:1cc5:31c::/46No route object for it. Add a route object with origin AS199018 in the RIR database for the space.1 of 636
ROA: origin2a0f:1cc5:330::/44ROAs covering it name AS218167, not AS199018. If AS199018 should announce it, add a ROA for AS199018.1 of 636
Route object: none2a0f:1cc5:330::/44No route object for it. Add a route object with origin AS199018 in the RIR database for the space.1 of 636
ROA: origin2a0f:1cc5:360::/44ROAs covering it name AS218167, not AS199018. If AS199018 should announce it, add a ROA for AS199018.1 of 636
Route object: none2a0f:1cc5:360::/44No route object for it. Add a route object with origin AS199018 in the RIR database for the space.1 of 636

Route objects not announced

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

2a14:67c1:903::/48RIPEValid
2a14:67c1:910::/46RIPEValid

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.