Two endpoints, one transparent circuit
The simplest service and where most customers start, whether it carries replication, a peering handoff or an internal VLAN stretched between two of your own rooms. Delivered as EVPL.
Transparent Ethernet between our European sites over EVPN-MPLS - tags intact, MTU intact, no addressing or routing decisions in between. What runs inside the circuit is entirely yours.
A Layer 2 service from us is a transparent pipe between ports on our network. We do not look inside it, we do not learn anything from it that we need to tell you about, and we do not renumber anything at either end.
> show l2circuit customer-a encap dot1q + QinQ transparent your vlans 1-4094 untouched your macs learned in control plane # we carry frames; what they mean is yours
EVPN-MPLS carries these circuits over the same backbone as the IP services - the same diverse paths, the same capacity planning. It is also why a multipoint service gains a site without touching the endpoints that are already up: MAC learning lives in the control plane, not flooded across the fabric.
Where a route has physical diversity we deliver the circuit protected. Where it does not, we say so before you order - and you decide whether your own equipment should handle failover instead.
The simplest service and where most customers start, whether it carries replication, a peering handoff or an internal VLAN stretched between two of your own rooms. Delivered as EVPL.
Every location on the service sees every other. Add a site later and it joins the existing domain without a change on the endpoints that are already up. Delivered as EVPN.
Rooted multipoint, which is what you want when aggregating branch or customer traffic into one core site and those spokes have no business talking directly. Delivered as EVPN.
Most Layer 2 customers hold at least one of these beside the circuit - the combinations below are the ones that actually happen.
When the E-Line is permanently full, the same corridor sells as a dedicated wavelength - your own channel, same endpoints, no re-engineering of the path. DWDM wavelengths →
A circuit between two sites plus transit at one or both of them - delivered on the same physical handoff, with the DDoS filter in front of every announced prefix. Protected IP transit →
Replication rides the circuit; the public faces of both sites sit behind the same mitigation. One attack cannot follow your failover, because both ends were protected before it started. DDoS protection →
Your VLAN tags survive untouched (dot1q and QinQ), your MACs are learned in the control plane rather than flooded, and we neither inspect nor renumber anything. We carry frames; what they mean is yours.
Up to 9000 bytes end to end - path dependent, and confirmed before turn-up rather than assumed, because a jumbo circuit that silently fragments is worse than an honest 1500.
Yes - E-LAN and E-Tree run on EVPN, so a new site joins the existing domain without touching the endpoints that are already up.
Sub-50 ms switching where the route has physical diversity; stated plainly where it does not, so you can decide if your own equipment should handle failover.
Y.1731 and 802.1ag OAM, with per-circuit graphs visible to you - the same telemetry we watch, not a monthly PDF.
This site sets zero cookies - no analytics, no trackers, no profile of you. The only third-party requests are the fonts, served by Google Fonts, and the spam check on the contact form. Everything else stays between your browser and our network - the full privacy note.