ixreport

ISP SHIELD

AS61624 · INFNOC // ISP SHIELD

INFNOC NETWORKS

9Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
9Using the route servers
1To fix in PeeringDB
8Facilities in PeeringDB

Tools: Where can I peer with ISP SHIELD? · Where should ISP SHIELD peer next? · Compare ISP SHIELD with another network

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

PeeringDB fix list Printable page · CSV

One thing to fix in ISP SHIELD's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on ISP SHIELD's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in ISP SHIELD's PeeringDB record. Add one entry per connection with these values.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export and website members list
    IPv480.81.195.202
    IPv62001:7f8::f0b8:0:1
    Speed100000 Mbps (100G)
    RS peerYes

Exchanges over time

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

Map

Where ISP SHIELD'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 390.25G across 9 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.209.80 2001:7f8:1::a506:1624:1 250M Down Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.195.202 2001:7f8::f0b8:0:1 100G Down Not in PeeringDB
United States DE-CIX New York New York, United States 206.82.104.27 2001:504:36::f0b8:0:1 20G Down Both
Brazil IX.br (PTT.br) Brasília Brasília/DF, Brazil 45.184.145.44 2001:12f8:0:13::145:44 10G 242 routes PeeringDB only
Brazil IX.br (PTT.br) Curitiba Curitiba, Brazil 45.184.147.26 2001:12f8:0:4::147:26 10G 242 routes PeeringDB only
Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil 45.68.74.240 2001:12f8:0:9::146:240 20G 254 routes PeeringDB only
Brazil IX.br (PTT.br) Porto Alegre Porto Alegre/RS, Brazil 177.52.38.238 2001:12f8:0:6::238 10G 242 routes PeeringDB only
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.212.140 2001:12f8::212:140 200G 255 routes PeeringDB only
Paraguay PIT Paraguay Ciudad del Este, Paraguay 45.68.95.20
45.68.95.33
2801:10:400:595::20
2801:10:400:595::33
2 × 10G Yes PeeringDB

Exchanges in its buildings that it isn't on (6)

These exchanges have a switch in a facility where ISP SHIELD lists itself in PeeringDB, but don't have ISP SHIELD as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (8)

The buildings ISP SHIELD lists in PeeringDB, and how many of the exchanges in each it's on.

Brazil Equinix SP4 - São PauloBarueri 1 of 6
Brazil Ascenty SPO02 - São PauloOsasco 1 of 4
Brazil Ascenty FTZ01 - FortalezaMaracanaú 1 of 2
Brazil Ascenty SPO04 - São PauloOsasco 0 of 2
Brazil Ascenty SPO03 - São PauloOsasco 0 of 1
Paraguay WIND NET CDE1Ciudad del Este 1 of 1
Paraguay WIND NET HDR1Hernandarias 1 of 1
Brazil Ferenz Networks DCXaxim No exchange