Network · data from 2026-11-12
AS152082 Infonusa Teknologi Telekomunikasi Nusantara
Registry name: INFONUSANET-AS-ID - PT Infonusa Teknologi Telekomunikasi Nusantara, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS152082, 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.80.98.0/24 | Valid | Nonecovered by 103.80.98.0/23 | 673 100% |
| 103.80.99.0/24 | Valid | Nonecovered by 103.80.98.0/23 | 673 100% |
| 157.10.88.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 157.10.89.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 2001:df3:5bc0::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 103.80.98.0/23 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS152082: AS152082:AS-INFONUSANET-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 (AS152082 isn't in the set, or no route object for AS152082 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 | AS152082 in it | Not covered |
|---|---|---|---|---|---|
| AS152082:AS-INFONUSANET-ID | 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 6 are in fix.csv.
- Route object: none2
- Route object: RIR3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.80.98.0/24 | No route object for it. A route object for 103.80.98.0/23 with origin AS152082 covers it (filters allowing more-specifics accept it). Add a route object with origin AS152082 in the RIR database for the space. |
| Route object: none | 103.80.99.0/24 | No route object for it. A route object for 103.80.98.0/23 with origin AS152082 covers it (filters allowing more-specifics accept it). Add a route object with origin AS152082 in the RIR database for the space. |
| Route object: RIR | 157.10.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 157.10.89.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:df3:5bc0::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS152082 whose prefix no peer sees AS152082 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 157.10.88.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.