ixreport

SP9SKA

AS218241

1Exchange, of which 1 VIX
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
1Using the route servers
1To fix in PeeringDB

This network has no PeeringDB record; it was found on exchanges' own member lists.

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

AS218241 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (1)

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

  1. United States EVIX Fremont, United States · PeeringDB 2274From its IX-F export and website members list
    IPv4206.81.104.37
    IPv62602:fed2:fff:ffff::37
    Speed1000 Mbps (1G)
    RS peerYes

    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

01Nov 14, 2026Nov 19, 20261

Collecting since Nov 14, 2026: one point a day, so this fills in as the days go by.

Show as a table
DateExchanges
Nov 19, 20261
Nov 18, 20261
Nov 17, 20261
Nov 16, 20261
Nov 15, 20261
Nov 14, 20261

Map

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

United States EVIXVIX Fremont, United States 206.81.104.37 2602:fed2:fff:ffff::37 1G Down Not in PeeringDB

Recent changes Search them

  • Nov 15, 2026 [WEB] AS218241 SP9SKA now on EVIX's website list
  • Nov 14, 2026 [IXF] AS218241 SP9SKA added to EVIX