bgpreport

Network · data from 2026-11-12

AS22220 EACOMARTS - Electronic Arts, Inc.

Registry name: EACOMARTS - Electronic Arts, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22220, 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.132.0/22 No ROA Other origin only 673 100% 67
159.153.49.0/24 No ROA Nonecovered by 159.153.48.0/21 672 100% 67
159.153.73.0/24 No ROA None 670 100% 67
159.153.51.0/24 No ROA Nonecovered by 159.153.48.0/21 669 99% 67
159.153.38.0/24 No ROA None 1 0%low visibility 1
159.153.48.0/21 No ROA Other IRR onlyRADB 673 100% 67
159.153.70.0/23 No ROA Other IRR onlyRADB 673 100% 67
159.153.84.0/22 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS22220 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 17 are in fix.csv.

  • ROA: none8
  • Route object: none5
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none159.153.132.0/22No ROA covers it. Add a ROA for AS22220, maxLength 22.673 of 673
Route object: none159.153.132.0/22Route objects for it name AS14891. Add a route object with origin AS22220 in the RIR database for the space.673 of 673
ROA: none159.153.49.0/24No ROA covers it. Add a ROA for AS22220, maxLength 24.672 of 673
Route object: none159.153.49.0/24No route object for it. A route object for 159.153.48.0/21 with origin AS22220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22220 in the RIR database for the space.672 of 673
ROA: none159.153.73.0/24No ROA covers it. Add a ROA for AS22220, maxLength 24.670 of 673
Route object: none159.153.73.0/24No route object for it. Add a route object with origin AS22220 in the RIR database for the space.670 of 673
ROA: none159.153.51.0/24No ROA covers it. Add a ROA for AS22220, maxLength 24.669 of 673
Route object: none159.153.51.0/24No route object for it. A route object for 159.153.48.0/21 with origin AS22220 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22220 in the RIR database for the space.669 of 673
ROA: none159.153.38.0/24No ROA covers it. Add a ROA for AS22220, maxLength 24.1 of 673
Route object: none159.153.38.0/24No route object for it. Add a route object with origin AS22220 in the RIR database for the space.1 of 673
ROA: none159.153.48.0/21No ROA covers it. Add a ROA for AS22220, maxLength 21.673 of 673
Route object: RIR159.153.48.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none159.153.70.0/23No ROA covers it. Add a ROA for AS22220, maxLength 23.673 of 673
Route object: RIR159.153.70.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none159.153.84.0/22No ROA covers it. Add a ROA for AS22220, maxLength 22.673 of 673
Route object: RIR159.153.84.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

2620:11e:3040::/44RADBNo ROA

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.