bgpreport

Network · data from 2026-11-12

AS21530 FISERV-EPF-OMAHA - Fiserv Solutions, LLC

Registry name: FISERV-EPF-OMAHA - Fiserv Solutions, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21530, 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.
2620:10f:400c::/48 No ROA None 636 100% 67
2620:10f:400c::/47 No ROA None 635 100% 67
216.66.211.0/24 Valid Nonecovered by 216.66.210.0/23 673 100% 67
170.186.154.0/24 Valid RIR databaseARIN 673 100% 67
216.66.210.0/23 Valid RIR databaseARIN 673 100% 67

AS-SET

AS21530 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: none2
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2620:10f:400c::/48No ROA covers it. Add a ROA for AS21530, maxLength 48.636 of 636
Route object: none2620:10f:400c::/48No route object for it. Add a route object with origin AS21530 in the RIR database for the space.636 of 636
ROA: none2620:10f:400c::/47No ROA covers it. Add a ROA for AS21530, maxLength 47.635 of 636
Route object: none2620:10f:400c::/47No route object for it. Add a route object with origin AS21530 in the RIR database for the space.635 of 636
Route object: none216.66.211.0/24No route object for it. A route object for 216.66.210.0/23 with origin AS21530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21530 in the RIR database for the space.673 of 673

Route objects not announced

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

170.186.152.0/24ARINValid

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.