ixreport

GILEADE TELECOMUNICACOES E MULTIMIDIA

AS271263 · Gileade Telecom

GILEADE TELECOMUNICACOES E MULTIMIDIA LTDA

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
2Using the route servers
0Facilities in PeeringDB

Tools: Where can I peer with GILEADE TELECOMUNICACOES E MULTIMIDIA? · Where should GILEADE TELECOMUNICACOES E MULTIMIDIA peer next? · Compare GILEADE TELECOMUNICACOES E MULTIMIDIA with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list

Nothing to fix: GILEADE TELECOMUNICACOES E MULTIMIDIA's PeeringDB record matches the member lists of the 2 exchanges we could compare.

Exchanges over time

012Oct 3, 2026Nov 19, 20262
Show as a table
DateExchanges
Nov 19, 20262
Nov 18, 20262
Nov 17, 20262
Nov 16, 20262
Nov 15, 20262
Nov 14, 20262
Nov 13, 20262
Nov 12, 20262
Nov 11, 20262
Nov 10, 20262
Nov 9, 20262
Nov 8, 20262
Nov 7, 20262
Nov 6, 20262
Nov 5, 20262
Nov 4, 20262
Nov 3, 20262
Nov 2, 20262
Nov 1, 20262
Oct 31, 20262
Oct 30, 20262
Oct 29, 20262
Oct 28, 20262
Oct 27, 20262
Oct 26, 20262
Oct 25, 20262
Oct 24, 20262
Oct 23, 20262
Oct 22, 20262
Oct 21, 20262
Oct 20, 20262
Oct 19, 20262
Oct 18, 20262
Oct 17, 20262
Oct 16, 20262
Oct 15, 20262
Oct 14, 20262
Oct 13, 20262
Oct 12, 20262
Oct 11, 20262
Oct 10, 20262
Oct 9, 20262
Oct 8, 20262
Oct 7, 20262
Oct 6, 20262
Oct 5, 20262
Oct 4, 20262
Oct 3, 20262

Map

Where GILEADE TELECOMUNICACOES E MULTIMIDIA's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 20G across 2 exchanges.

Brazil IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil 45.68.81.181 2001:12f8:0:2::53:181 10G 5 routes Both
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.213.17 2001:12f8::213:17 10G 5 routes PeeringDB only

GILEADE TELECOMUNICACOES E MULTIMIDIA lists no facilities in PeeringDB.