Network · data from 2026-11-12
AS38145 Panca Dewata Utama
Registry name: PANCA-AS-ID - PT. Panca Dewata Utama, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38145, 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.
| 2405:fc0::/32 | No ROA | None | 2 0%low visibility |
| 202.180.48.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 673 100% |
| 202.180.51.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 673 100% |
| 202.180.53.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 673 100% |
| 202.180.54.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 673 100% |
| 202.180.55.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 673 100% |
| 202.180.49.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 202.180.50.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS38145: AS38145:AS-PORTLINK-ID. 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 (AS38145 isn't in the set, or no route object for AS38145 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 | AS38145 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS38145:AS-PORTLINK-ID | 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 17 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR5
- AS-SET: not found1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2405:fc0::/32 | No ROA covers it. Add a ROA for AS38145, maxLength 32. |
| Route object: none | 2405:fc0::/32 | No route object for it. Add a route object with origin AS38145 in the RIR database for the space. |
| Route object: RIR | 202.180.48.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.180.51.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.180.53.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.180.54.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 202.180.55.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| AS-SET: not found | AS38145:AS-PORTLINK-ID | PeeringDB names AS38145:AS-PORTLINK-ID; no IRR database read has it. |
Route objects not announced
Route objects with origin AS38145 whose prefix no peer sees AS38145 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.180.48.0/21 | APNIC, NTTCOM | No ROA |
| 202.180.48.0/22 | NTTCOM | No ROA |
| 202.180.48.0/23 | NTTCOM, RADB | No ROA |
| 202.180.50.0/23 | NTTCOM | No ROA |
| 202.180.52.0/22 | NTTCOM | No ROA |
| 202.180.52.0/23 | NTTCOM | No ROA |
| 202.180.52.0/24 | NTTCOM, REACH | Valid |
| 202.180.54.0/23 | NTTCOM, RADB | No ROA |
| 203.191.40.0/21 | NTTCOM, RADB | No ROA |
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.