bgpreport

Network · data from 2026-11-12

AS17635 GoldNet Pty Ltd

Registry name: GOLDNETPTYLTD-AS-AP - GoldNet Pty Ltd, AU · PeeringDB

18IPv4 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
16Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS17635, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17635, 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.

203.14.105.0/24 Valid RIR databaseAPNIC 672 100% 66
203.57.128.0/20 Valid RIR databaseAPNIC 672 100% 66
2406:9680::/32 Valid RIR databaseAPNIC 634 100% 68
203.57.128.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.129.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.130.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.131.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.132.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.133.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.134.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.135.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.136.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.137.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.138.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.139.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.140.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.141.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.142.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34
203.57.143.0/24 Valid RIR databaseAPNIC 67 10%low visibility 34

AS-SET

PeeringDB's irr_as_set for AS17635: APNIC::AS17635:AS-GOLDNET. 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 (AS17635 isn't in the set, or no route object for AS17635 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 objectsAS17635 in itNot covered
APNIC::AS17635:AS-GOLDNET APNIC 4237 Yes 0

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.

  • Route object: not announced14

Route objects not announced

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

203.57.128.0/21APNICValid
203.57.128.0/22APNICValid
203.57.128.0/23APNICValid
203.57.130.0/23APNICValid
203.57.132.0/22APNICValid
203.57.132.0/23APNICValid
203.57.134.0/23APNICValid
203.57.136.0/21APNICValid
203.57.136.0/22APNICValid
203.57.136.0/23APNICValid
203.57.138.0/23APNICValid
203.57.140.0/22APNICValid
203.57.140.0/23APNICValid
203.57.142.0/23APNICValid

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.