ixreport

Misaka Network, Inc.

AS57695 · Misaka.io

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

Tools: Where can I peer with Misaka Network, Inc.? · Where should Misaka Network, Inc. peer next? · Compare Misaka Network, Inc. with another network

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

PeeringDB fix list Printable page · CSV

10 things to fix in Misaka Network, Inc.'s PeeringDB record, from what its exchanges publish: 5 to add, 5 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Misaka Network, Inc.'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 (5)

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

  1. United States FCIX Fremont, United States · PeeringDB 2163From its website members list
    IPv4206.80.238.48
    IPv62001:504:91::48
    SpeedNot published
    RS peerNot published
  2. United States HOUIX Houston, United States · PeeringDB 2835From its IX-F export and website members list
    IPv4206.83.136.19
    IPv62001:504:9e::19
    Speed40000 Mbps (40G)
    RS peerNot published
  3. Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil · PeeringDB 171From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  4. United States KCIX Kansas City, United States · PeeringDB 249From its IX-F export and website members list
    IPv4206.51.7.60
    IPv62001:504:1b:1::60
    Speed40000 Mbps (40G)
    RS peerNot published
  5. United States STLIX Saint Louis, MO, United States · PeeringDB 2585From its IX-F export and website members list
    IPv4206.83.12.37
    IPv62001:504:98::37
    Speed40000 Mbps (40G)
    RS peerNot published

Correct these entries (5)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 80.81.192.231: set Speed to 10000 (10G) (now 1000).
  2. Portugal DE-CIX Lisbon Lisbon, Portugal · PeeringDB 2531
    ProblemPeeringDB hasThe export has
    Port speed differs100M1G
    • In the entry with IPv4 185.1.131.48: set Speed to 1000 (1G) (now 100).
  3. United States HOUIX Houston, United States · PeeringDB 2835
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB206.83.136.19 is AS917 Misaka.io206.83.136.19
    Address belongs to another network in PeeringDB2001:504:9e::19 is AS917 Misaka.io2001:504:9e::19

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

  4. United States KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB206.51.7.60 is AS917 Misaka.io206.51.7.60
    Address belongs to another network in PeeringDB2001:504:1b:1::60 is AS917 Misaka.io2001:504:1b:1::60

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

  5. United States STLIX Saint Louis, MO, United States · PeeringDB 2585
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB206.83.12.37 is AS917 Misaka.io206.83.12.37
    Address belongs to another network in PeeringDB2001:504:98::37 is AS917 Misaka.io2001:504:98::37

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

Exchanges over time

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

Map

Where Misaka Network, Inc.'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 122.1G, at the 6 of 8 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.192.231 2001:7f8::e15f:0:1 1G Down Both Speed differs
Portugal DE-CIX Lisbon Lisbon, Portugal 185.1.131.48 2001:7f8:d5::e15f:0:1 100M Down Both Speed differs
Spain DE-CIX Madrid Madrid, Spain 185.1.192.193 2001:7f8:a0::e15f:0:1 1G Down Both
United States FCIX Fremont, United States 206.80.238.48 2001:504:91::48 Not in PeeringDB
United States HOUIX Houston, United States 206.83.136.19 2001:504:9e::19 40G Not in PeeringDB Address taken
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil Not in PeeringDB
United States KCIX Kansas City, United States 206.51.7.60 2001:504:1b:1::60 40G Not in PeeringDB Address taken
United States STLIX Saint Louis, MO, United States 206.83.12.37 2001:504:98::37 40G Not in PeeringDB Address taken

Misaka Network, Inc. lists no facilities in PeeringDB.