bgpreport

Network · data from 2026-11-12

AS30528 EiCatalyst Networks

Registry name: EICAT - E. I. Catalyst, CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30528, 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.
205.189.139.0/24 No ROA Other IRR onlyALTDB, BBOI 671 100% 68
66.96.16.0/20 Valid RIR databaseARIN, BBOI 671 100% 68
72.0.64.0/20 Valid RIR databaseARIN, BBOI, RADB 671 100% 68
2001:1928::/32 Valid RIR databaseARIN 634 100% 69

AS-SET

AS30528's PeeringDB record names no 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 15 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none205.189.139.0/24No ROA covers it. Add a ROA for AS30528, maxLength 24.671 of 673
Route object: RIR205.189.139.0/24Route object only in ALTDB, BBOI. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

66.246.132.0/23RADBNo ROA
66.246.136.0/23RADBNo ROA
66.246.150.0/23RADBNo ROA
198.73.212.0/22RADBNo ROA
199.166.32.0/23RADBNo ROA
204.15.184.0/21ARINValid
205.189.97.0/24RADBNo ROA
205.189.98.0/24RADBNo ROA
205.189.131.0/24RADBNo ROA
205.233.48.0/21BBOINo ROA
205.233.214.0/24RADBNo ROA
206.130.36.0/24RADBNo ROA
209.222.48.0/20ARINValid

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.