AS821

AS821 is a dormant legacy autonomous system registered under ARIN to Designed Information Systems Corporation (DISC), a small Burnaby, British Columbia, Canada company, and it announces zero IPv4 and zero IPv6 prefixes in the global routing table as of 2026-08-01.

ARIN's RDAP record shows the autnum as formally "Active," allocated 1994-02-22 and last changed 1995-05-05 — both top-level registration events, not decoy entity timestamps. Despite the active registry status, every routing source checked agrees the ASN carries no live BGP presence.

RIPEstat routing-status shows 0 announced prefixes on both protocols, 0 of 328 RIS peers seeing it on IPv4 and 0 of 322 on IPv6, and 0 observed neighbours. CAIDA AS Rank lists it at 79,459 with seen: false and cliqueMember: false, consistent with no current topology crawl visibility. A direct fetch of bgp.he.net/AS821 independently corroborated 0 announced prefixes and 0 BGP peers; a bgp.tools fetch attempt returned HTTP 500 and could not corroborate further.

No PeeringDB network object exists for AS821, so peering policy and network type are Unknown rather than inferred. No operator-run website was located — a POC email domain (simkin.com) returned HTTP 403 and is unconfirmed as the org's own site. CAIDA AS Rank puts the customer cone at 1 ASN (itself), 0 prefixes, and 0 addresses, consistent with the zero announced prefixes and zero peers observed elsewhere.

Exposure

No live BGP announcements or peers means no directly exposed routed address space to assess; the ASN presents effectively zero current attack surface at the routing layer.

Abuse signal

No notable public abuse signal found as of 2026-08-01 — not on Spamhaus ASN-DROP, no matching NANOG mailing-list archive threads; a general web search for "AS821" was dominated by an unrelated "Alaska Airlines flight AS821" string collision, a known false-positive trap for this query.

Contact currency

ARIN's own record flags the technical POC (AH52-ARIN) as an "Unvalidated POC" with no response since 2010-06-08, so the on-file abuse contact should be treated as stale.

Notable CVE

none found.

Operator

Designed Information Systems Corporation (D.I.S.C.), ARIN handle DISC-9, 5065 Anola Drive, Burnaby, BC V5B 4V7, Canada [Confirmed] — ARIN RDAP autnum/entity records

Country / RIR

CA, ARIN [Confirmed] — ARIN RDAP entity DISC-9

Allocated

1994-02-22 (ARIN RDAP top-level autnum registration event); last changed 1995-05-05 [Confirmed] — ARIN RDAP autnum top-level events

Org status

ARIN RDAP status Active (registry-active); registrant is a small BC, Canada company; technical POC (AH52-ARIN) flagged unvalidated since 2010-06-08; zero current BGP announcements despite formally active RIR record [Confirmed] — ARIN RDAP autnum/entity

Contacts

no publishable role contact exists on this record — the sole ARIN POC (handle AH52-ARIN, holding the abuse, administrative and technical roles) is a natural person per its RDAP vCard, so its contact detail is correctly withheld; ARIN has flagged that POC unvalidated since 2010-06-08. Registrant organisation is Designed Information Systems Corporation, 5065 Anola Drive, Burnaby, BC V5B 4V7, Canada (org premises)

[Confirmed] — ARIN RDAP entity AH52-ARIN (vCard kind), ARIN RDAP entity DISC-9

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-08-01 — not in Spamhaus ASN-DROP, no NANOG archive hits; general web search dominated by an unrelated "Alaska Airlines flight AS821" collision — spamhaus.org/drop/asndrop, mail-archive.com NANOG search

Network & routing

Network type

Unknown / likely dormant — no PeeringDB network object exists for AS821 (404 on site and API); live BGP shows 0 prefixes, 0 peers [Likely] — peeringdb.com/asn/821, bgp.he.net/AS821

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone 1 ASN (itself), 0 prefixes, 0 addresses (CAIDA rank 79,459, seen:false, degree 0 in every direction) [Confirmed] — RIPEstat routing-status / CAIDA AS Rank / bgp.he.net (2026-08)

Routing/peering

NOT announced — 0 of 328 RIS peers seeing it on IPv4, 0 of 322 on IPv6, 0 observed neighbours; CAIDA rank 79,459 with seen:false and cliqueMember:false; bgp.he.net independently confirms 0 peers, 0 prefixes [Confirmed]. No PeeringDB record, so peering policy is Unknown [Unknown]

RPKI

not assessable — AS821 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation requires a --prefix parameter and none exist [Confirmed]

Notable usage

Unknown — no source found describing notable historical or current usage for AS821 [Unknown]

Related ASNs

Unknown — no related-ASN grouping found for this registrant [Unknown]

Analyst note

Encountered as a formally-active-but-operationally-dormant legacy ASN; WHOIS/RDAP resolves cleanly to a small BC, Canada operator (DISC), but no BGP presence, no PeeringDB record, and no operator website were found. Research relied on WebFetch against named registry and reputational sources.