Network & Peering
nrdigitallc.com is the official website of AS218876, the autonomous system operated by N.R Digital LLC. This page documents our network, how to peer with us, and how to reach us about abuse.
Autonomous system details
| Operator | N.R Digital LLC |
|---|---|
| AS number | AS218876 |
| AS name | NR-DIGITAL-LLC-AS |
| Registry (RIR) | RIPE NCC — org ORG-NDL10-RIPE, registered 25 August 2026 |
| IRR as-set | [AS-SET] |
| IPv4 prefixes | [IPv4 PREFIXES] |
| IPv6 prefixes | [IPv6 PREFIXES] |
| PeeringDB | [PEERINGDB URL] |
| Registered address | 1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110, United States |
What runs on this network
The autonomous system exists to serve our own products — we are the operator and the customer:
- VaultProxies (vaultproxies.net) — our proxy service, sold for lawful business uses such as web scraping, market research, ad verification, and SEO monitoring.
- VeloRDP Cloud (velordp.cloud) — our hosting platform: KVM VPS, dedicated servers, web hosting, and game servers, with DDoS protection on every plan.
- CyberTemp (cybertemp.xyz) — our temporary email service.
Full product details are on our services page.
Footprint
Our primary deployment zone is Frankfurt, Germany (Equinix FR5), with direct connectivity to DE-CIX for low-latency reach across European networks. Additional capacity is deployed through partner facilities in Europe and North America.
| Primary facility | Equinix FR5 — Frankfurt, DE |
|---|---|
| Exchanges | [IX LIST] |
| Upstreams and partners | [UPSTREAMS] |
| DDoS mitigation | Always-on filtering in front of customer-facing ranges |
Peering policy
We maintain an open peering policy and will peer with any network that can meet the basics below. Peering requests, capacity questions, and maintenance coordination go to noc@nrdigitallc.com.
- A fully redundant, professionally operated network with a 24/7 contact
- Up-to-date PeeringDB record
- Accurate IRR objects for the prefixes you announce, and valid RPKI ROAs
- No default route, no pointing static routes at us, no transit through the peering session
- Prompt handling of abuse and technical issues reported by us
Routing security
- Our prefixes are covered by RPKI ROAs, and we validate RPKI on sessions with peers and upstreams — invalids are dropped.
- We publish and maintain IRR objects for everything we originate, and build peer filters from IRR data.
- We apply maximum-prefix limits and inbound/outbound prefix filtering on every BGP session.
- We follow MANRS norms for filtering, anti-spoofing, coordination, and global validation.
Abuse handling
We answer abuse reports ourselves. Send reports about traffic originating from AS218876 to abuse@nrdigitallc.com, a monitored mailbox read by the people who operate the network.
- Include: source and destination IP addresses, the port and protocol, timestamps with the time zone, and relevant log excerpts or headers. Reports without timestamps and time zones cannot be traced.
- Acknowledgement: we aim to acknowledge every report within one business day.
- Action: confirmed abuse results in customer notification, filtering, suspension, or account termination, depending on severity. Attacks, port scanning, intrusion attempts, spam, phishing, and malware distribution are prohibited under our Acceptable Use terms.
- Law enforcement and legal requests: send to contact@nrdigitallc.com with "Legal" in the subject line.
Network contacts
| NOC & peering | noc@nrdigitallc.com |
|---|---|
| Abuse | abuse@nrdigitallc.com |
| Business & billing | contact@nrdigitallc.com |
Want to peer with AS218876?
Send us your ASN, PeeringDB record, and preferred exchange — we'll get a session set up.
Email our NOC