Autonomous system detail

AS1018

Announced

AS1018 announces 1 IPv4 and 0 IPv6 prefixes and peers with 1 other networks.

Summary

// analyst note
Routing counts are the combined observation across route-views2 and route-views6 at 2026-11-01T00:00:00.000Z; AS35471 is an observed AS_PATH neighbour, not a verified peer or upstream.
IPv4 prefixes
1
~512 addresses
IPv6 prefixes
0
—
Peer networks
1
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

AS1018 has no verified operator identity in the supplied evidence. In the combined RouteViews observation at 2026-11-01 00:00 UTC, collected from route-views2 and route-views6, it had one IPv4 prefix covering an estimated 512 addresses and zero IPv6 prefixes. This is a dated routing snapshot, not a claim about current activity beyond that observation.

The combined observation records one AS_PATH neighbour, AS35471. That adjacency does not establish a verified peer, upstream, customer, or provider relationship. The evidence does not identify who operates AS1018, where it is based, what network type it represents, or what services it provides. IANA identifies the number as assigned by ARIN within the 1–1876 resource block; this is allocating-RIR information, not an individual assignment record.

For investigation, compare the observed prefix and AS_PATH in later routing snapshots and consult authoritative registry records for a specific assignment and operator linkage. Treat the single observed prefix as a useful lead for route-level identification, not proof of ownership, deployment, traffic volume, legitimacy, or security. No security finding or reputation assessment is supplied.

Routing observation
One IPv4 prefix and zero IPv6 prefixes were observed in the combined RouteViews snapshot at 2026-11-01 00:00 UTC.
Triage
Operator identity and security status are unknown from the supplied evidence; the routing observation alone does not establish legitimacy or risk.
Observed adjacency
AS35471 appears as an AS_PATH neighbour; this does not verify a peering or commercial relationship.
Operator
Unknown [Unknown]
AS name
Unknown [Unknown]
Country
Unknown [Unknown]

Network & routing

Network type
Unknown [Unknown]
Routing observation time
2026-11-01T00:00:00.000Z [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261101.0000.bz2
ASN
1018 [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
1 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261101.0000.bz2
IPv4 address estimate
512 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261101.0000.bz2
IPv6 prefixes
0 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261101.0000.bz2
AS_PATH neighbour count
1 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261101.0000.bz2
Observed AS_PATH neighbour
AS35471 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261101.0000.bz2
[ 02 ] — Announced prefixes

What this network routes.

1 prefixes total · as observed by RouteViews at 2026-11-06 · one collector view, not a global census
// IPv4 prefixes1
  1. 209.16.140.0/23/23
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

1 observed neighbour
// Notable connections1 of 1 observed

Neighbours observed by RouteViews at 2026-11-06, lowest ASN first. Relationships are inferences from the CAIDA AS Relationships Dataset, 2026-08-01, and establish no commercial arrangement; a dash means the inference did not resolve.

ASNOperatorRole
AS35471 — —
Neighbours observed via public BGP collectors; not a complete peering list.