bgpreport

Network · data from 2026-11-12

AS54294 ECC-LINK-001 - ERIE COMMUNITY COLLEGE

Registry name: ECC-LINK-001 - ERIE COMMUNITY COLLEGE, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54294, 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.29.6.0/24 No ROA Other IRR onlyRADB 672 100% 68
199.29.7.0/24 No ROA Other IRR onlyRADB 672 100% 68
199.29.8.0/24 No ROA Other IRR onlyRADB 672 100% 68
192.188.230.0/24 Valid RIR databaseARIN, RADB 672 100% 68
192.188.231.0/24 Valid RIR databaseARIN, RADB 672 100% 68
192.188.232.0/24 Valid RIR databaseARIN, RADB 672 100% 68
198.99.88.0/24 Valid RIR databaseARIN, RADB 672 100% 68
198.99.89.0/24 Valid RIR databaseARIN, RADB 672 100% 68
198.99.90.0/24 Valid RIR databaseARIN, RADB 672 100% 68

AS-SET

AS54294 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 6 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none199.29.6.0/24No ROA covers it. Add a ROA for AS54294, maxLength 24.672 of 673
Route object: RIR199.29.6.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.29.7.0/24No ROA covers it. Add a ROA for AS54294, maxLength 24.672 of 673
Route object: RIR199.29.7.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.29.8.0/24No ROA covers it. Add a ROA for AS54294, maxLength 24.672 of 673
Route object: RIR199.29.8.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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