bgpreport

Network · data from 2026-11-12

AS25816 TOURO - Touro College

Registry name: TOURO - Touro College, US · not in PeeringDB

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

Announced routes

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

98.142.115.0/24 No ROA Other origin onlycovered by 98.142.114.0/23 673 100% 67
98.142.126.0/24 No ROA None 673 100% 67
98.142.127.0/24 No ROA None 673 100% 67
98.142.114.0/24 No ROA Nonecovered by 98.142.114.0/23 672 100% 67
98.142.120.0/24 No ROA Other IRR onlyRADB 673 100% 67
98.142.121.0/24 No ROA Other IRR onlyRADB 673 100% 67
107.181.27.0/24 No ROA Other IRR onlyRADB 672 100% 67
98.142.112.0/24 Valid RIR databaseARIN, RADB 673 100% 67
98.142.113.0/24 Valid RIR databaseARIN, RADB 673 100% 67
192.245.89.0/24 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

AS25816 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 21 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none98.142.115.0/24No ROA covers it. Add a ROA for AS25816, maxLength 24.673 of 673
Route object: none98.142.115.0/24Route objects for it name AS46887. A route object for 98.142.114.0/23 with origin AS25816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25816 in the RIR database for the space.673 of 673
ROA: none98.142.126.0/24No ROA covers it. Add a ROA for AS25816, maxLength 24.673 of 673
Route object: none98.142.126.0/24No route object for it. Add a route object with origin AS25816 in the RIR database for the space.673 of 673
ROA: none98.142.127.0/24No ROA covers it. Add a ROA for AS25816, maxLength 24.673 of 673
Route object: none98.142.127.0/24No route object for it. Add a route object with origin AS25816 in the RIR database for the space.673 of 673
ROA: none98.142.114.0/24No ROA covers it. Add a ROA for AS25816, maxLength 24.672 of 673
Route object: none98.142.114.0/24No route object for it. A route object for 98.142.114.0/23 with origin AS25816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25816 in the RIR database for the space.672 of 673
ROA: none98.142.120.0/24No ROA covers it. Add a ROA for AS25816, maxLength 24.673 of 673
Route object: RIR98.142.120.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none98.142.121.0/24No ROA covers it. Add a ROA for AS25816, maxLength 24.673 of 673
Route object: RIR98.142.121.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none107.181.27.0/24No ROA covers it. Add a ROA for AS25816, maxLength 24.672 of 673
Route object: RIR107.181.27.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

98.142.112.0/23ARINNo ROA
98.142.114.0/23RADBNo ROA
98.142.120.0/23ARINNo ROA
98.142.124.0/23ARINNo ROA
104.254.44.0/24ARIN, RADBValid
104.254.45.0/24ARIN, RADBValid
104.254.46.0/24ARIN, RADBValid

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.