Autonomous system detail

AS1625

Not announced

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

Summary

// analyst note
Combined route-views2 and route-views6 observation at 2026-11-06T20:00:00.000Z; zero prefixes, zero peers, and no AS_PATH neighbours observed. One snapshot does not establish inactivity or identity.
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

AS1625 has no confirmed operator identity in the supplied evidence, and the combined routing snapshot observed zero IPv4 and zero IPv6 prefixes. The snapshot was observed at 2026-11-06 20:00 UTC by route-views2 and route-views6; it also recorded zero peers and no AS_PATH neighbours. These results describe that observation only and do not establish whether the ASN is inactive, who operates it, or what it is used for.

The IANA AS-number record places AS1625 in resource block 1-1876, assigned by ARIN. This identifies the allocating regional registry for the block; it is not an individual assignment record and does not establish an operator, country, or deployment location.

For identification, compare this result with a later routing snapshot and consult authoritative registry records for any entity explicitly linked to AS1625. If investigating a suspected route, check its origin ASN and announcement time against multiple collectors. The supplied observations contain no prefixes, peers, or neighbour ASNs to use as a routing fingerprint, and provide no basis for assessing security or legitimacy.

Routing observation
Zero IPv4 and IPv6 prefixes, zero peers, and no AS_PATH neighbours were observed in the combined route-views2 and route-views6 snapshot at 2026-11-06 20:00 UTC. This is not evidence that the ASN is inactive.
Triage
The supplied snapshot offers no announced prefix or neighbour to use for route attribution. Compare later observations and check authoritative registry records for an entity explicitly linked to AS1625.
Security
No security findings or reputation evidence were supplied; no safety or legitimacy conclusion can be drawn.
Operator
Unknown [Unknown] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
Country
Unknown [Unknown] — 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
1625 [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
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 observed
0 [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.11/RIBS/rib.20261106.2000.bz2
AS_PATH neighbours observed
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.