bgpreport

Network · data from 2026-11-12

AS30864 Elavon-Financial-Services-DAC_AS Elavon Financial Services DAC

Registry name: Elavon-Financial-Services-DAC_AS Elavon Financial Services DAC, IE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30864, 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.
195.137.204.0/24 No ROA Nonecovered by 195.137.204.0/23 672 100% 67
195.137.205.0/24 No ROA Nonecovered by 195.137.204.0/23 672 100% 67
213.225.230.0/24 No ROA Nonecovered by 213.225.228.0/22 672 100% 67
195.245.90.0/24 No ROA Other IRR onlyRADB 672 100% 67
195.245.91.0/24 No ROA Other IRR onlyRADB 672 100% 67
213.225.228.0/22 No ROA Other IRR onlyRADB 672 100% 67
195.137.204.0/23 No ROA RIR databaseRIPE 673 100% 66
195.245.90.0/23 No ROA RIR databaseRIPE 673 100% 67
195.170.169.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67

AS-SET

AS30864 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 15 are in fix.csv.

  • ROA: none9
  • Route object: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none195.137.204.0/24No ROA covers it. Add a ROA for AS30864, maxLength 24.672 of 673
Route object: none195.137.204.0/24No route object for it. A route object for 195.137.204.0/23 with origin AS30864 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30864 in the RIR database for the space.672 of 673
ROA: none195.137.205.0/24No ROA covers it. Add a ROA for AS30864, maxLength 24.672 of 673
Route object: none195.137.205.0/24No route object for it. A route object for 195.137.204.0/23 with origin AS30864 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30864 in the RIR database for the space.672 of 673
ROA: none213.225.230.0/24No ROA covers it. Add a ROA for AS30864, maxLength 24.672 of 673
Route object: none213.225.230.0/24No route object for it. A route object for 213.225.228.0/22 with origin AS30864 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30864 in the RIR database for the space.672 of 673
ROA: none195.245.90.0/24No ROA covers it. Add a ROA for AS30864, maxLength 24.672 of 673
Route object: RIR195.245.90.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none195.245.91.0/24No ROA covers it. Add a ROA for AS30864, maxLength 24.672 of 673
Route object: RIR195.245.91.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none213.225.228.0/22No ROA covers it. Add a ROA for AS30864, maxLength 22.672 of 673
Route object: RIR213.225.228.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none195.137.204.0/23No ROA covers it. Add a ROA for AS30864, maxLength 23.673 of 673
ROA: none195.245.90.0/23No ROA covers it. Add a ROA for AS30864, maxLength 23.673 of 673
ROA: none195.170.169.0/24No ROA covers it. Add a ROA for AS30864, maxLength 24.672 of 673

Route objects not announced

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