About AS56951
WeCode (AS56951) operates an open peering policy, welcoming peering connections with networks present on mutual exchange points, subject to the technical requirements below.
Open Policy
We welcome peering with any network that meets our technical requirements. No traffic minimums required for IX peering.
RPKI-Signed Routes
All our prefixes are covered by valid Route Origin Authorizations (ROAs). We filter RPKI-invalid routes from peers.
IRR Filtered
We use AS-WECODE in the RIPE IRR database. We expect peers to maintain accurate AS-SETs and prefix lists in IRR.
Internet Exchange Presence
WeCode is currently present at the following Internet Exchange Points.
| Exchange | PoP | Speed | IPv4 Address | IPv6 Address | Status |
|---|---|---|---|---|---|
| InterLAN-IX |
🇷🇴
Cluj-Napoca efectRO DC |
10G | 86.104.125.186 |
2001:7f8:64:225::5:6951 |
Active |
| Interlan-IX |
🇷🇴
București NXDATA-2 Bucharest |
Planned | — |
— |
Planned |
Interconnection Facilities
Physical locations where WeCode has network infrastructure available for peering and colocation.
| Facility | City | Country | PNI Available |
|---|---|---|---|
| efectRO DC | Cluj-Napoca | Romania | Yes |
| DataWave #1 | Cluj-Napoca | Romania | Yes |
Technical Requirements
WeCode adheres to industry best practices to ensure stable and secure peering sessions.
Route Filtering
Both parties must maintain accurate AS-SETs or route-sets in a public IRR database. WeCode will use IRR data to generate prefix-list filters for all BGP sessions.
RPKI Validation
WeCode enforces RPKI route origin validation. Routes with an RPKI status of Invalid will be rejected. We strongly recommend peers deploy RPKI ROAs for their prefixes.
BCP-38 / Anti-Spoofing
Peers are expected to implement BCP-38 source address filtering to prevent IP spoofing and protect the shared IXP fabric from DDoS amplification attacks.
NOC Contact
An up-to-date NOC contact email in PeeringDB is mandatory. Timely response to abuse and operational issues is expected from both parties.
PeeringDB Entry
Peers must have an up-to-date PeeringDB entry including accurate prefix maximums, IX presence and contact information. WeCode will reference PeeringDB for session configuration.
Maximum Prefixes
WeCode will configure max-prefix limits based on PeeringDB data. Exceeding the limit by more than 20% will result in session teardown and immediate notification.
Private Network Interconnect (PNI)
For high-volume traffic exchange, WeCode supports direct cross-connects at our colocation facilities.
PNI Threshold
Either party may request a PNI when traffic at a shared location consistently exceeds 1 Gbps. We support single or multiple 10G / 100G connections.
Capacity Upgrades
Timely capacity upgrades are required to ensure congestion-free traffic exchange. WeCode will proactively notify peers when utilization approaches 80% of provisioned capacity.
Important Notices
In order to uphold operational excellence, we retain the following rights as part of our Peering Policy:
Reserved Rights
- We maintain the ability to modify our peering policy and peering requirements at any given time.
- We retain the right to accept or decline a peering request at our discretion, without limitation to any specific reason, at any given time.
- In the event of a severe quality of service issue, such as the detection of high latency, packet loss, or jitter patterns, we reserve the right to suspend peering connectivity without prior notice. Furthermore, we may take necessary traffic engineering measures to ensure the maintenance of service quality.
- We retain the right to selectively withdraw prefixes from public Internet Exchange Point (IXP) fabrics as necessary in order to safeguard the quality of our services.
- We reserve the right to terminate any peering connection without prior notice at any given time.
More details on PeeringDB at https://www.peeringdb.com/asn/56951.
Ready to Peer with WeCode?
Send us your ASN, PeeringDB link and IX locations. We typically respond within one business day.