Carrier Ethernet: private L2 circuits in Riga

A VPN rides the public internet, so your traffic shares the path with everyone else and inherits whatever congestion, packet loss and jitter that path has on a given day. Encryption also adds tunnelling overhead on your routers. A Carrier Ethernet circuit is a private Layer 2 path: your frames never touch the public internet, latency stays where you measured it, and the contract includes availability and repair time commitments instead of best effort. A VPN is still fine for occasional remote access; when VoIP, replication or trading traffic needs predictable behaviour every day, a private circuit is the right tool.

Yes, and that is the most common design: a point-to-point link from your office straight into our data centre in Riga, so the circuit ends next to your servers, backups and cloud resources. In practice this means your office network and your hosted equipment behave like one local network, without tunnels and without exposing anything to the public internet. It also simplifies day-to-day work such as replication and moving large backups, because that traffic stays on the private path. Name your office address in the quote request, and during the feasibility step we confirm reach and media all the way to your site.

The range goes from modest links for branch offices up to multi-gigabit trunks, and the honest answer is that the achievable speed depends on the two endpoints. Reach, the available media at each site and the capacity on the route set the ceiling, which is why we run a feasibility check first. Tell us the two sites and the target speed, and we confirm what is actually deliverable before you commit to anything. If you are not sure what speed you need, describe the workload, for example backup windows or replication volume, and we will size the link together with you.

Yes. Every circuit is monitored with alerting on circuit health, so a fault shows up on our side without you having to notice it first and call. The SLA that comes with the circuit defines both availability and repair times, which means a fault is worked against committed deadlines rather than whenever it is convenient. Monitoring covers the circuit itself, the path between your two ports; everything behind the ports, your VLANs, routing and equipment, remains your responsibility. If you see anything odd, write to support and we will tell you the current state of the circuit and what is being done about it.

E-Line is the point-to-point service type in the MEF Carrier Ethernet framework: a private Layer 2 Ethernet connection between exactly two sites. You get an Ethernet port at each end, and everything you send into one port comes out of the other, which is why it is often described as one long cable. Because the service works at Layer 2, there is no routing on our side: your VLANs, your IP addressing, your routing protocols and your equipment stay entirely under your control. The limitation is in the name: it connects two sites, so a design with three or more locations needs more than one circuit.

There is no fixed price list, because the two endpoints and the bandwidth drive most of the cost: how far apart the sites are, what media is available at each of them and how much capacity you want on the route. That is why the process starts with a quote rather than a shop page. Send us your two sites and the target speed, and you receive the circuit design, the monthly price and the SLA terms in one offer. Requesting a quote does not commit you to anything, so it is also a practical way to compare the offer against your current connectivity.

Yes. The transport is VLAN transparent: the tags you send into the port at one site come out unchanged at the other, so your existing segmentation keeps working end to end. You do not renumber anything, you do not register your VLAN plan with us, and you do not coordinate changes: add or remove VLANs on your own schedule and the circuit simply carries them. This matters in practice because office networks and server networks usually already have a VLAN structure, and a circuit that forced you to rebuild it would be expensive in time. Your switches and routers at both ends remain yours to configure.

Yes. Within the capacity of the delivered ports and the route, a bandwidth upgrade is a configuration change on our side, not a new construction project: no new cabling, no site visit, no second installation. In practice you write to support, we confirm the new speed and the adjusted monthly price, and the change is applied to the existing circuit. That is why it is sensible to start with the bandwidth you need today instead of overbuying for the future. If a requested speed ever goes beyond what the current media can carry, we tell you that during the feasibility check and offer a design that can.