Autonomous system
AS6515 DACSNX-ISP - DACS-IX
Unclassified ARIN NSP
Summary
DACS-IX
hosting legacy
AS6515 belongs to DACS-IX, a Maryland-based operator that runs internet-exchange fabrics in the Washington–Baltimore corridor and sells ISP and cloud services under the DACS-NX and DACS Cloud names. ARIN registered the ASN in 2019, so despite the low number there is no early-internet pedigree here.
What it's used for
- Routed ISP and cloud addressing, not the exchange fabric itself. The announced
/24s carry netnamesSPG-ISP-REASSIGN-BLOCK1andBLOCK2registered to DACS Cloud, which is customer-reassignment space. - Reverse DNS resolves to gateway routers under
dacs-nx.net(for example abwi1gateway, i.e. the Baltimore–Washington area), confirming this is the operator's own transit and hosting network.
Notable
- The registered address is a Silver Spring, Maryland data-centre facility, and the company's exchange presence spans sites including Baltimore, Ashburn, Reston, Atlanta, Orlando and New York.
- Do not confuse this AS with the peering LAN. An IXP operator's company AS and its exchange fabric are different things; only the former originates routes, and that is what AS6515 does.
Interesting
- The registry has carried several names for this ASN over the years (
DACSIX-EAST,DACSNX-ISP,DACSNX-APEX), reflecting the operator's split between its exchange, ISP and cloud brands.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 4 exchanges in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| New York International Internet Exchange | New York, United States | 198.32.160.52 |
| DACS-IX East | Baltimore, United States | 206.83.44.250 |
| DACS-IX West | Fremont, United States | 206.83.140.10 |
| Nell-IX | Reston, United States | 149.112.180.10 |
Transit providers
7 upstream, 6 downstream and 20 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-06, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 3 prefixes · 1.02K addresses IPv6 6 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 9 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS6515- Registry name
- DACSNX-APEX
- Registrant
- DACS-IX
- Abuse contact
- noc@dacs-nx.com
- Registered
- 2019-08-29
- Last changed
- 2026-10-05
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- DACS NX
- Also known as
- DACS-NX
- Network type
- NSP
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- IRR as-set
RADB::AS6515:AS-DACSNX- Present at
- 12 exchanges
- Facilities
- 11 facilities
- Website
- http://www.dacs-nx.com
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 15 valid, 0 with no ROA
- ROAs
- 7 authorising AS6515
- ASPA
- no ASPA record
- IRR
- 100% registered · 15 of 15 announcements
- Route objects
- 53 naming AS6515
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 454 networks and 1,854 prefixes, as published 2026-11-06. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere