BGP Peering
Direct BGP-4 sessions with AS35661. Full or partial routes, BFD, 4-byte ASN. Live in 24-48 hours.
AS35661 Presence
Private peering (cross-connect) available at all four locations.
View our PeeringDB ProfileTechnical Specifications
| Specification | Details |
|---|---|
| BGP Version | BGP-4 (RFC 4271) |
| Session Types | eBGP (External), iBGP (Internal) |
| IPv4 Support | Full BGP table or partial routes |
| IPv6 Support | Native dual-stack |
| ASN Support | 2-byte and 4-byte ASN |
| Route Filtering | Prefix lists, AS-PATH, communities |
| BFD Support | Bidirectional Forwarding Detection |
| MD5 Authentication | Supported |
| AS-SET | AS-VIRTUASYS |
| IRR Database | RIPE |
| Max Prefix IPv4 | 1000 |
| Max Prefix IPv6 | 100 |
| Session Setup | 24-48 hours |
| Port Speed | 1 Gbps - 100 Gbps |
| Locations | Paris, Lille, Amsterdam, Frankfurt, + remote peering |
| Redundancy | Dual routers recommended |
| Monitoring | 24/7 NOC + NetFlow |
| NOC Contact | noc@virtuasys.eu, +33 1 85 09 04 04 (24/7) |
| SLA | 99.9% BGP session uptime |
Use Cases
- ISP Multi-Homing
- Establish redundant BGP sessions with multiple upstreams for path diversity and failover.
- CDN/Content Providers
- Optimize content delivery with direct peering to reduce latency and transit costs.
- Enterprise Multi-Site
- Connect multiple datacenter locations with private iBGP for consistent routing.
- Traffic Engineering
- Shape inbound/outbound traffic using AS-PATH prepending, MED, and local preference.
BGP Session Setup
Requirements
- Valid ASN (2-byte or 4-byte)
- IPv4 and/or IPv6 addresses
- LOA (Letter of Authorization) if announcing PI space
- Route objects registered in IRR (Internet Routing Registry)
- Up-to-date PeeringDB entry
- 24/7 NOC contact on file
Process
- 1Submit your ASN, prefixes and PeeringDB entry
- 2We verify route objects and authorization
- 3Exchange session details (IP addresses, MD5 password) and go live within 24-48 hours
Commercial Shape
Settlement-free peering for balanced traffic exchange. No minimum traffic requirement, no setup fee.
Frequently Asked Questions
Common questions about direct network interconnection
No. You can use our ASN to announce your prefixes, or we can help you obtain your own through our RIPE LIR services if needed.
Yes. We support native dual-stack BGP for both IPv4 and IPv6.
AS-PATH filtering, prefix lists, BGP communities, MED, local preference. We filter routes against RPKI validation and IRR records for security.
24-48 hours after route object verification.
Yes. BFD is available for sub-second failover detection.
Yes. We offer remote peering options in addition to on-net peering. However, we do not accept peering over tunnels (GRE, IPsec, VXLAN, etc.) or similar overlay technologies. Remote peering must be established through direct cross-connects or private Layer 2 interconnection.
Yes, for AS35661 peers meeting the requirements above: settlement-free, no minimum traffic, no setup fee. We maintain an open peering policy; requirements are listed in the Setup section above.
Talk BGP with an engineer
Bring your own ASN or announce your prefixes through ours. Production-grade BGP-4 sessions with 24/7 NOC support.