Network · data from 2026-11-12
AS45735 Uninet Media Sakti AS45735
Registry name: UNINET-NAP-AS-ID - PT. UNINET MEDIA SAKTI, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45735, 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.151.162.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 2406:1b40::/32 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS45735: AS45735:AS-UNINETMEDIASAKTI. 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 (AS45735 isn't in the set, or no route object for AS45735 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 | AS45735 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS45735:AS-UNINETMEDIASAKTI | 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 24 are in fix.csv.
- AS-SET: not found1
- Route object: not announced23
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: not found | AS45735:AS-UNINETMEDIASAKTI | PeeringDB names AS45735:AS-UNINETMEDIASAKTI; no IRR database read has it. |
Route objects not announced
Route objects with origin AS45735 whose prefix no peer sees AS45735 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.151.162.0/24 | APNIC | Valid |
| 103.151.163.0/24 | APNIC | Valid |
| 111.221.40.0/22 | NTTCOM | No ROA |
| 111.221.40.0/23 | NTTCOM | No ROA |
| 111.221.40.0/24 | NTTCOM | No ROA |
| 111.221.41.0/24 | NTTCOM | No ROA |
| 111.221.42.0/23 | NTTCOM | No ROA |
| 111.221.42.0/24 | NTTCOM | No ROA |
| 111.221.43.0/24 | NTTCOM | No ROA |
| 202.145.0.0/20 | NTTCOM | No ROA |
| 202.145.0.0/21 | NTTCOM | No ROA |
| 202.145.4.0/22 | NTTCOM | No ROA |
| 203.161.16.0/20 | NTTCOM | No ROA |
| 203.161.16.0/21 | NTTCOM | No ROA |
| 203.161.16.0/22 | NTTCOM | No ROA |
| 203.161.16.0/23 | NTTCOM | No ROA |
| 203.161.18.0/23 | NTTCOM | No ROA |
| 203.161.20.0/22 | NTTCOM | No ROA |
| 203.161.20.0/23 | NTTCOM | No ROA |
| 203.161.22.0/23 | NTTCOM | No ROA |
| 203.161.23.0/24 | NTTCOM | No ROA |
| 2001:470:1f5::/48 | ARIN | Invalid: origin |
| 2001:470:3c3::/48 | ARIN | Invalid: origin |
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.