Network · data from 2026-11-12
AS46023 Quantum Tera Network
Registry name: QUANTUMNET-AS-ID - PT Quantum Tera Network, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46023, 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.252.8.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 43.252.8.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 43.252.8.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 43.252.9.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 43.252.10.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 43.252.10.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 43.252.11.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.24.104.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.24.104.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.24.104.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.24.105.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.24.106.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.24.106.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.24.107.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.75.52.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.75.52.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.75.52.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.75.53.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.75.54.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.75.55.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.106.76.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 103.106.76.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.106.77.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.106.78.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 103.106.78.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.106.79.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.245.16.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.245.16.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.245.16.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.245.17.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.245.18.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.245.18.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.245.19.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.8.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.8.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.8.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.9.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.10.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.10.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.11.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.12.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.12.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.12.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.13.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.14.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.14.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 175.106.15.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.145.62.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 203.145.62.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 203.145.63.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.75.54.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 2406:b900::/32 | Valid | Other IRR onlyRADB | 636 100% |
| 103.106.76.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS46023: AS46023:AS-QUANTUMNET. 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 (AS46023 isn't in the set, or no route object for AS46023 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 | AS46023 in it | Not covered |
|---|---|---|---|---|---|
| AS46023:AS-QUANTUMNET | APNIC | 3 | 1 | 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 53 are in fix.csv.
- Route object: RIR52
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 43.252.8.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.252.8.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.252.8.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.252.9.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.252.10.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.252.10.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.252.11.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.104.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.104.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.104.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.105.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.106.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.106.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.24.107.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.75.52.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.75.52.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.75.52.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.75.53.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.75.54.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.75.55.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.106.76.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.106.76.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.106.77.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.106.78.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.106.78.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.106.79.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.245.16.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.245.16.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.245.16.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.245.17.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.245.18.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.245.18.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.245.19.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.8.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.8.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.8.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.9.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.10.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.10.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.11.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.12.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.12.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.12.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.13.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.14.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.14.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 175.106.15.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.145.62.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.145.62.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.145.63.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.75.54.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2406:b900::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46023 whose prefix no peer sees AS46023 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 175.106.8.0/21 | NTTCOM | 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.