bgpreport

Network · data from 2026-11-12

AS10558 BIOLA---BIOLA-UNIVERSITY - Biola University, Inc.

Registry name: BIOLA---BIOLA-UNIVERSITY - Biola University, Inc., US · 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
2Route objects not announced registered with origin AS10558, seen from no peer

Announced routes

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

199.19.144.0/24 Valid Other origin onlycovered by 199.19.144.0/23 671 100% 67
199.19.145.0/24 Valid Nonecovered by 199.19.144.0/23 671 100% 67
199.19.146.0/24 Valid Nonecovered by 199.19.146.0/23 671 100% 67
199.19.147.0/24 Valid Nonecovered by 199.19.146.0/23 671 100% 67
199.19.144.0/23 Valid Other IRR onlyRADB 672 100% 67
199.19.146.0/23 Valid Other IRR onlyRADB 672 100% 67

AS-SET

AS10558 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 8 are in fix.csv.

  • Route object: none4
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none199.19.144.0/24Route objects for it name AS8075. A route object for 199.19.144.0/23 with origin AS10558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10558 in the RIR database for the space.671 of 673
Route object: none199.19.145.0/24No route object for it. A route object for 199.19.144.0/23 with origin AS10558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10558 in the RIR database for the space.671 of 673
Route object: none199.19.146.0/24No route object for it. A route object for 199.19.146.0/23 with origin AS10558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10558 in the RIR database for the space.671 of 673
Route object: none199.19.147.0/24No route object for it. A route object for 199.19.146.0/23 with origin AS10558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10558 in the RIR database for the space.671 of 673
Route object: RIR199.19.144.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR199.19.146.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

192.34.232.0/24RADBNo ROA
199.19.144.0/22ARINValid

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.