bgpreport

Network · data from 2026-11-12

AS24614 SAKARYA-NET-AS Sakarya University

Registry name: SAKARYA-NET-AS Sakarya University, TR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24614, 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.
194.27.188.0/22 Valid None 671 100% 66
194.27.196.0/22 Valid None 671 100% 66
194.27.238.0/23 Valid Other origin only 671 100% 67
194.27.240.0/20 Valid Other origin only 671 100% 67
193.140.252.0/23 Valid RIR databaseRIPE 671 100% 67
193.255.252.0/22 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS24614 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 4 are in fix.csv.

  • Route object: none4
ChangePrefix or setDetailFull-table peers
Route object: none194.27.188.0/22No route object for it. Add a route object with origin AS24614 in the RIR database for the space.671 of 673
Route object: none194.27.196.0/22No route object for it. Add a route object with origin AS24614 in the RIR database for the space.671 of 673
Route object: none194.27.238.0/23Route objects for it name AS8517. Add a route object with origin AS24614 in the RIR database for the space.671 of 673
Route object: none194.27.240.0/20Route objects for it name AS8517. Add a route object with origin AS24614 in the RIR database for the space.671 of 673

Route objects not announced

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