bgpreport

Network · data from 2026-11-12

AS138399 VADACOMLIMITED-AS-AP - VADACOM LIMITED

Registry name: VADACOMLIMITED-AS-AP - VADACOM LIMITED, NZ · not in PeeringDB

0IPv4 routes
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
11Route objects not announced registered with origin AS138399, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS138399, 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.
2403:e040::/32 Valid RIR databaseAPNIC, RADB 635 100% 69

AS-SET

AS138399 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 11 are in fix.csv.

  • Route object: not announced11

Route objects not announced

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

103.124.132.0/22APNIC, RADBValid
103.124.132.0/24APNICValid
103.124.133.0/24APNICValid
103.124.134.0/24APNICValid
103.124.135.0/24APNICValid
2403:e040::/33APNICValid
2403:e040::/34APNICValid
2403:e040:4000::/34APNICValid
2403:e040:8000::/33APNICValid
2403:e040:8000::/34APNICValid
2403:e040:c000::/34APNICValid

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.