Interconnection
AS263444 Open X Tecnologia Ltda
Unclassified LACNIC
Recorded presence
Internet exchanges
Internet exchanges where Packet Clearing House has a port recorded for AS263444, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's page, with its peering LANs and everyone else on it.
North America 5 Latin America 3 Europe 2
| Exchange | Location | Their address | Policy | Member ports |
|---|---|---|---|---|
| IX.br (PTT.br) São Paulo | São Paulo, Brazil | 187.16.214.191 | Open | 2,704 |
| IX.br (PTT.br) Fortaleza | Fortaleza, Brazil | 45.68.72.146 | — | 939 |
| DE-CIX New York | New York, United States | 206.82.104.229 | Open | 285 |
| NetIX | Sofia, Bulgaria | 185.1.226.203 | Open | 264 |
| IX.br (PTT.br) Curitiba | Curitiba, Brazil | 45.184.146.19 | — | 250 |
| New York International Internet Exchange | New York, United States | 2001:504:1::a526:3444:1 | Open | 213 |
| Peering.cz | Prague, Czech Republic | 2001:7f8:7f::c:54 | Selective | 211 |
| FL-IX - The Florida Internet Exchange / Community IX - Florida | Miami, United States | 206.41.108.121 | Open | 181 |
| Equinix Internet Exchange Miami | Miami, United States | 198.32.243.119 | Open | 178 |
| Equinix-LA(former Paix) retired | Los Angeles, United States | 198.32.243.119 | Open | — |
Recorded rather than inferred: an address on a peering LAN is at that exchange by definition. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. An absent exchange means PCH has no record of it, not that the network is not there. For the operator's own claims, see its PeeringDB record.
From the exchange directory collected 2026-10-13 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,177 recorded member ports, licensed CC BY-NC-SA 3.0.
PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.