bgpreport

Network · data from 2026-11-12

AS399604 ES10-08873-01 - EXL SERVICE.COM, LLC

Registry name: ES10-08873-01 - EXL SERVICE.COM, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399604, 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.
63.234.186.0/24 No ROA None 673 100% 67
63.239.194.0/24 No ROA None 673 100% 67
65.122.132.0/24 No ROA None 673 100% 67
207.67.53.32/27 No ROA None 2 0%low visibility 2
12.111.79.0/24 No ROA None 1 0%low visibility 2
12.227.225.0/24 No ROA Other IRR onlyRADB 673 100% 67
12.70.27.0/24 No ROA Other IRR onlyRADB 672 100% 67
12.130.80.0/24 No ROA Other IRR onlyRADB 672 100% 67
63.240.62.0/24 No ROA Other IRR onlyRADB 672 100% 67
199.106.88.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS399604 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none5
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none63.234.186.0/24No ROA covers it. Add a ROA for AS399604, maxLength 24.673 of 673
Route object: none63.234.186.0/24No route object for it. Add a route object with origin AS399604 in the RIR database for the space.673 of 673
ROA: none63.239.194.0/24No ROA covers it. Add a ROA for AS399604, maxLength 24.673 of 673
Route object: none63.239.194.0/24No route object for it. Add a route object with origin AS399604 in the RIR database for the space.673 of 673
ROA: none65.122.132.0/24No ROA covers it. Add a ROA for AS399604, maxLength 24.673 of 673
Route object: none65.122.132.0/24No route object for it. Add a route object with origin AS399604 in the RIR database for the space.673 of 673
ROA: none207.67.53.32/27No ROA covers it. Add a ROA for AS399604, maxLength 27.2 of 673
Route object: none207.67.53.32/27No route object for it. Add a route object with origin AS399604 in the RIR database for the space.2 of 673
ROA: none12.111.79.0/24No ROA covers it. Add a ROA for AS399604, maxLength 24.1 of 673
Route object: none12.111.79.0/24No route object for it. Add a route object with origin AS399604 in the RIR database for the space.1 of 673
ROA: none12.227.225.0/24No ROA covers it. Add a ROA for AS399604, maxLength 24.673 of 673
Route object: RIR12.227.225.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none12.70.27.0/24No ROA covers it. Add a ROA for AS399604, maxLength 24.672 of 673
Route object: RIR12.70.27.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none12.130.80.0/24No ROA covers it. Add a ROA for AS399604, maxLength 24.672 of 673
Route object: RIR12.130.80.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none63.240.62.0/24No ROA covers it. Add a ROA for AS399604, maxLength 24.672 of 673
Route object: RIR63.240.62.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.106.88.0/24No ROA covers it. Add a ROA for AS399604, maxLength 24.672 of 673
Route object: RIR199.106.88.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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