Networks
To provide bandwidth and connectivity to and from some of our services, we run on top of the Autonomous Systems: AS401401 and AS401720 as well as many other networks.
Our network is monitored, and metrics are collected to determine its performance. However, we do this in a privacy friendly way by not storing any flow data.
An experimental anycast network (AS401401) designed to add noise (randomness) into the network layer
Read more about Unredacted Labs
Peering Policy
Unredacted Inc is a 501(c)(3) nonprofit that builds Internet infrastructure and services to help people access the open Internet and protect their right to privacy. We maintain an open peering policy and welcome interconnection with networks that share our interest in a healthy, well-connected Internet.
Our Networks
Unredacted operates two autonomous systems:
| ASN | Name | IRR as-set | Purpose |
|---|---|---|---|
AS401401 | Unredacted Inc (NoiseNet) | AS-UNREDACTED-NOISENET | NoiseNet — anycast edge network for privacy & anti-censorship services |
AS401720 | Unredacted Inc (Core) | AS-UNREDACTED | Content delivery & infrastructure |
General Policy
Our peering policy is open. We are happy to peer with any network operating in good faith, regardless of size, traffic volume, or ratio. There is no contract requirement and no minimum traffic threshold.
We peer over route servers at Internet Exchange Points where we are present, and we are also open to establishing bilateral (direct) BGP sessions where it is mutually beneficial.
Requirements
We ask that prospective peers meet the following baseline criteria:
- Operate a publicly routable ASN and maintain accurate PeeringDB records.
- Maintain up-to-date IRR route objects (RPSL) for all announced prefixes.
- Announce only prefixes they are authorized to originate or transit.
- Have a reachable NOC contact for operational issues.
- Do not point a default route or send traffic not destined for our announced prefixes across the peering session.
Route Server Peering
At exchanges where we have a presence, we peer with the available route servers. If your network is also present at one of those exchanges, we may already be exchanging routes – no action required on your part. You can confirm mutual IX presence on our PeeringDB pages linked below.
Bilateral Peering
We are open to establishing direct bilateral BGP sessions when doing so is deemed mutually beneficial – for example, when both networks share presence at an exchange and direct sessions would improve convergence time or enable more specific traffic engineering. To request a bilateral session, contact us at the address below.
Technical Details
| Protocols | IPv4 Unicast, IPv6 Unicast |
|---|---|
| MD5 | Supported on request; not required |
| Max Prefix Limits | We recommend configuring reasonable prefix limits. Our current announcements are small, but please refer to PeeringDB or the IRR for up-to-date figures. |
| RPKI | We sign our routes with RPKI ROAs and encourage peers to validate and filter based on RPKI status. |
| Graceful Shutdown | We support RFC 8326 (GRACEFUL_SHUTDOWN community) and encourage peers to do the same. |
PeeringDB
For the most current information on our exchange presence, facilities, and contact details, please see our PeeringDB records:
Contact
To request peering, report an issue, or ask a question, reach out to our NOC:
| Peering & NOC | noc [ @ ] unredacted.org |
|---|---|
| Abuse | abuse [ @ ] unredacted.org |
| Website | unredacted.org |
We reserve the right to disable or decline a peering session at any time if a peer is observed engaging in abusive behavior, originating hijacked prefixes, or otherwise operating in a manner harmful to the stability of the Internet. This policy may be updated from time to time; the version published on this page is always the current one.