Data-center interconnect
Extend a Layer 2 segment between two facilities so clusters, storage replication and failover behave as though they share a switch fabric.
Layer 2 transport
A transparent Layer 2 circuit between two points. Your VLANs, your frames, your Layer 3 — we move the packets and stay out of the way.
A point-to-point Layer 2 circuit connects two locations as though a very long patch cable ran between them. Frames enter one end and leave the other. There is no provider router in the path making decisions about your traffic, and no NAT, firewall or address translation to work around.
That makes it the right tool when you need two networks to behave like one network — replication, interconnect, exchange access, or simply extending a segment between buildings.
Circuits can also be combined with IP transit: dedicated point-to-point interconnection into the Network Edge backbone with AS7201 riding over the top, so your router does not have to live in the same building as the hand-off.
If your paperwork calls this something else, it is the same service. A port-based circuit — your own port, everything on it going to one place — is what the industry calls an Ethernet Private Line, or EPL. A VLAN-based circuit — one of your ports presenting several of your own circuits to several destinations, so you buy one hand-off instead of four — is an Ethernet Virtual Private Line, or EVPL. Both are private: the capacity is yours, and the only traffic on the port is yours. We sell both, and an RFP written in either vocabulary gets quoted without translation.
| Service layer | Layer 2 Ethernet, transparent |
| Also known as | Ethernet Private Line — EPL, or EVPL when one of your ports carries several circuits |
| Port speeds | 100M / 1G / 10G / 25G / 40G / 100G |
| Hand-off | Port-based or VLAN-based |
| Tagging | Untagged, single tag or trunked |
| Protocols carried | Any Ethernet payload, IPv4 and IPv6 |
| Jumbo frames | Supported where the path allows |
| Topologies | Site to site, site to data center, site to IXP |
| Diversity | Diverse physical paths available on request |
| Combined with | AS7201 IP transit |
Use cases
Extend a Layer 2 segment between two facilities so clusters, storage replication and failover behave as though they share a switch fabric.
Reach an exchange point from a site that is not in that building. Your port at the IX, your BGP sessions, delivered over our transport.
Move bulk replication traffic off your Internet circuit and onto dedicated transport where it will not compete with production.
Carry AS7201 IP transit from the hand-off point back to your own router, in your own rack, at your own site.
Connect a corporate network to a colocation footprint without putting that traffic on the public Internet.
Private network-to-network hand-off with a partner, supplier or downstream network.
Hand-off and design
Every circuit is engineered rather than picked off a menu. What we need from you is short:
Questions
Layer 2. The circuit is transparent Ethernet — we carry your frames between end points and do not participate in your Layer 3. Your addressing, routing protocols and VLAN plan stay yours.
Yes. Those are the Carrier Ethernet names for the same two ways of delivering it. A port-based circuit, where you get your own port and everything on it goes to one destination, is an Ethernet Private Line (EPL). A VLAN-based circuit, where one of your ports presents several of your own circuits to several destinations so you buy one hand-off instead of four, is an Ethernet Virtual Private Line (EVPL). Both are private and the capacity on either is yours. We sell both; tell us which you want, or describe what you need and we will tell you which one fits.
Yes. We can deliver a port-based circuit that carries all tags, or a VLAN-based circuit that carries specific tags, depending on how you want the hand-off structured.
Yes, where the underlying path supports it. Tell us the MTU your application needs and we will confirm what we can deliver on that route.
Data-center interconnect, replication and backup traffic, reaching an Internet exchange from a site that is not in that building, extending a network between offices and colocation, and carrying IP transit from a hand-off point back to a customer router.
Yes — a common design is dedicated point-to-point transport into the Network Edge backbone with AS7201 transit riding over it, so the customer router does not have to sit in the same building as the hand-off.
Tell us the capacity you need and where you need it. An engineer reviews every request and comes back with a design and a price.