Network · data from 2026-11-12
AS140401 PROXINET
Registry name: PROXINET-AS-ID - PT Proxi Jaringan Nusantara, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140401, 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.
| 149.7.63.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.187.116.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.187.117.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.184.54.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.184.55.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.150.218.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 103.150.219.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 45.198.249.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS140401: AS140401:AS-PROXINET. 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 (AS140401 isn't in the set, or no route object for AS140401 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 | AS140401 in it | Not covered |
|---|---|---|---|---|---|
| AS140401:AS-PROXINET | APNIC | 2 | 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 13 are in fix.csv.
- ROA: none1
- Route object: RIR7
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 149.7.63.0/24 | No ROA covers it. Add a ROA for AS140401, maxLength 24. |
| Route object: RIR | 149.7.63.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.187.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.187.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.184.54.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.184.55.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.150.218.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.150.219.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140401 whose prefix no peer sees AS140401 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.198.232.0/23 | AFRINIC | Invalid: origin |
| 45.198.248.0/24 | AFRINIC, RADB | Valid |
| 103.150.218.0/23 | RADB | Valid |
| 103.184.54.0/23 | RADB | Valid |
| 103.187.116.0/23 | 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.