bgpreport

Network · data from 2026-11-12

AS63279 XKEY

Registry name: XKEY - XKEY, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63279, 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.
2602:feda:3f0::/44 No ROA RIR databaseARIN 635 100% 69
170.39.203.0/24 Valid RIR databaseARIN 671 100% 68
2406:840:ece0::/44 Valid RIR databaseAPNIC 635 100% 69
2602:806:b000::/40 Valid RIR databaseARIN 635 100% 69
2602:806:b0fe::/48 Valid RIR databaseARIN 635 100% 69
2602:806:b0ff::/48 Valid RIR databaseARIN 635 100% 69
2a06:a005:1d90::/44 Valid RIR databaseRIPE 634 100% 69
2a0e:b107:a00::/44 Valid RIR databaseRIPE 634 100% 69
2a0e:b107:a20::/44 Valid RIR databaseRIPE 634 100% 69
2a0e:b107:b20::/44 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS63279'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 38 are in fix.csv.

  • ROA: none1
  • Route object: not announced37
ChangePrefix or setDetailFull-table peers
ROA: none2602:feda:3f0::/44No ROA covers it. Add a ROA for AS63279, maxLength 44.635 of 636

Route objects not announced

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

2406:840:ece0::/45APNICValid
2406:840:ece0::/46APNICValid
2406:840:ece0::/47APNICValid
2406:840:ece0::/48APNICValid
2406:840:ece1::/48APNICValid
2406:840:ece2::/47APNICValid
2406:840:ece2::/48APNICValid
2406:840:ece3::/48APNICValid
2406:840:ece4::/46APNICValid
2406:840:ece4::/47APNICValid
2406:840:ece4::/48APNICValid
2406:840:ece5::/48APNICValid
2406:840:ece6::/47APNICValid
2406:840:ece6::/48APNICValid
2406:840:ece7::/48APNICValid
2406:840:ece8::/45APNICValid
2406:840:ece8::/46APNICValid
2406:840:ece8::/47APNICValid
2406:840:ece8::/48APNICValid
2406:840:ece9::/48APNICValid
2406:840:ecea::/47APNICValid
2406:840:ecea::/48APNICValid
2406:840:eceb::/48APNICValid
2406:840:ecec::/46APNICValid
2406:840:ecec::/47APNICValid
2406:840:ecec::/48APNICValid
2406:840:eced::/48APNICValid
2406:840:ecee::/47APNICValid
2406:840:ecee::/48APNICValid
2406:840:ecef::/48APNICValid
2602:feda:3f9::/48ARINNo ROA
2602:feda:3fb::/48ARINNo ROA
2602:feda:3fc::/47ARINNo ROA
2602:feda:3fc::/48ARINNo ROA
2602:feda:3fd::/48ARINNo ROA
2602:feda:3fe::/48ARINNo ROA
2602:feda:3fe:f000::/54ARINNo 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.