bgpreport

Network · data from 2026-11-12

AS131296 REXNETWORKS

Registry name: REXNETWORKS-AS-AP - REXNETWORKS LIMITED, NZ · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS131296, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131296, 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.
103.68.228.0/22 Valid RIR databaseAPNIC 671 100% 68
180.222.124.0/22 Valid RIR databaseAPNIC 671 100% 68

AS-SET

AS131296'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 12 are in fix.csv.

  • Route object: not announced12

Route objects not announced

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

103.68.228.0/23APNICValid
103.68.228.0/24APNICValid
103.68.229.0/24APNICValid
103.68.230.0/23APNICValid
103.68.230.0/24APNICValid
103.68.231.0/24APNICValid
180.222.124.0/23APNICValid
180.222.124.0/24APNICValid
180.222.125.0/24APNICValid
180.222.126.0/23APNICValid
180.222.126.0/24APNICValid
180.222.127.0/24APNICValid

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.