Summary

  • IX.br describes participation through a network’s physical port at a PIX or through a CIX shared-port provider. These are access arrangements, not a comparative reliability rating.
  • Before treating another connection as a recovery path, a participant should establish its relevant physical dependencies, usable capacity and activation authority. The access descriptions do not establish those participant-specific facts.

A second port is not necessarily a second way out of a failure. If two connections depend on the same failed element, counting them separately does not make that element avoidable. Conversely, a shared access arrangement should not be presumed unable to support continuity merely because it is shared. The useful starting point is a specified failure and the service that must survive it.

For networks considering IX.br access, that distinction separates a connection decision from a recovery assessment. It also prevents an institutional description from being mistaken for a participant-level guarantee.

How IX.br describes access

NIC.br describes IX.br as an initiative of CGI.br and NIC.br that installs and operates traffic exchange points and provides infrastructure for direct interconnection between autonomous systems. That describes the exchange initiative’s role; it does not settle the availability of an individual participant’s path to it.

IX.br’s CIX joining guidance describes participation through a physical port for an autonomous system at a PIX, or through a CIX, identified as a shared-port provider. The distinction concerns how the participant reaches the exchange. It should not be expanded into an assertion that one option has an independent transport path, a particular recovery time or superior availability.

The IX.br glossary places the physical hosting role at the PIX: data centres or telecommunications operators provide an environment for IX.br equipment and connectivity, such as links or cross-connects, through which participants reach the exchange infrastructure. It describes a CIX as allowing multiple autonomous systems to share a single connection to IX.br.

These descriptions identify useful places to ask questions. At the PIX, the questions concern the facility and connectivity on which access depends. For a CIX connection, they also concern the shared connection and the participant’s usable alternatives. The definitions are not a complete allocation of repair duties, contractual obligations or authority to change traffic paths.

Start with the failure, not the port count

Consider a hypothetical participant with two connections. If both traverse a transport segment that becomes unavailable, the second connection does not avoid that particular failure. If they avoid that segment but depend on the same unavailable participant-side equipment, transport diversity alone would not preserve the service. These are conditional examples, not findings about an IX.br participant’s topology.

The corresponding question for shared access is equally specific. If several participants depend on a connection that becomes unavailable, their continuity depends on the alternatives each can actually use. The word shared identifies a dependency to examine. It does not reveal whether those participants have other connections, whether those connections remain available, or how much traffic they could carry.

For either arrangement, a recovery assessment therefore needs to move through three questions: what failed, what remains usable, and what action would restore the required service? A diagram showing another line answers only part of that sequence. A proposed alternative must also be available to the participant, capable of carrying the required traffic under the chosen conditions, and capable of being activated when needed.

Authority deserves its own place in that assessment. The party able to repair an element need not be the party authorised to move traffic or activate an alternative. Participants should identify those roles rather than assigning all of them to NIC.br, a PIX host or a CIX provider on the strength of an access label.

The boundary of the conclusion

The access descriptions do not establish measured participant availability, independent physical paths, spare capacity or failover times. They cannot support a reliability ranking between a participant’s own port and a shared connection. Equally, the absence of those measurements from this discussion does not establish that such capabilities or documentation are absent from IX.br’s operations.

This is an explanation of access dependencies, not a report of a newly verified outage or a performance audit. Its bounded conclusion is practical: use the PIX and CIX descriptions to locate the questions that matter, then assess recovery against an explicit failure scenario. Count an alternative as usable only to the extent that evidence supports the service it is expected to preserve.

Related directory entry: NIC.br.