Autonomous system detail

AS1505

Not announced

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

Summary

// analyst note
No prefixes or AS_PATH neighbours were observed in the combined Route Views snapshot at 2026-11-03 14:00 UTC across route-views2 and route-views6; this does not establish inactivity.
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

AS1505 is an autonomous system number assigned by ARIN; its operator and purpose are Unknown from the supplied evidence. In the combined Route Views observation at 2026-11-03 14:00 UTC, across route-views2 and route-views6, it had zero observed IPv4 prefixes, zero IPv6 prefixes, zero estimated IPv4 addresses, and zero observed peers. This describes that snapshot only; it does not establish that the ASN is dormant or inactive.

The IANA record places AS1505 in resource range 1–1876 and identifies ARIN as the allocating regional internet registry. That range-level assignment does not identify an individual registrant, operator, country, or deployment. The routing sample contains no AS_PATH neighbours, so it supplies no observed adjacency to investigate in this snapshot.

For triage, compare later routing snapshots and check authoritative registration records for an ASN-specific organization and contact-free organizational details. If routes appear later, inspect their origin and paths across multiple collectors before attributing them to an operator or inferring provider relationships. Treat an empty observation here as a time-bounded routing result, not a safety or reputation assessment.

Routing snapshot
Zero IPv4 and IPv6 prefixes and zero AS_PATH neighbours observed in the combined Route Views snapshot at 2026-11-03 14:00 UTC across route-views2 and route-views6.
Registry
IANA identifies ARIN as the allocating RIR for the range containing AS1505; an ASN-specific operator is Unknown.
Triage
Compare later snapshots and verify any future origin or path observations before making attribution claims.
Observation scope
combined RouteViews snapshot at 2026-11-03T14:00:00.000Z; route-views2, route-views6 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
ASN
1505 [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.20261103.1400.bz2
IPv4 address estimate
0 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
IPv6 prefixes observed
0 [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
AS_PATH neighbours observed
0 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.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.