rirtracker

ASN

AS10519

Now

ARIN statistics
Assigned (dated 1997-08-29) (US), in the latest file
Registry
ARIN
Holder
Verizon Business
From
ARIN's latest statistics and the latest transfer record

Latest change

Transfer log Merger/acquisition or reorganization

Reported
2026-05-13 (ARIN)
Confidence
Confirmed
Inventory
No effect on ARIN applicant inventory

Timeline (1)

Every change the tracker has found, newest first. It covers ARIN from 2008-12-01, the RIPE NCC from 2010-04-23, APNIC from 2008-02-15, LACNIC from 2012-06-29 and AFRINIC from 2012-10-03.

2026-05-13 ARIN Transfer log Merger/acquisition or reorganization Confirmed
Transfer log
Merger/acquisition: ANS Communications, Inc. (ARIN) to Verizon Business (ARIN)
From
ANS Communications, Inc. ARIN
To
Verizon Business ARIN
Inventory
No effect on ARIN applicant inventory

ARIN's transfer log records a merger, acquisition or reorganization from ANS Communications, Inc. (ARIN) to Verizon Business (ARIN) on 2026-05-13 20:58 UTC. The registration changed hands; it is not a new allocation from ARIN. ARIN-Issued and ARIN's statistics don't show this change; only the transfer log records it.

Evidence (3) · classifier 1.4.0,
  1. Transfer log Transfer log: MERGER_ACQUISITION on 2026-05-13 20:58 UTC, ANS Communications, Inc. (ARIN) to Verizon Business (ARIN); resources moved: AS10519 source · retrieved
  2. Before ARIN delegated statistics 2026-05-12 (produced 2026-05-12T13:00:41+00:00), before the report: assigned (dated 1997-08-29) source · retrieved
  3. After ARIN delegated statistics 2026-05-14 (produced 2026-05-14T13:00:40+00:00), after the report: assigned (dated 1997-08-29) source · retrieved

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
ARINMerger acquisitionAS10519 ANS Communications, Inc. ARINVerizon Business ARIN

Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this ASN (ARIN's from 2009, the RIPE NCC's from 2012, APNIC's from 2010, LACNIC's from 2016, AFRINIC's from 2018). A transfer between two registries is in both logs.

RDAP lookups

Not looked up. The tracker queries RDAP for changes as they're reported (on first sight, after 24 hours and after seven days); older changes aren't looked up because today's RDAP says nothing about the past.

This page as data: asn/10519.json