bgpreport

Network · data from 2026-11-12

AS8456 ASBOUN Bogazici University

Registry name: ASBOUN Bogazici University, TR · not in PeeringDB

27IPv4 routes 100.0% RPKI valid · 85.2% 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
5Route objects not announced registered with origin AS8456, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS8456, 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.

161.9.147.0/24 Valid Nonecovered by 161.9.144.0/21 673 100% 67
193.140.201.0/24 Valid Nonecovered by 193.140.200.0/22 673 100% 67
193.140.204.0/24 Valid Nonecovered by 193.140.204.0/22 673 100% 67
193.255.30.0/24 Valid Other origin only 672 100% 67
79.123.176.0/23 Valid RIR databaseRIPE 672 100% 67
79.123.178.0/24 Valid RIR databaseRIPE 672 100% 67
79.123.179.0/24 Valid RIR databaseRIPE 672 100% 67
79.123.180.0/24 Valid RIR databaseRIPE 672 100% 67
79.123.181.0/24 Valid RIR databaseRIPE 672 100% 67
79.123.182.0/24 Valid RIR databaseRIPE 672 100% 67
79.123.183.0/24 Valid RIR databaseRIPE 672 100% 67
95.183.228.0/24 Valid RIR databaseRIPE 672 100% 67
161.9.144.0/21 Valid RIR databaseRIPE 672 100% 67
193.140.193.0/24 Valid RIR databaseRIPE 672 100% 67
193.140.194.0/24 Valid RIR databaseRIPE 672 100% 67
193.140.195.0/24 Valid RIR databaseRIPE 672 100% 67
193.140.196.0/22 Valid RIR databaseRIPE 672 100% 67
193.140.196.0/24 Valid RIR databaseRIPE 672 100% 67
193.140.200.0/22 Valid RIR databaseRIPE 672 100% 67
193.140.203.0/24 Valid RIR databaseRIPE 672 100% 67
193.140.204.0/22 Valid RIR databaseRIPE 672 100% 67
193.140.208.0/21 Valid RIR databaseRIPE 672 100% 67
161.9.151.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.192.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.199.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.200.0/24 Valid RIR databaseRIPE 671 100% 67
193.140.213.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS8456 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 9 are in fix.csv.

  • Route object: none4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none161.9.147.0/24No route object for it. A route object for 161.9.144.0/21 with origin AS8456 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8456 in the RIR database for the space.673 of 673
Route object: none193.140.201.0/24No route object for it. A route object for 193.140.200.0/22 with origin AS8456 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8456 in the RIR database for the space.673 of 673
Route object: none193.140.204.0/24No route object for it. A route object for 193.140.204.0/22 with origin AS8456 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8456 in the RIR database for the space.673 of 673
Route object: none193.255.30.0/24Route objects for it name AS8517. Add a route object with origin AS8456 in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS8456 whose prefix no peer sees AS8456 announce. Many are kept on purpose (backup routes, space announced only in some places).

79.123.176.0/21RIPEInvalid: origin
193.140.192.0/20RIPEInvalid: origin
208.218.43.0/24RIPE-NONAUTHNo ROA
208.218.46.0/24RIPE-NONAUTHNo ROA
208.225.48.0/20RIPE-NONAUTHNo ROA

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.