Network · data from 2026-11-12
AS150692 Golden Dragon 2000
Registry name: GD2CL-AS-AP - Golden Dragon 2000, MM · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS150692, 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.59.162.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.59.163.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 2400:cea0:c000::/36 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2400:cea0:d000::/36 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2400:cea0:e000::/36 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2400:cea0:f000::/36 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2400:cea0::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:1000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:2000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:3000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:4000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:5000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:6000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:7000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:8000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:9000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:a000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
| 2400:cea0:b000::/36 | Valid | RIR databaseAPNIC, RADB | 316 50% |
AS-SET
PeeringDB's irr_as_set for AS150692: AS-DRAGONNET. 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 (AS150692 isn't in the set, or no route object for AS150692 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.
| Name | Database | ASNs | Sets | AS150692 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-DRAGONNET | In no IRR database read today. | |||||
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 7 are in fix.csv.
- AS-SET: not found1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: not found | AS-DRAGONNET | PeeringDB names AS-DRAGONNET; no IRR database read has it. |
Route objects not announced
Route objects with origin AS150692 whose prefix no peer sees AS150692 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.158.252.0/24 | NTTCOM, RADB | No ROA |
| 38.158.253.0/24 | NTTCOM, RADB | No ROA |
| 38.158.254.0/24 | NTTCOM, RADB | No ROA |
| 38.158.255.0/24 | NTTCOM, RADB | No ROA |
| 103.59.162.0/23 | APNIC, NTTCOM, RADB | Valid |
| 2400:cea0::/32 | APNIC, RADB | Valid |
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.