Multihoming in Brazil means at least two upstreams and, in practice, IX.br as a third path. The architecture that holds is one transit provider per physical route, peering for the domestic share, and communities to steer inbound traffic.
The common mistake is buying two upstreams that meet in the same building. Check where the circuits physically land before you call it redundant.
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.
More on Brazilian connectivity, from the same series:
Or start from all services.
Multihoming is the point at which a network stops depending on one supplier's good day. Two upstreams, your own ASN, your own prefixes announced to both — and traffic that keeps flowing when one of them has a problem you cannot see and cannot fix.
Two upstreams into the same router leave you with a single point of failure that no BGP configuration can route around. Two routers is the honest version. Two routers in two locations is the version that also survives a power event.
Taking the full table from both gives you the most control and demands the most from the hardware. Taking a default route from both is cheap and gives up most of the benefit. Partial plus default is the middle ground most networks land on: enough to make good decisions about the destinations that matter, without carrying everything.
Outbound is easy — you decide. Inbound is decided by everyone else, and your only real levers are AS path prepending, communities offered by your upstreams, and more specific announcements used sparingly. Prepending is blunt and slow to converge. Communities are precise and underused, and are worth asking your upstreams to document before you sign.
IX.br changes the calculation here. A large share of domestic traffic is reachable through the exchange, so a Brazilian multihoming design is usually two transit providers plus an exchange port, not just two providers. That third leg often carries more traffic than either paid upstream, and it costs a fraction of what the equivalent transit would.
Diversity also has to be checked physically. Two upstreams whose fiber runs down the same highway are not diverse, and in Brazil that is a common accident rather than a rare one.
Announce only what is yours, accept only what you should. Build prefix filters from IRR data and keep them current, apply maximum-prefix limits so a neighbour's mistake does not become your outage, and validate with RPKI where your upstreams support it. Most famous BGP incidents were a missing filter rather than an attack.
JCM Carrier is a neutral multicarrier operator in Brazil. Send us an address and we map every route that can actually deliver there, then come back with price, lead time and SLA — normally within two business hours, and with no CNPJ required to start.
See also: IP transit in Brazil · peering vs IX.br · network redundancy
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.