Autonomous system detail

AS1699

Not announced

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

Summary

// analyst note
Routing counts and three AS_PATH neighbors are from the combined route-views2 and route-views6 observation at 2026-11-06T20:00:00Z; this snapshot does not identify an operator.
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

AS1699 has no identified operator in the supplied evidence. In the combined Route Views snapshot observed at 2026-11-06 20:00 UTC by route-views2 and route-views6, it announced 43 IPv4 prefixes, representing an estimated 19,456 IPv4 addresses, and no IPv6 prefixes. This is evidence of routing activity at that snapshot, not a statement about its status at other times.

The same combined observation recorded three AS_PATH neighbor ASNs: AS701, AS702, and AS703. These adjacencies do not establish verified peering, upstream, customer, or provider relationships. The supplied IANA records place AS1699 in the 1–1876 resource block assigned by ARIN; that identifies the allocating RIR, not an individual assignment or present-day organization.

For identification or incident triage, compare the specific prefix and observation time against current routing data and the relevant route origin records. Check whether the observed origin and path match the route under investigation, and corroborate any proposed operator attribution with direct organizational evidence. The supplied snapshot and registry block do not establish ownership, location, legitimacy, or security status.

Routing observation
Combined snapshot at 2026-11-06 20:00 UTC recorded 43 IPv4 prefixes, an estimate of 19,456 IPv4 addresses, and zero IPv6 prefixes.
AS_PATH neighbors
AS701, AS702, and AS703 were observed; these are not verified commercial relationships.
Triage
Match the relevant prefix and timestamp against current routing and origin records; the supplied evidence does not identify an operator or establish a security finding.
Operator identity
Unknown [Unknown] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
ASN
1699 [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
IPv4 prefixes
43 in the combined observation at 2026-11-06T20:00:00Z [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
IPv4 address estimate
19456 in the combined observation at 2026-11-06T20:00:00Z [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
IPv6 prefixes
0 in the combined observation at 2026-11-06T20:00:00Z [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
Observed AS_PATH neighbors
AS701, AS702, AS703; not verified peers or commercial relationships [Confirmed] — https://archive.routeviews.org/route-views2/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.