bgpreport

Network · data from 2026-11-12

AS36063 ITSPEED-0001 - Arrownet, Inc.

Registry name: ITSPEED-0001 - Arrownet, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36063, 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.
2605:cf40::/32 No ROA Other origin only 631 99% 67
66.203.128.0/20 No ROA RIR databaseARIN 669 99% 67

AS-SET

AS36063 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 3 are in fix.csv.

  • ROA: none2
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none2605:cf40::/32No ROA covers it. Add a ROA for AS36063, maxLength 32.631 of 636
Route object: none2605:cf40::/32Route objects for it name AS15242. Add a route object with origin AS36063 in the RIR database for the space.631 of 636
ROA: none66.203.128.0/20No ROA covers it. Add a ROA for AS36063, maxLength 20.669 of 673

Route objects not announced

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