bgpreport

Network · data from 2026-11-12

AS13713 ARCOT - Avago Technologies U.S. Inc.

Registry name: ARCOT - Avago Technologies U.S. Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13713, 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.
130.119.3.0/24 No ROA None 673 100% 67
209.185.8.0/24 No ROA None 672 100% 67
216.18.146.0/24 No ROA Other IRR onlyRADB 673 100% 70
199.101.152.0/24 No ROA RIR databaseARIN 673 100% 70
199.101.153.0/24 No ROA RIR databaseARIN 673 100% 70
199.101.154.0/24 No ROA RIR databaseARIN 673 100% 70
216.18.144.0/24 No ROA RIR databaseARIN 672 100% 67
216.18.145.0/24 No ROA RIR databaseARIN 672 100% 67
199.101.155.0/24 No ROA RIR databaseARIN 671 100% 67
144.49.60.0/24 Valid RIR databaseARIN 673 100% 70
144.49.61.0/24 Valid RIR databaseARIN 673 100% 70
144.49.62.0/24 Valid RIR databaseARIN 673 100% 70

AS-SET

AS13713 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 12 are in fix.csv.

  • ROA: none9
  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none130.119.3.0/24No ROA covers it. Add a ROA for AS13713, maxLength 24.673 of 673
Route object: none130.119.3.0/24No route object for it. Add a route object with origin AS13713 in the RIR database for the space.673 of 673
ROA: none209.185.8.0/24No ROA covers it. Add a ROA for AS13713, maxLength 24.672 of 673
Route object: none209.185.8.0/24No route object for it. Add a route object with origin AS13713 in the RIR database for the space.672 of 673
ROA: none216.18.146.0/24No ROA covers it. Add a ROA for AS13713, maxLength 24.673 of 673
Route object: RIR216.18.146.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.101.152.0/24No ROA covers it. Add a ROA for AS13713, maxLength 24.673 of 673
ROA: none199.101.153.0/24No ROA covers it. Add a ROA for AS13713, maxLength 24.673 of 673
ROA: none199.101.154.0/24No ROA covers it. Add a ROA for AS13713, maxLength 24.673 of 673
ROA: none216.18.144.0/24No ROA covers it. Add a ROA for AS13713, maxLength 24.672 of 673
ROA: none216.18.145.0/24No ROA covers it. Add a ROA for AS13713, maxLength 24.672 of 673
ROA: none199.101.155.0/24No ROA covers it. Add a ROA for AS13713, maxLength 24.671 of 673

Route objects not announced

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