Autonomous system detail

AS1130

Not announced

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

Summary

// analyst note
The combined Route Views observation at 2026-11-03 14:00 UTC recorded no prefixes or AS_PATH neighbours across route-views2 and route-views6. This does not establish inactivity or identity. Preserve contextual evidence and compare with additional observations before attribution.
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

AS1130 is assigned within the ARIN-allocated AS-number block, and the combined routing snapshot observed no announced prefixes or AS_PATH neighbours for it. This is a snapshot finding, not proof that the ASN is dormant, inactive, or unused.

At 2026-11-03 14:00 UTC, the combined observation across Route Views collectors route-views2 and route-views6 recorded zero IPv4 prefixes, zero IPv6 prefixes, zero estimated IPv4 addresses, and zero peers. The observation has a single timestamp and covers only those two collectors. No operator, organization, country, network type, website, or security findings are established by the supplied evidence.

For identification, treat AS1130 as unconfirmed when matching it to an organization or service. If it appears in a log or configuration, retain the surrounding timestamp, addresses, and AS_PATH, then compare them with other routing observations and first-party documentation. Do not infer an upstream, customer relationship, ownership, or malicious activity from this snapshot. The zero counts describe what these collectors observed at that time; a later or broader observation may differ.

Routing observation
Zero IPv4 and IPv6 prefixes and zero AS_PATH neighbours in the combined snapshot at 2026-11-03 14:00 UTC across route-views2 and route-views6.
Triage
The snapshot does not establish inactivity, ownership, legitimacy, or malicious use. Preserve any surrounding log context and compare with additional observations before attributing AS1130.
ASN
1130 [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
0 in the combined observation at 2026-11-03 14:00 UTC [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
IPv4 address estimate
0 in the combined observation at 2026-11-03 14:00 UTC [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
IPv6 prefixes
0 in the combined observation at 2026-11-03 14:00 UTC [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2
AS_PATH neighbour count
0 in the combined observation at 2026-11-03 14:00 UTC [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.