ixreport

SFO-IX

AS13094 · SFO-IX

Milecom LLC

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

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

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

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.233.30178.18.224.61 178.18.233.30
    IPv6 address missing from PeeringDB2a03:5f80:4:1::233:302a03:5f80:4::224:61 2a03:5f80:4:1::233:30
    Port speed differs10G2 × 10G
    • Add an entry: IPv4 178.18.224.61, IPv6 2a03:5f80:4::224:61, speed 10000 (10G), RS peer yes.

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

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

Map

Where SFO-IX'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 500G across 10 exchanges.

Russia CLOUD-IX EKT Ekaterinburg, Russia 31.28.29.19 2a00:13c0:3:9::1f1c:1d13 10G Yes PeeringDB
Russia DataLine-IX Moscow, Russia 185.1.52.39 2001:7f8:62:52::39 10G Yes PeeringDB
Ukraine DTEL-IX Kiev, Ukraine 193.25.180.212 2001:7f8:63::d4 10G Yes PeeringDB
Russia Eurasia Peering IX Moscow, Russia 185.232.60.124 2a0d:e180::60:124 100G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.233.30 2a03:5f80:4:1::233:30 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.209.36 2001:7f8:20:101::209:36 30G Yes Both
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.58 2001:7f8:20:401::87:58 20G Yes Both
Russia SFO-IX Barnaul, Novosibirsk, Russia 91.221.180.100
91.221.181.100
2a0b:9fc0:1:0:1:3094:180:100
2a0b:9fc0:1:0:1:3094:181:100
2 × 100G Yes PeeringDB
Russia Sibir-IX Krasnoyarsk, Russia 185.1.81.13 2001:7f8:ac:142::13 10G Yes PeeringDB
Russia W-IX Moscow, Russia 193.106.112.55 2a00:1b30::55 100G Yes PeeringDB

SFO-IX lists no facilities in PeeringDB.