bgpreport

Network · data from 2026-11-12

AS23703 RIGNET-AS-AP - RigNet, Communication to remote locations in Asia/Pacific.

Registry name: RIGNET-AS-AP - RigNet, Communication to remote locations in Asia/Pacific., SG · not in PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
2Route objects not announced registered with origin AS23703, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23703, 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.
202.78.16.0/20 Valid RIR databaseAPNIC, RADB 671 100% 68
2405:d980::/32 Valid RIR databaseAPNIC 634 100% 69

AS-SET

AS23703 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 2 are in fix.csv.

  • Route object: not announced2

Route objects not announced

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

202.78.31.0/24APNICValid
2001:470:314::/48ARINValid

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.