bgpreport

Network · data from 2026-11-12

AS203943 ALEXANDER NICHOLSON

Registry name: NET-AN ALEXANDER NICHOLSON, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203943, 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.
2a0e:b107:5a5::/48 No ROA RIR databaseRADB, RIPE 635 100% 67
2a0e:b107:5a7::/48 No ROA RIR databaseRIPE 635 100% 67
2a0e:b107:5a1::/48 Valid RIR databaseRIPE 635 100% 69
2a0e:b107:5a2::/48 Valid RIR databaseRIPE 635 100% 69
2a0e:b107:5a3::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

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

  • ROA: none2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none2a0e:b107:5a5::/48No ROA covers it. Add a ROA for AS203943, maxLength 48.635 of 636
ROA: none2a0e:b107:5a7::/48No ROA covers it. Add a ROA for AS203943, maxLength 48.635 of 636

Route objects not announced

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

2a06:8180:4::/48RADBNo ROA
2a0e:b107:5a0::/48RIPENo ROA
2a0e:b107:5a4::/48RIPENo ROA
2a0e:b107:5a6::/48RIPENo ROA
2a0e:b107:5a8::/48RIPENo ROA
2a0e:b107:5a9::/48RIPENo ROA
2a0e:b107:5aa::/48RIPENo ROA
2a0e:b107:5ab::/48RIPENo ROA
2a0e:b107:5ac::/48RIPENo ROA
2a0e:b107:5ad::/48RIPENo ROA
2a0e:b107:5ae::/48RIPENo ROA
2a0e:b107:5af::/48RIPENo 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.