AS578

AS578 sits inside the IANA 16-bit AS Numbers registry block historically assigned by ARIN, but no live registry record for it exists today. Direct ARIN RDAP (rdap.arin.net/registry/autnum/578) returns HTTP 404 "AUTNUM NOT FOUND," legacy WHOIS (whois.arin.net:43) returns "No match found for AS578," and the generic RDAP bootstrap (rdap.org/autnum/578) also returns 404 — confirmed on two separate live queries, including a re-run of the project's own canonical-fetch script. RIPEstat's as-overview shows an empty holder field, and third-party aggregator cidr-report.org labels the ASN "-Reserved AS-" with an unspecified (ZZ) country code, consistent with an entry that has lapsed or was never re-registered rather than one that is actively held. A separate aggregator, ipinfo.io, attaches the name "Packaging Dynamics," but that attribution is not corroborated by any authoritative source and the company's real corporate website shows no ASN or network operations content, so it is treated as unverified rather than fact. Routing history is the one area with strong corroboration: AS578 was first seen originating 207.61.186.0/24 in September 2002 and last seen originating 12.106.238.0/24 (a prefix bgp.he.net flags as a bogon) around mid-to-late June 2018, with a single historical BGP peer, AS32654 (Towerstream I, Inc.). It has announced zero prefixes and drawn zero RIS visibility ever since, and CAIDA's ASRank has no entry for it at all.

Operator

Unknown/unverifiable — no operator name is confirmed by any authoritative source. Third-party aggregator ipinfo.io names "Packaging Dynamics," but ARIN RDAP/WHOIS show no current record and the company's real site (packagingdynamics.com) has no network/ASN content

[Unknown] — https://ipinfo.io/AS578, https://rdap.arin.net/registry/autnum/578

Country / RIR

RIR = ARIN, via the IANA 16-bit AS Numbers registry block (resource 1-1876, "Assigned by ARIN"), independently confirmed by RIPEstat's authoritative_rir: arin field [Confirmed] — https://stat.ripe.net/data/as-overview/data.json?resource=578, https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=578. Country is Unknown/unspecified: RIPEstat's holder field is blank and cidr-report.org lists country code "ZZ"

[Likely] — https://www.cidr-report.org/as6447/autnums.html

Allocated

Unknown — no RDAP autnum object exists for AS578 at all (HTTP 404 confirmed on two independent live queries against rdap.org, plus ARIN RDAP 404 and legacy WHOIS "no match"), so there is no top-level events[] block to read a registration date from. This is a genuine source absence, not a truncation artifact, and no date is recorded

[Confirmed absence of record] — https://rdap.org/autnum/578, https://rdap.arin.net/registry/autnum/578

Org status

No current ARIN registration found — direct RDAP and legacy WHOIS queries both returned "not found" on 2026-07-11 [Confirmed] — https://rdap.arin.net/registry/autnum/578

Contacts

None listed — RIPEstat's abuse-contact-finder returned zero abuse contacts [Confirmed] — https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=578

Security/abuse context (NEUTRAL, DATED)

No notable public abuse signal found as of 2026-07-11 across Spamhaus ASN-DROP (partial fetch only), general web search, and NANOG archive search; RIPEstat abuse-contact-finder returns an empty abuse_contacts array. Caveat: this may reflect the ASN's long-term routing inactivity (dark since 2018) rather than a clean, active reputation

Network & routing

Network type

Unknown — cannot be classified without a confirmed operator [Unknown]

Size / routing footprint

0 IPv4 prefixes and 0 IPv6 prefixes currently announced (0 of 325 RIS peers see any v4 route, 0 of 322 see any v6 route); historically originated exactly one IPv4 prefix (12.106.238.0/24, flagged as a bogon by bgp.he.net) in its final active period

[Confirmed] — https://stat.ripe.net/data/routing-status/data.json?resource=578, https://bgp.he.net/AS578

Routing/peering history

First seen announcing 207.61.186.0/24 on 2002-09-14; last seen announcing 12.106.238.0/24 on 2018-06-25 per RIPEstat (bgp.he.net independently states "not visible in the global routing table since June 21, 2018" — a several-day discrepancy between the two sources for the same withdrawal event, both cited here rather than resolved). Sole historical BGP peer: AS32654 (Towerstream I, Inc.) [Confirmed core facts; Likely on exact withdrawal date] — https://stat.ripe.net/data/routing-status/data.json?resource=578, https://bgp.he.net/AS578

RPKI

Not assessable — AS578 announces no prefixes today, so RIPEstat's rpki-validation check was skipped (it requires a specific prefix argument) and there are no ROAs to validate against [Confirmed] — https://stat.ripe.net/data/rpki-validation/data.json

CAIDA rank / customer cone

No CAIDA ASRank entry exists for AS578 ({"data":{"asn":null}}), consistent with an ASN withdrawn from routing since 2018; customer cone and AS rank are therefore Unknown [Confirmed absence] — https://api.asrank.caida.org/v2/restful/asns/578

Related ASNs

None found in any source consulted [Confirmed absence]

Analyst note

AS578 reads as a lapsed/legacy ARIN-block ASN with no live registry record. It was routed for roughly 16 years (2002–2018) under an operator that cannot now be confirmed, then went fully dark. The "Packaging Dynamics" attribution seen on aggregator sites is not corroborated and should not be treated as fact.