bgpreport

Network · data from 2026-11-12

AS57052 BIOWAREONLINEEU1 ELECTRONIC ARTS IRELAND LIMITED

Registry name: BIOWAREONLINEEU1 ELECTRONIC ARTS IRELAND LIMITED, IE · not in PeeringDB

9IPv4 routes 0.0% RPKI valid · 66.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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 AS57052, seen from no peer

Announced routes

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

159.153.124.0/22 No ROA Other origin only 673 100% 67
159.153.160.0/21 No ROA Other origin only 673 100% 67
159.153.38.0/24 No ROA Nonecovered by 159.153.32.0/21 669 99% 67
159.153.32.0/21 No ROA Other IRR onlyRADB 673 100% 67
159.153.58.0/23 No ROA Other IRR onlyRADB 673 100% 67
159.153.62.0/23 No ROA Other IRR onlyRADB 673 100% 67
159.153.72.0/21 No ROA Other IRR onlyRADB 673 100% 67
159.153.80.0/22 No ROA Other IRR onlyRADB 673 100% 67
159.153.224.0/21 No ROA Other IRR onlyRADB 673 100% 67
2a00:ad40:10::/44 Valid Other IRR onlyRADB 634 100% 68

AS-SET

AS57052 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 19 are in fix.csv.

  • ROA: none9
  • Route object: none3
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none159.153.124.0/22No ROA covers it. Add a ROA for AS57052, maxLength 22.673 of 673
Route object: none159.153.124.0/22Route objects for it name AS7171. Add a route object with origin AS57052 in the RIR database for the space.673 of 673
ROA: none159.153.160.0/21No ROA covers it. Add a ROA for AS57052, maxLength 21.673 of 673
Route object: none159.153.160.0/21Route objects for it name AS7171. Add a route object with origin AS57052 in the RIR database for the space.673 of 673
ROA: none159.153.38.0/24No ROA covers it. Add a ROA for AS57052, maxLength 24.669 of 673
Route object: none159.153.38.0/24No route object for it. A route object for 159.153.32.0/21 with origin AS57052 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57052 in the RIR database for the space.669 of 673
ROA: none159.153.32.0/21No ROA covers it. Add a ROA for AS57052, maxLength 21.673 of 673
Route object: RIR159.153.32.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none159.153.58.0/23No ROA covers it. Add a ROA for AS57052, maxLength 23.673 of 673
Route object: RIR159.153.58.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none159.153.62.0/23No ROA covers it. Add a ROA for AS57052, maxLength 23.673 of 673
Route object: RIR159.153.62.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none159.153.72.0/21No ROA covers it. Add a ROA for AS57052, maxLength 21.673 of 673
Route object: RIR159.153.72.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none159.153.80.0/22No ROA covers it. Add a ROA for AS57052, maxLength 22.673 of 673
Route object: RIR159.153.80.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none159.153.224.0/21No ROA covers it. Add a ROA for AS57052, maxLength 21.673 of 673
Route object: RIR159.153.224.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2a00:ad40:10::/44Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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