ixreport

STORMYCLOUDINC: PeeringDB fix list

AS400226 · peeringdb.com/net/28625

PeeringDB

2 things to fix in STORMYCLOUDINC's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on STORMYCLOUDINC'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 (2)

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
    IPv4 address missing from PeeringDBnone80.81.193.173
    Port speed differs10G100G
    • In the entry with IPv6 2001:7f8::6:1b62:0:1: set IPv4 to 80.81.193.173 (now empty); set Speed to 100000 (100G) (now 10000).
  2. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 206.82.104.102: set Speed to 100000 (100G) (now 10000).

From ixreport.com/net/400226/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.