bgpreport

Network · data from 2026-11-12

AS6932 EBSCOPUB - EBSCO Publishing

Registry name: EBSCOPUB - EBSCO Publishing, US · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 20.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No 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 AS6932, seen from no peer

Announced routes

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

140.234.250.0/24 No ROA Nonecovered by 140.234.0.0/16 673 100% 67
140.234.251.0/24 No ROA Nonecovered by 140.234.0.0/16 673 100% 67
140.234.252.0/24 No ROA Nonecovered by 140.234.0.0/16 673 100% 67
140.234.254.0/24 No ROA Nonecovered by 140.234.0.0/16 673 100% 67
140.234.0.0/16 No ROA RIR databaseARIN 673 100% 67

AS-SET

AS6932 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.

  • ROA: none5
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: none140.234.250.0/24No ROA covers it. Add a ROA for AS6932, maxLength 24.673 of 673
Route object: none140.234.250.0/24No route object for it. A route object for 140.234.0.0/16 with origin AS6932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6932 in the RIR database for the space.673 of 673
ROA: none140.234.251.0/24No ROA covers it. Add a ROA for AS6932, maxLength 24.673 of 673
Route object: none140.234.251.0/24No route object for it. A route object for 140.234.0.0/16 with origin AS6932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6932 in the RIR database for the space.673 of 673
ROA: none140.234.252.0/24No ROA covers it. Add a ROA for AS6932, maxLength 24.673 of 673
Route object: none140.234.252.0/24No route object for it. A route object for 140.234.0.0/16 with origin AS6932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6932 in the RIR database for the space.673 of 673
ROA: none140.234.254.0/24No ROA covers it. Add a ROA for AS6932, maxLength 24.673 of 673
Route object: none140.234.254.0/24No route object for it. A route object for 140.234.0.0/16 with origin AS6932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6932 in the RIR database for the space.673 of 673
ROA: none140.234.0.0/16No ROA covers it. Add a ROA for AS6932, maxLength 16.673 of 673

Route objects not announced

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