Data centre interconnect in Brazil is normally delivered as layer 2 Ethernet between facilities, from 100 Mbps to 10 Gbps and above, with the route and the diversity being the part that actually needs specifying. It is quoted per route.
Ask one question before signing: are the two paths physically diverse, or do they share a duct? Diversity on paper that shares a trench is not diversity.
Brazil connectivity delivered by a neutral multicarrier operator. We map every route available at your address and come back with price, lead time and SLA.
Data center interconnect is the circuit between two facilities that carries your traffic as if the two rooms were one. It is what makes storage replication, live migration, active-active clusters and a real disaster recovery site possible — all of which assume a link that is predictable in latency and does not lose frames under load.
The distinction that matters commercially is layer. Layer 2 hands you a transparent Ethernet path: your VLANs, your addressing, your routing decisions, and the two sites behave like one broadcast domain if you want them to. Layer 3 hands you a routed service, which is easier to operate and scale but takes the addressing decisions out of your hands. Replication and clustering usually want layer 2. Most other things do not.
The dense part of the Brazilian data center market sits in the São Paulo metropolitan area, with Rio de Janeiro second and a growing set of regional facilities elsewhere. Inside a campus, interconnect is a cross-connect and a small monthly fee. Between metros it is a transport circuit and the price moves with distance and with how many carriers actually run that route.
The failure mode to plan around is shared infrastructure. Two circuits from two different suppliers can still ride the same physical duct on the same stretch of highway, which means one excavator takes both down at once. If diversity is the reason you are buying the second circuit, it has to be verified on the route, not assumed from the logo on the invoice.
Carrier-neutral, so the answer reflects which carriers actually run between the two facilities you named rather than which one we would prefer to sell. We map the routes available at both addresses and come back with price, lead time and SLA, normally within two business hours. No CNPJ required to start.
Related: L2 transport · cloud connect · data center connectivity · network redundancy · the Miami corridor
Dedicated IPLC and Ethernet private line between Portugal and Brazil, with presence in Lisbon, Madrid, Milan and Frankfurt through the operators in our group and partner networks. Contractual SLA, 24/7 NOC, 100 Mbps to 10 Gbps+. We accept payment in USD and EUR.
Group network: AS14840 (5–10 Tbps, 60 Hudson and Equinix Miami) and AS269311 (100 Gbps at IX.br Rio, at the Globenet cable landing station). Both on PeeringDB.
RFQ by email: [email protected] · NOC 24/7: [email protected]
Send us the address. We check which carriers can actually deliver there and reply with price, lead time and SLA. Reply within 2 business hours.