Network · data from 2026-11-12
AS133827 Universitas Islam Indonesia
Registry name: IDNIC-UII-AS-ID - UNIVERSITAS ISLAM INDONESIA, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133827, 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.55.139.0/24 | Valid | RIR databaseALTDB, APNIC, NTTCOM, RADB | 673 100% |
| 103.95.6.0/23 | Valid | RIR databaseALTDB, APNIC, NTTCOM, RADB | 673 100% |
| 103.95.6.0/24 | Valid | RIR databaseALTDB, APNIC, NTTCOM, RADB | 673 100% |
| 103.220.113.0/24 | Valid | RIR databaseALTDB, APNIC, NTTCOM, RADB | 673 100% |
| 2404:a640::/32 | Valid | RIR databaseALTDB, APNIC, RADB | 635 100% |
| 2404:a640:113::/48 | Valid | RIR databaseALTDB, APNIC, RADB | 635 100% |
| 2404:a640:139::/48 | Valid | RIR databaseALTDB, APNIC, RADB | 635 100% |
| 2404:a640:956::/48 | Valid | RIR databaseALTDB, APNIC, RADB | 635 100% |
| 2404:a640:957::/48 | Valid | RIR databaseALTDB, APNIC, RADB | 635 100% |
| 103.95.7.0/24 | Valid | RIR databaseALTDB, APNIC, NTTCOM, RADB | 2 0%low visibility |
AS-SET
AS133827's PeeringDB record names no AS-SET.
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 3 are in fix.csv.
- Route object: not announced3
Route objects not announced
Route objects with origin AS133827 whose prefix no peer sees AS133827 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.55.138.0/24 | RADB | No ROA |
| 2001:df2:3e00::/48 | RADB | No ROA |
| 2404:a640:62::/48 | 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.