bgpreport

Network · data from 2026-11-12

AS31689 EMU-AS Eastern Mediterranean University

Registry name: EMU-AS Eastern Mediterranean University, TR · not in PeeringDB

20IPv4 routes 100.0% RPKI valid · 75.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS31689, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS31689, 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.
193.140.45.0/24 Valid Nonecovered by 193.140.40.0/21 673 100% 67
194.27.76.0/24 Valid Nonecovered by 194.27.76.0/22 673 100% 67
194.27.77.0/24 Valid Nonecovered by 194.27.76.0/22 673 100% 67
194.27.78.0/24 Valid Nonecovered by 194.27.76.0/22 673 100% 67
194.27.79.0/24 Valid Nonecovered by 194.27.76.0/22 673 100% 67
193.140.40.0/21 Valid RIR databaseRIPE 673 100% 68
193.140.172.0/22 Valid RIR databaseRIPE 673 100% 68
194.27.76.0/22 Valid RIR databaseRIPE 673 100% 68
193.140.46.0/24 Valid RIR databaseRIPE 672 100% 68
193.140.47.0/24 Valid RIR databaseRIPE 672 100% 68
193.140.40.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.41.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.42.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.43.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.44.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.172.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.173.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.174.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.175.0/24 Valid RIR databaseRIPE 671 100% 67
194.27.73.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS31689 isn't in PeeringDB, where networks name their 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 5 are in fix.csv.

  • Route object: none5
ChangePrefix or setDetailFull-table peers
Route object: none193.140.45.0/24No route object for it. A route object for 193.140.40.0/21 with origin AS31689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31689 in the RIR database for the space.673 of 673
Route object: none194.27.76.0/24No route object for it. A route object for 194.27.76.0/22 with origin AS31689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31689 in the RIR database for the space.673 of 673
Route object: none194.27.77.0/24No route object for it. A route object for 194.27.76.0/22 with origin AS31689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31689 in the RIR database for the space.673 of 673
Route object: none194.27.78.0/24No route object for it. A route object for 194.27.76.0/22 with origin AS31689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31689 in the RIR database for the space.673 of 673
Route object: none194.27.79.0/24No route object for it. A route object for 194.27.76.0/22 with origin AS31689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31689 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS31689 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.