Summary
- The São Paulo admission page prints that participation is open to any autonomous system, with a trailing asterisk; the asterisk resolves into a signed interconnection contract terminable by either party on 30 days' notice, a cap of twenty announced prefixes unless justified, a duty to keep registration data current, and a power to disconnect every port involved in malicious activity or port scanning.
- One exit route is dated and symmetric, two are immediate and one-sided; the port is priced by capacity in three cities while the route server that validates each announcement against Registro.br or another registry's data, IRR objects and RPKI charges nothing and cuts nobody off — it tags the announcement invalid and leaves the decision to the participants.
The sentence and the asterisk
The admission page for São Paulo (adesao/sp) prints it plainly: "A participação é aberta a qualquer Sistema Autônomo* que desejar trocar tráfego em uma localidade do IX.br." Any autonomous system that wishes to exchange traffic at an IX.br location, with an asterisk at the end.
That asterisk is not a footnote about tariffs. The same page sets the order of operations — choose a PIX, arrange the physical interconnection, request activation in the meu.ix.br portal, sign a participation contract, meet the technical requirements — and notes that São Paulo, Rio de Janeiro and Fortaleza are the locations where participation carries a cost. Money is disclosed on the surface, in a table with a date. The asterisk points somewhere else: at the contract and at the two policies the contract pulls in behind it.
What the asterisk resolves into
The published model interconnection contract (Modelo de Contrato de Interligação de Sistemas Autônomos), version 1.0 dated 30 June 2017, sits between NIC.br and an IX.br participant for the interconnection of autonomous systems. It states the network's ASN, the route-server-or-bilateral condition, BGP4 and compliance with the technical-requirements and acceptable-use policies. It also prints an exit that runs both ways: "As partes poderão rescindir o presente contrato, a qualquer tempo, desde que a parte interessada comunique a outra com 30 (trinta) dias de antecedência." Either party, any time, thirty days.
Then come the powers that do not wait thirty days. The same contract, in the retained document set, provides blocking and termination for non-payment after 60 days, immediate disconnection or quarantine by the NOC where the policy is breached, and blocking and termination for repeated or bad-faith breaches.
The technical-requirements policy (Política de Requisitos Técnicos), version 1.0 of the same date, states that Registro.br manages IP numbers and ASNs in Brazil and that participants and CIX operators must keep their registration data current. It caps each participant's announcements at twenty prefixes — "Cada Participante deverá anunciar no máximo 20 prefixos, contudo, esse limite poderá ser revisto desde que devidamente justificado" — prohibits default routes and advertisement of the IX.br LAN address space, requires authorisation for announced resources, and requires NEXT_HOP_SELF for routes learned at the exchange.
The acceptable-use policy (Política de Uso Aceitável), version 1.0 of the same date, requires participants to keep their ports fairly available and follow the technical requirements, and prints this: "O NIC.br se reserva o direito de desconectar todas as portas envolvidas em atividades maliciosas, e/ou varredura de portas." All the ports involved. Not the offending session alone: the ports.
The technical rules page (regras) opens with the entry condition in five words — "ASN; Possuir e operar um sistema autônomo." Possess and operate an autonomous system — then requires a multilateral agreement through the route server or direct bilateral sessions, BGP4, NEXT_HOP_SELF when announcing other participants' prefixes, broadcast limited to ARP resolution, and no default route and no use of another network's resources without authorisation.
One exit is dated. Two are immediate and one-sided.
Count the exit routes and the asymmetry is the story. The contract gives either party termination at any time on thirty days' notice: dated, symmetric, and usable by a network that wants out. The NOC power to disconnect or quarantine for a policy breach is immediate. The acceptable-use power to disconnect every port involved in malicious activity or port scanning is immediate. Both of those run one way, and both are triggered by a judgement the operator makes.
That is not a scandal; it is a specification. An exchange that could not cut a port during a scan would be a liability to everyone on the fabric. But it settles what the word "open" is doing in that sentence: open describes who may ask, not what happens after the answer. What I did not find matters too — no refusal, suspension, disconnection, quarantine or blocking decision, notice or record was read here, so this is the instrument as printed, not a practice observed.
The filter that degrades instead of disconnecting
The BGP-communities policy (tratamento de communities), v3.0 and undated, describes the route server validating each announcement's origin against Registro.br or RIR allocation data, IRR route objects and RPKI, and marking the result valid, invalid or unknown through BGP communities. The retained excerpt states the purpose: "um prefixo cujo anúncio foi originado por um determinado AS foi realmente designado a ele pelo Registro.br ou um RIR."
Read the consequence carefully, because it is the most interesting instrument on the fabric. An announcement that fails the test is not pulled off the exchange and the port is not cut. It is tagged, and the participants decide what to do with a tag. The operator degrades information; the operators of the networks decide reachability. That is a milder lever than a port cut, and it is the one that runs continuously, on every announcement, without a notice period and without an accusation.
The record-keeper is inside the fabric
NIC.br's own profile page (perfil) describes a private, non-profit civil entity responsible for operating the .br domain and for distributing IP numbers and registering autonomous systems in Brazil, with Registro.br and IX.br among its units, and describes IX.br as a CGI.br and NIC.br initiative. A second page (atividades do Registro.br) records a cooperation agreement with LACNIC under which IPv4, IPv6 and ASN resources for Brazil remain NIC.br's responsibility while LACNIC acts as the regional registry for Latin America and the Caribbean. A third (endereços IP e ASNs) calls NIC.br, through Registro.br, a National Internet Registry sharing LACNIC's pool and applying the same regional distribution rules, with the hierarchy running from IANA to LACNIC to national registries and then to providers. Registro.br's numbering rules (regras e políticas de numeração) justify an ASN for an organisation multihomed across two or more independent transit providers that needs dynamic routing, or one whose routing policy is distinct from its providers'.
So the entity that keeps the registration records the fabric validates against also runs the fabric. That coincidence is real, and it is narrower than I expected when I started.
I went looking for a title check that would accept only resources allocated by Registro.br — a door that opens on the registry's own paperwork. The policy as I read it does not say that. It validates origin against Registro.br or another RIR, plus IRR objects and RPKI. A prefix allocated by a registry NIC.br does not operate can pass the origin check at São Paulo. The Brazilian registry's role in this filter is about where records are kept and kept current, not about exclusivity at the door, and printing that correction is more useful than defending the premise it replaces.
What the port costs, and what the price does not buy
The price table dated 1 October 2026 (TBV IX.br SP/RJ/CE) prints monthly recurring charges by port: R$115 for 1G, R$690 for 10G, R$3,450 for 100G and R$10,350 for 400G, a CIX connection at R$115, one-time charges of R$300 for PIX migration and R$80 for bilateral VLAN configuration. It covers São Paulo/SP, Rio de Janeiro/RJ and Fortaleza/CE, taxes included, and notes that payments from abroad may carry additional taxes and expenses. The 100G row shows its components — 50,00 and 3.400,00, total 3.450,00. The addition is mine and it closes.
The FAQ (faq) adds the funding line: "Com relação as demais localidades o NIC.br, que é quem opera o IX.br, atualmente não cobra nada dos participantes", with investments and operating costs covered by .br domain registration revenue, and a note that participants may still pay third parties for transport, colocation or cross-connects. Three cities with a price, the rest without one, funded out of domain registrations.
Two printings exist and one publisher printed both. The FAQ's price answer links to a table dated 1 September 2023; the table retrieved separately is dated 1 October 2026, and its 400G total is R$13,800 in the earlier printing against R$10,350 in the later one. That is a change between two documents, not a contradiction inside one, and the FAQ carries no visible last-update date. Both printings are reported here and neither is adopted as the current price list.
What the numbers count
The participant figure (participantes de São Paulo) reads "IX.br - São Paulo - 2712 Participantes", last updated 2026-11-08 12:00. Participants are not ASNs and not ports.
The port inventory comes from the IX.br engineering update of 17 December 2025 (atualização 2025): 4,983 participant ports, of which 239 at 1G, 2,902 at 10G, 1,795 at 100G and 47 at 400G. The addition is mine — 239 + 2,902 + 1,795 + 47 = 4,983 — and it reproduces the printed total. The same deck reports 190 PIX points of presence, 493 network equipment units, 168 servers, and year peaks of 46.6 Tbit/s nationally and 30.4 Tbit/s at São Paulo. Its port table does not make the São Paulo scope unambiguous in the extracted text, so 4,983 is used here as a national composition figure, not a São Paulo count.
Traffic comes from NIC.br's release of 20 March 2026 (50 Tbit/s): 50 Tbit/s of aggregate traffic that month, 32 Tbit/s of it at São Paulo, across 39 metropolitan areas, with about 3.8 thousand participating autonomous systems and about 7 thousand connections, and more than 2.5 thousand directly connected networks in São Paulo. That is a record at the time of publication, not a standing peak. The forum deck dated 14 August 2026 (IX Fórum Regional) reports 39 locations, 3,871 participating ASNs and 55 Tbit/s nationally, and lists São Paulo at 35 Tbit/s with 2,696 ASNs.
The exchange's own São Paulo traffic page (tráfego agregado) exists, headed "Agregado total (São Paulo)", with a last-update stamp of 2026-11-11 17:00. No numeric value was captured from it, so no peak is attributed to that page here.
Keep the objects apart. 2,712 participants, 2,696 ASNs in the August deck and about 3.8 thousand participating systems nationally are three counted things, not one. About 7,000 connections and 4,983 ports are two more. Aggregate traffic is not capacity, and no capacity total is computed. No port count is multiplied by any price in this article and no revenue figure is derived.
What is new here
Prior coverage, measured on 18 November 2026: a briefing published 19 September 2026 reads IX.br and NIC.br access arrangements through PIX and CIX as a recovery question; a research article published 29 July 2026 reads a 400G core decision behind IX.br São Paulo through one named engineer; a company profile published 10 July 2026 places a small provider's fibre footprint through the exchange. None of the three reads admission, pricing or disconnection as an instrument. This one does, provision by provision, and the delta is exactly that reading.
What I read, and what I did not
- The model contract, the technical-requirements policy and the acceptable-use policy are version 1.0 dated 30 June 2017. Whether a later revision governs current admissions was not verified; they are described as the published model and the versions read.
- The communities policy read is v3.0 and undated. A v4.4.2 dated 27 October 2026 was noted in the documentation material and was not obtained, so the validation set described here may have changed.
- The technical rules page is a web summary. The three policies and the model contract were read through search-indexed PDF text rather than a direct PDF rendering.
- No numeric São Paulo aggregate was captured from the traffic page; only the page, its series heading and the 2026-11-11 17:00 stamp are asserted.
- No refusal, suspension, disconnection, quarantine or blocking decision, notice or record was read, and nothing is asserted about whether any of those powers has ever been exercised or against whom.
- No appeal, hearing or dispute-resolution provision was read. That is a statement about what I read, never that none exists.
- No Brazilian statute, decree, Anatel regulation or competition-authority decision on exchange access, interconnection or National Internet Registry functions was read.
- No participant contract actually signed by any network was read; the contract discussed is a published model.
- The FAQ has no visible last-update date, and its price answer links to the 1 September 2023 table; both printings are reported and neither is adopted as current.
- The 400G difference between printings is reported as a change between two documents, not as a contradiction inside one.
- No RPKI repository or IRR database was queried; the communities policy is read as text and was not tested against live announcements.
- The 4,983 ports come from a 2025 engineering presentation and are used as a national composition figure only.
- The March 2026 release describes a record at the time of publication.
- Everything here is a reading of documents obtained on 18 November 2026; retrieval limits are facts about access, not about the institutions.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






