NyaNet operates under Autonomous System AS200993 and hosts external services required for its operation. Our network consists of globally distributed ingress points: we operate dozens of Points of Presence (PoPs) worldwide, colocated with multiple upstream providers that offer access to Internet Exchange Points (IXPs) and private interconnects.
AS200993 carries three types of traffic:
Based on our traffic distribution, we expect approximately 60% predominantly outbound traffic and 40% predominantly inbound traffic. We are working on reducing the share of inbound traffic, but cannot guarantee this in the near future.
Each NyaNet PoP contains its own set of servers. A PoP may host:
either individually or all at once.
Each PoP announces unique IP prefixes in every deployed location, except for prefixes required for Anycast operation. We provide an RFC 8805 Geofeed (CSV) mapping announced IP addresses to their geographical locations within our network.
Test IP addresses listed in the Geofeed comments may be used to evaluate connection quality and stability.
Each PoP routes traffic independently from other locations. Prefixes learned at other PoPs are not used to deliver content that is not regionally associated with the originating PoP.
If you believe there are errors or inaccuracies during testing, please contact us at pop@nyanet.ru and include:
NyaNet follows an open peering policy.
To peer with NyaNet, the following requirements must be met:
We automate data collection from PeeringDB to identify optimal content delivery paths and suitable peering partners. At a minimum, the following information must be present:
NyaNet is present at key IXPs and announces all available prefixes at all IXPs accessible to us in a given location. We actively expand our IXP presence, with a preference for non-profit IXPs.
If we are present in your data center but not available at your IXP, please contact peering@nyanet.ru.
If you peer via a route server (RS), you should receive all our local routes and Anycast ingress points (and vice versa). In most cases, IXP peering alone is sufficient and PNI is not required.
We support bilateral peering with networks whose traffic volume exceeds:
Local prefixes are announced over a dedicated session. Performance improvement is possible but not guaranteed.
When requesting peering, please email peering@nyanet.ru and include:
In many locations we maintain dual IXP ports — please establish BGP sessions on all available ports.
We support settlement-free PNI in locations listed in PeeringDB or available via partner VLANs.
PNIs are available for peers with traffic volumes exceeding 1 Gbps, regardless of location. Smaller networks are expected to use IXP or bilateral peering.
Typically, we initiate PNI or bilateral peering when utilization exceeds 50% of 1 Gbps for a given ASN. Costs are split evenly; IP addressing is provided by us, and both parties supply LoAs.
When utilization exceeds 1 Gbps, we fully cover PNI costs.
To request PNI, contact peering@nyanet.ru.
Fallback is a reserve PoP connection announced upstream on demand and used exclusively for service purposes.
Do we need to peer with NyaNet?
Not necessarily, unless utilization toward AS200993 exceeds
50%.
Will bilateral peering increase the number of announced prefixes?
No. Prefix sets are
strictly location- and PoP-specific.
Why are you not present at %ixpname%?
We actively expand IXP presence but cannot guarantee
participation everywhere. Suggestions are welcome via peering@nyanet.ru.
Why are you not present at M9?
Due to high costs and insufficient economic justification
after recent price increases.
I want a 10G PNI in %locationname%.
Email peering@nyanet.ru with your ASN.
Was this written as a joke?
Yes — to avoid an empty peering page 🙂