AS1280

AS1280 is an ASN with observed routing activity, but the supplied evidence does not establish its registered organization or current operator. In the combined Route Views observation at 2026-11-03 14:00 UTC, it appeared with 92 IPv4 prefixes and 7 IPv6 prefixes. These counts describe that snapshot from route-views2 and route-views6 together; they do not establish ownership or deployment.

The same observation contained nine AS_PATH neighbours. Treat those as routing adjacencies only: they do not verify commercial peers, upstreams, or customer relationships. For identification, compare the ASN and its announced prefixes with current routing and registry records, and seek first-party evidence explicitly linking the organization to AS1280 before assigning an operator.

ISC’s 2014 network operations report mentions AS1280 in describing a large DDoS attack against ISC services and hosted name-service infrastructure. It says transit providers filtered attack traffic after the attack vector was identified with community assistance. This documents a historical event involving AS1280; it does not establish the ASN’s present operator, current threat status, or a mapping between AS1280 and a specific product or prefix.

Routing observation

92 IPv4 prefixes and 7 IPv6 prefixes observed in the combined Route Views snapshot at 2026-11-03 14:00 UTC.

Identity

Operator and registered organization are Unknown from the supplied evidence.

Security context

ISC’s 2014 report mentions AS1280 in a DDoS incident; this is historical context, not a current safety or threat assessment.

Triage

Validate any attribution against current routing and first-party records that explicitly identify AS1280.

RIR

ARIN [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv

Operator

Unknown [Unknown] — https://www.isc.org/blogs/notable-events-in-isc-network-operations-in-2014/

Country

Unknown [Unknown] — https://www.isc.org/blogs/notable-events-in-isc-network-operations-in-2014/

Network & routing

Network type

Unknown [Unknown] — https://www.isc.org/blogs/notable-events-in-isc-network-operations-in-2014/

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

1280 [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv

IPv4 prefixes

92 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2

IPv4 address estimate

23296 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2

IPv6 prefixes

7 [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2

AS_PATH neighbour count

9 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261103.1400.bz2

Historical security context

AS1280 was mentioned in ISC’s account of a DDoS incident [Confirmed] — https://www.isc.org/blogs/notable-events-in-isc-network-operations-in-2014/