ixreport

PHADE Software - PowerWeb

AS35053 · PowerWeb

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

Tools: Where can I peer with PHADE Software - PowerWeb? · Where should PHADE Software - PowerWeb peer next? · Compare PHADE Software - PowerWeb with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in PHADE Software - PowerWeb's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on PHADE Software - PowerWeb'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 (4)

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 MegaIX Berlin Berlin, Germany · PeeringDB 209
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8:5:0:88ed:0:1
    • In the entry with IPv4 194.9.117.31: set IPv6 to 2001:7f8:8:5:0:88ed:0:1 (now empty).

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

  2. Germany MegaIX Dusseldorf Dusseldorf, Germany · PeeringDB 91
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8::88ed:0:1
    • In the entry with IPv4 194.146.118.55: set IPv6 to 2001:7f8:8::88ed:0:1 (now empty).

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

  3. Germany MegaIX Frankfurt Frankfurt, Germany · PeeringDB 676
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8:20:0:88ed:0:1
    • In the entry with IPv4 62.69.146.25: set IPv6 to 2001:7f8:8:20:0:88ed:0:1 (now empty).

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

  4. Germany MegaIX Hamburg Hamburg, Germany · PeeringDB 291
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8:10:0:88ed:0:1
    • In the entry with IPv4 193.42.155.15: set IPv6 to 2001:7f8:8:10:0:88ed:0:1 (now empty).

    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

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

Map

Where PHADE Software - PowerWeb'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 1.3G across 4 exchanges.

Germany MegaIX Berlin Berlin, Germany 194.9.117.31 100M Yes Both IPv6 not in PeeringDB
Germany MegaIX Dusseldorf Dusseldorf, Germany 194.146.118.55 100M Yes Both IPv6 not in PeeringDB
Germany MegaIX Frankfurt Frankfurt, Germany 62.69.146.25 1G Both IPv6 not in PeeringDB
Germany MegaIX Hamburg Hamburg, Germany 193.42.155.15 100M Yes Both IPv6 not in PeeringDB

PHADE Software - PowerWeb lists no facilities in PeeringDB.