Autonomous system detail

AS1667

Not announced

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

Summary

// analyst note
IANA identifies AS1667 as within the block assigned by ARIN. Organization, country, network type, and operator are not established by supplied evidence.
// security note
The combined RouteViews observation at 2026-11-06 20:00 UTC showed zero IPv4 and IPv6 prefixes and zero AS_PATH neighbours.
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  ·  3 sources  ·  How this page is checked

AS1667 is an ASN in the IANA block assigned by ARIN; the supplied registry evidence does not identify an organization, country, or network type. Its live-routing snapshot showed zero IPv4 and zero IPv6 prefixes, zero represented IPv4 addresses, and zero observed AS_PATH neighbours.

Those counts are the combined observation from RouteViews route-views2 and route-views6 at 2026-11-06 20:00 UTC. They describe that snapshot only. No prefixes or neighbours observed there does not establish that the ASN is inactive, unassigned to an individual entity, or absent from other routing views or times.

For identification, compare the ASN and any candidate prefix against dated routing data and an authoritative organization record that explicitly links the entity to AS1667. If investigating a particular address, check its current origin and route history independently; this snapshot provides no prefix to attribute to the ASN. The evidence supplied here does not support a vendor identity or a security assessment.

Identity
IANA places AS1667 in the block assigned by ARIN; an organization is not identified. [Confirmed]
Routing snapshot
Zero IPv4 and IPv6 prefixes, zero IPv4 addresses represented, and zero AS_PATH neighbours in the combined RouteViews observation at 2026-11-06 20:00 UTC. [Confirmed]
Triage
Treat the zero counts as snapshot-scoped; seek an explicit ASN-to-organization record and compare independent, dated route observations for identification. [Confirmed]
RIR
ARIN [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
Observation scope
combined RouteViews snapshot at 2026-11-06T20:00:00.000Z; route-views2, route-views6 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
ASN
1667 [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
IPv4 prefixes
0 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
IPv4 address estimate
0 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
IPv6 prefixes
0 [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
Observed AS_PATH neighbours
0 [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.