Autonomous system detail

AS1701

Not announced

No prefixes for this AS number were observed in the RouteViews RIB.

Summary

// analyst note
One combined routing observation at 2026-11-06 20:00 UTC across route-views2 and route-views6; AS270 is an observed AS_PATH neighbour, not a verified peer or upstream.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
—
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Low  ·  4 sources  ·  How this page is checked

AS1701 is an ASN whose registered organization and operating purpose are Unknown in the supplied evidence. A combined Route Views snapshot observed two IPv4 prefixes, an estimated 131,072 IPv4 addresses, and no IPv6 prefixes at 2026-11-06 20:00 UTC across route-views2 and route-views6. These are observations from that timestamp and collector pair, not a statement about current routing beyond the snapshot.

The same combined observation recorded one AS_PATH neighbour, AS270. This adjacency does not establish a verified peering session, upstream, or business relationship. The IANA entry places AS1701 in resource range 1–1876 and says it was assigned by ARIN; this identifies the allocating RIR, not an individual assignment record or present-day operator.

For identification, compare the two observed prefixes and their paths with a fresh routing snapshot and authoritative registry records that explicitly connect an organization to AS1701. Treat the absence of observed IPv6 routes as limited to this snapshot. The supplied evidence includes no operator-linked products, security findings, or reputation information, so it cannot support conclusions about use, legitimacy, or safety.

Routing exposure
Two IPv4 prefixes and zero IPv6 prefixes were observed in the combined snapshot at 2026-11-06 20:00 UTC from route-views2 and route-views6.
Observed adjacency
AS270 appears as the single sampled AS_PATH neighbour; this does not verify a commercial peer or upstream.
Triage
Identify any candidate operator through records that explicitly link it to AS1701, then compare the observed routes with a fresh snapshot before attributing them.
Operator
Unknown [Unknown] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv

Network & routing

Routing snapshot
2026-11-06 20:00 UTC; combined across route-views2 and route-views6 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
ASN
1701 [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
Allocating RIR
ARIN [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
IANA resource range
1–1876 [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
IPv4 prefixes observed
2 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
IPv4 address estimate
131072 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
IPv6 prefixes observed
0 [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
AS_PATH neighbours observed
1 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
Sampled AS_PATH neighbour
AS270 [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · as observed by RouteViews at 2026-11-06 · one collector view, not a global census
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.