bgpreport

Network · data from 2026-11-12

AS58666 Vorco

Registry name: NASL-AS-AP - Vorco, NZ · PeeringDB

12IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
8Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS58666, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS58666, 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.
43.245.80.0/22 Valid RIR databaseAPNIC, RADB 672 100% 68
103.14.68.0/22 Valid RIR databaseAPNIC, RADB 672 100% 68
103.232.156.0/23 Valid RIR databaseAPNIC, RADB 672 100% 68
103.232.158.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
103.232.180.0/22 Valid RIR databaseAPNIC, RADB 672 100% 68
202.12.104.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
2404:5700::/32 Valid RIR databaseAPNIC, RADB 636 100% 69
2404:5700::/33 Valid RIR databaseAPNIC, RADB 55 9%low visibility 30
2404:5700:8000::/33 Valid RIR databaseAPNIC, RADB 55 9%low visibility 30
43.245.80.0/23 Valid RIR databaseAPNIC, RADB 52 8%low visibility 29
43.245.82.0/23 Valid RIR databaseAPNIC, RADB 52 8%low visibility 29
103.14.68.0/23 Valid RIR databaseAPNIC, RADB 52 8%low visibility 29
103.14.70.0/23 Valid RIR databaseAPNIC, RADB 52 8%low visibility 29
103.232.180.0/23 Valid RIR databaseAPNIC, RADB 52 8%low visibility 29
103.232.182.0/23 Valid RIR databaseAPNIC, RADB 52 8%low visibility 29

AS-SET

PeeringDB's irr_as_set for AS58666: AS-VORCO. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS58666 isn't in the set, or no route object for AS58666 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS58666 in itNot covered
AS-VORCO RADB 4123 Yes 0
APNIC (also) 4123 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS58666 is announced.

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.