Network · data from 2026-11-12
AS55680 Universitas Atma Jaya Yogyakarta
Registry name: KSI-UAJY-AS-ID - Kantor Sistem Informasi Universitas Atma Jaya Yogyakarta, ID · PeeringDB
6IPv4 routes
100.0% RPKI valid · 100.0% with a route object
13IPv6 routes
100.0% RPKI valid · 7.7% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
12 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS55680, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS55680, 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.
| 2400:dbe0:2::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:11::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:21::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:22::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:23::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:24::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:25::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:31::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:32::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:33::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:34::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 2400:dbe0:41::/48 | Valid | Nonecovered by 2400:dbe0::/32 | 635 100% |
| 103.60.234.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 103.60.234.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.60.235.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 202.14.92.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 202.14.93.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2400:dbe0::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 202.14.92.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
AS-SET
AS55680'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 18 are in fix.csv.
- Route object: none12
- Route object: RIR6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2400:dbe0:2::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:11::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:21::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:22::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:23::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:24::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:25::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:31::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:32::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:33::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:34::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: none | 2400:dbe0:41::/48 | No route object for it. A route object for 2400:dbe0::/32 with origin AS55680 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55680 in the RIR database for the space. |
| Route object: RIR | 103.60.234.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.60.234.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.60.235.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.14.92.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.14.93.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2400:dbe0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS55680 is announced.
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.