Network · data from 2026-11-12
AS45291 Prima Telekom Indonesia
Registry name: PTINET-AS-ID - PT Prima Telekom Indonesia, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45291, 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.
| 2406:80c0::/32 | No ROA | Other IRR onlyRADB | 635 100% |
| 103.156.72.0/24 | Valid | Nonecovered by 103.156.72.0/23 | 673 100% |
| 103.156.73.0/24 | Valid | Nonecovered by 103.156.72.0/23 | 673 100% |
| 203.153.216.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.153.217.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.153.218.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.153.219.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS45291: AS45291:AS-PTI. 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 (AS45291 isn't in the set, or no route object for AS45291 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 | AS45291 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS45291:AS-PTI | 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 16 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: RIR5
- AS-SET: not found1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2406:80c0::/32 | No ROA covers it. Add a ROA for AS45291, maxLength 32. |
| Route object: RIR | 2406:80c0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 103.156.72.0/24 | No route object for it. A route object for 103.156.72.0/23 with origin AS45291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45291 in the RIR database for the space. |
| Route object: none | 103.156.73.0/24 | No route object for it. A route object for 103.156.72.0/23 with origin AS45291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45291 in the RIR database for the space. |
| Route object: RIR | 203.153.216.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.153.217.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.153.218.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.153.219.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS45291:AS-PTI | PeeringDB names AS45291:AS-PTI; no IRR database read has it. |
Route objects not announced
Route objects with origin AS45291 whose prefix no peer sees AS45291 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.156.72.0/23 | RADB | Valid |
| 202.180.43.0/24 | NTTCOM, RADB | No ROA |
| 203.153.216.0/22 | NTTCOM | Valid |
| 203.153.216.0/23 | NTTCOM, RADB | Valid |
| 203.153.218.0/23 | NTTCOM, RADB | Valid |
| 203.253.218.0/23 | NTTCOM, RADB | No ROA |
| 203.253.218.0/24 | 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.