Autonomous system detail  ·  US flag US

AS815

Not announced

Last known operator Verizon Business (org handle MCICS). No prefixes for this AS number were observed in the RouteViews RIB.

Summary

// analyst note
Administratively active, operationally dormant legacy ASN. RDAP resolves to Verizon Business under the historical UUNET-CANADA label; last routing-table announcement on record is 216.95.232.0/24, last seen 2002-02-19. Verizon's active backbone routing runs under AS701/AS702/AS703, not AS815. All routing sources (RIPEstat, CAIDA) agree on zero current announcements, zero peers, zero cone.
// security note
NEUTRAL/DATED: no notable public abuse signal found specifically for AS815 as of 2026-08-01.
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: High  ·  11 sources  ·  How this page is checked

AS815 is a legacy autonomous system originally assigned to UUNET Canada Inc. and now registered to Verizon Business, but it is dormant in the global routing table — RIPEstat and CAIDA both show it announcing zero IPv4 and zero IPv6 prefixes today, with no visible BGP peers, upstreams, or customers.

The ASN's history traces UUNET's rise as one of the first major commercial ISPs. UUNET Canada's national IP backbone ran under this number before UUNET was absorbed into MFS/WorldCom, then MCI, and finally acquired by Verizon in 2006 to form Verizon Business — the current ARIN registrant of record (org handle MCICS).

ARIN's RDAP record remains administratively active for AS815 (status: active, last changed 2022-05-31), but the last routing-table announcement on record dates to 2002-02-19 (216.95.232.0/24). CAIDA ranks it 79,459 with a customer cone limited to the ASN itself — zero prefixes, zero addresses, zero degree in any direction.

No PeeringDB profile exists for AS815 (a direct lookup returns 404), and no AS815-specific peering policy was found. Verizon Business does publish a corporate peering policy, but it scopes itself explicitly to its three active regional backbone ASNs — AS701 (Americas), AS702 (Europe), and AS703 (Asia-Pacific) — and never names AS815, so whether that policy would govern this ASN if it were reactivated is unconfirmed.

Exposure
AS815 originates no live prefixes, so it presents no current routing attack surface (no announced space to hijack or misroute).
Abuse signal
No notable public abuse report names AS815 or UUNET-Canada specifically as of 2026-08-01; a direct Spamhaus ASN-DROP query for AS815 returned no result.
Related-ASN caution
Distinct Verizon/UUNET-lineage ASNs carry documented abuse history — Spamhaus's 2016 report on cybercrime routing names AS7046 (originally UUnet Technologies), not AS815 — so that history should not be conflated with this ASN.
RPKI
Not evaluable; with zero announced prefixes there are no ROAs to validate against.
Operator
Verizon Business (org handle MCICS; current ARIN registrant); RDAP name field retains the legacy label UUNET-CANADA, reflecting origin as UUNET Canada Inc. [Confirmed] — rdap.arin.net/registry/autnum/815
Country / RIR
US, ARIN [Confirmed] — ARIN RDAP autnum record
Allocated
2002-05-21 (ARIN RDAP top-level autnum registration event); last changed 2022-05-31 [Confirmed] — rdap.arin.net/registry/autnum/815
Org status
active per ARIN (status: active); registrant Verizon Business, a business unit of Verizon Communications Inc., HQ Ashburn, VA; no indication of retirement or return to IANA [Confirmed] — rdap.arin.net/registry/autnum/815
Contacts
abuse-mail@verizonbusiness.com; abuse@verizon.com [Confirmed] — RIPEstat abuse-contact-finder

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found specifically for AS815 as of 2026-08-01; distinct Verizon/UUNET-lineage ASNs (e.g. AS7046, formerly UUnet Technologies) do carry documented abuse history and should not be conflated with AS815

[Likely] — spamhaus.org/resource-hub/service-providers/verizon-routing-millions-of-ip-addresses-for-cybercrime-gangs

Network & routing

Network type
legacy/historical UUNET Canada national IP backbone; dormant today (zero announced prefixes) — Verizon's active global backbone routing runs under AS701/AS702/AS703, not AS815 [Confirmed]
Size
dormant — 0 IPv4 prefixes / 0 addresses and 0 IPv6 prefixes; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses; CAIDA AS rank 79,459 [Confirmed] — RIPEstat routing-status, CAIDA AS Rank (2026-08-01)
Routing/peering
NOT announced — 0 RIS peers currently seeing it (0/328 v4, 0/322 v6); CAIDA degree total 0 (customer 0, peer 0, provider 0); no PeeringDB entry (404); last historical announcement was 216.95.232.0/24, last seen 2002-02-19 [Confirmed]. Verizon's active backbone (AS701/702/703) peering policy does not mention AS815 [Confirmed for policy scope; Unknown whether it would apply to AS815]
RPKI
not assessable — AS815 announces no prefixes, so there are no ROAs to validate; RIPEstat's rpki-validation check requires a prefix and was skipped for this reason [Confirmed]
Notable usage
historically the AS number for UUNET Canada's national IP network, a major early commercial ISP backbone; folded into Verizon Business after the 2006 acquisition; no current observable usage since the AS is dormant at the BGP level [Likely] — bgp.he.net/AS815, rdap.arin.net/registry/autnum/815
Related ASNs
AS701, AS702, AS703 (Verizon Business's active regional backbones, named in its published peering policy); AS7046 (originally UUnet Technologies, a distinct Verizon/UUNET-lineage ASN with documented abuse history) [Confirmed]
Analyst note
Encountered as an administratively active but operationally dormant legacy ASN. WHOIS/RDAP resolves to Verizon Business under the historical UUNET-CANADA label; live routing has not been observed since 2002, and Verizon's current active backbone runs under AS701/AS702/AS703. Clean — no abuse signal specific to this ASN.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · as observed by RouteViews at 2026-09-20 · 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.