Autonomous system detail

AS1627

Not announced

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

Summary

// analyst note
One combined Route Views observation at 2026-11-06 20:00 UTC; AS_PATH adjacency does not establish a commercial relationship.
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

AS1627 is an ASN with one IPv4 prefix and no IPv6 prefixes observed in a combined Route Views snapshot; its operator and registration details beyond the allocating RIR are unknown. This is a snapshot finding, not proof that the ASN is dormant or inactive.

At 2026-11-06 20:00 UTC, the combined observation from route-views2 and route-views6 contained one IPv4 prefix, an estimated 256 IPv4 addresses, zero IPv6 prefixes, and one observed AS_PATH neighbour: AS22773. The neighbour is a routing-path adjacency only; these data do not establish a verified peer, upstream, customer, or provider relationship.

IANA lists ASN 1627 within resource block 1–1876 as assigned by ARIN. That identifies the allocating RIR for the block, not an individual assignment record or the ASN’s present operator. The supplied evidence does not identify an organization, country, network type, website, or security status.

For triage, compare the prefix and origin in a current route view and check authoritative registry records before attributing the ASN to an organization. Treat AS22773 only as a lead for examining the observed path. Do not infer ownership, traffic prevalence, legitimacy, or safety from this single-time snapshot.

Observed routing
One IPv4 prefix and zero IPv6 prefixes in the combined Route Views observation at 2026-11-06 20:00 UTC.
Identity
Operator and country are unknown from the supplied evidence.
Triage
Confirm any present-day announcement and registry assignment independently; AS22773 is an observed AS_PATH neighbour, not a verified business relationship.
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
1627 [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 observed
1 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
IPv4 address estimate
256 [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
Observed AS_PATH neighbour
AS22773 [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.