Peer with AS215085

We maintain an open peering policy.

Our peeringDB page: https://www.peeringdb.com/net/35968

Peering requirements

General Requirements

• An up-to-date and valid PeeringDB profile
• Valid IRR and RPKI entries for all advertised prefixes
• An operational NOC contact (email or phone) for issues or abuse reports, monitored regularly for timely response
• Mutually agreed peering locations (IXPs or private interconnects)
• Support for MD5 authentication on BGP sessions when possible
• BGP sessions must be established over IPv6 and/or IPv4 as agreed

Routing Requirements

• Only advertise routes that are owned or properly registered to your ASN
• Do not advertise default routes or third-party prefixes unless explicitly agreed
• Maintain consistent prefix filtering and prevent route leaks
• Prefixes should be aggregated where possible

Downstream Policy

• Downstream customers must:
• Have valid IRR/RPKI data
• Only announce prefixes they have legal and administrative control over
• Be reachable for coordination
• We reserve the right to filter or de-peer downstreams not complying with these requirements

Operational Notes

• We monitor peering sessions for stability and performance
• Persistent route leaks, BGP session flapping, or abuse may lead to de-peering
• We prefer bi-directional traffic engineering coordination

Peering details

AS Number: AS 215085

AS-set: RIPE::AS215085:AS-PIXELHOSTING

Prefixes IPv4 in AS215085: 1

• 83.142.31.0/24

Prefixes IPv6 in AS215085: 1

• 2a06:9f41::/32

BGP communities for traffic engineering can be found on our BGP communities page

Want to peer with us?

You can send your peering request to noc AT pixelhosting DOT nl. Please configure your side within 24 hours after sending this mail. Also include your details in the email.