Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS6515 (DACSNX-ISP) announces 4 IPv4 and 10 IPv6 prefixes. 2 warnings
| AS page | AS6515 |
|---|---|
| Holder | DACSNX-ISP - DACS-IX |
| Allocation | ARIN, United States (US), assigned 2019-08-29 |
| Prefixes (IPv4 / IPv6) | 4 / 10 |
| RPKI valid | 100% (14 / 14) |
| Upstreams and peers | 11 |
| Peering policy | Open |
What to fix
-
Warning
2 of 14 announced prefixes have no IRR route object: 2602:ffa9:d32::/48, 2602:ffa9:d31::/48.
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS6515 in your RIR’s IRR database (or RADB).
route6: 2602:ffa9:d32::/48 origin: AS6515 route6: 2602:ffa9:d31::/48 origin: AS6515
-
Warning
No public NOC, policy or technical contact.
Other networks use these addresses to set up peering and to reach you during an incident.
Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.
Checks
Routing and RPKI 2 of 14 announced prefixes have no IRR route object: 2602:ffa9:d32::/48, 2602:ffa9:d31::/48.
- Pass: AS6515 announces 4 IPv4 and 10 IPv6 prefixes.
- Pass: All 14 announced prefixes are RPKI valid.
- Warning: 2 of 14 announced prefixes have no IRR route object: 2602:ffa9:d32::/48, 2602:ffa9:d31::/48.
- Info: 11 upstreams and peers, 6 downstream networks seen.
| Holder | DACSNX-ISP - DACS-IX |
|---|---|
| IPv4 prefixes | 4 |
| IPv6 prefixes | 10 |
| RPKI | 14 valid |
| Without IRR route object | 2 |
| Downstream networks | 6 |
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.arin.net.
- Pass: Found at rdap.arin.net.
| Name | DACSNX-APEX |
|---|---|
| Handle | AS6515 |
| Range | AS6515 |
| Status | active |
| Registered | 2019-08-29T09:39:29-04:00 |
| Last changed | 2026-10-05T15:37:41-04:00 |
| Abuse contact | noc@dacs-nx.com |
| Registry (RIR) | ARIN |
|---|---|
| Country | United States (US) |
| Delegated on | 2019-08-29 |
| Status | Assigned |
| Delegated range | AS6515 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | DACS-IX |
Source: https://rdap.arin.net/registry/autnum/6515. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS6515 is in PeeringDB as DACS NX.
- Info: Peering policy: Open.
- Info: Present at 12 internet exchanges with 12 ports (300G in total).
- Warning: No public NOC, policy or technical contact.
| Network | DACS NX (DACS-NX) |
|---|---|
| AS number | AS6515 |
| Type | NSP, Not Disclosed |
| Website | http://www.dacs-nx.com |
| IRR as-set | RADB::AS6515:AS-DACSNX |
| Prefixes (IPv4 / IPv6) | 1000 / 1000 |
| Traffic | 20-50Gbps, Not Disclosed |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-11-02 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup