ixreport

SATCORE

AS219384

Satcore LLC

1Exchange
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
Network ServicesType
SelectivePeering policy
0Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with SATCORE? · Where should SATCORE peer next? · Compare SATCORE 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 SATCORE's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 UTC.

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If SATCORE has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Türkiye GIBIRIX İstanbul, Türkiye · PeeringDB 3659Not on its website members list
    IPv4185.1.221.61
    IPv62001:7f8:11d::61
    Speed100000 Mbps (100G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

Exchanges over time

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

Map

Where SATCORE'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 100G across 1 exchange.

Türkiye GIBIRIX İstanbul, Türkiye 185.1.221.61 2001:7f8:11d::61 100G PeeringDB

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

These exchanges have a switch in a facility where SATCORE lists itself in PeeringDB, but don't have SATCORE 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.

Germany ERA-IX FrankfurtFrankfurt, Germany 85 TornadoDC - FRA1
Türkiye DE-CIX IstanbulIstanbul, Türkiye 72 DATACASA DC IST-1
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 DATACASA DC IST-1
Türkiye TurkIX IstanbulIstanbul, Türkiye 3 DATACASA DC IST-1
Facilities (2)

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

Türkiye DATACASA DC IST-1Istanbul 1 of 4
Germany TornadoDC - FRA1Langen 0 of 1