GOPAS Solutions
AS13157
GOPAS Solutions GmbH
Tools: Where can I peer with GOPAS Solutions? · Where should GOPAS Solutions peer next? · Compare GOPAS Solutions with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
6 things to fix in GOPAS Solutions's PeeringDB record, from what its exchanges publish: 6 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on GOPAS Solutions'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 (6)
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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:1::a501:3157:1 Port speed differs 200M 100M - In the entry with IPv4 80.249.211.22: set IPv6 to 2001:7f8:1::a501:3157:1 (now empty); set Speed to 100 (100M) (now 200).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8::3365:0:1 Port speed differs 200M 1G - In the entry with IPv4 80.81.194.189: set IPv6 to 2001:7f8::3365:0:1 (now empty); set Speed to 1000 (1G) (now 200).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:3d::3365:0:1 - In the entry with IPv4 185.1.210.32: set IPv6 to 2001:7f8:3d::3365:0:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:8:5:0:3365:0:1 - In the entry with IPv4 194.9.117.57: set IPv6 to 2001:7f8:8:5:0:3365: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:8::3365:0:1 - In the entry with IPv4 194.146.118.86: set IPv6 to 2001:7f8:8::3365: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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:8:10:0:3365:0:1 - In the entry with IPv4 193.42.155.36: set IPv6 to 2001:7f8:8:10:0:3365: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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 6 |
| Nov 17, 2026 | 6 |
| Nov 16, 2026 | 6 |
| Nov 15, 2026 | 6 |
| Nov 14, 2026 | 6 |
| Nov 13, 2026 | 6 |
| Nov 12, 2026 | 6 |
| Nov 11, 2026 | 6 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 6 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 6 |
| Nov 5, 2026 | 6 |
| Nov 4, 2026 | 6 |
| Nov 3, 2026 | 6 |
| Nov 2, 2026 | 6 |
| Nov 1, 2026 | 6 |
| Oct 31, 2026 | 6 |
| Oct 30, 2026 | 6 |
| Oct 29, 2026 | 6 |
| Oct 28, 2026 | 6 |
| Oct 27, 2026 | 6 |
| Oct 26, 2026 | 6 |
| Oct 25, 2026 | 6 |
| Oct 24, 2026 | 6 |
| Oct 23, 2026 | 6 |
| Oct 22, 2026 | 6 |
| Oct 21, 2026 | 6 |
| Oct 20, 2026 | 6 |
| Oct 19, 2026 | 6 |
| Oct 18, 2026 | 6 |
| Oct 17, 2026 | 6 |
| Oct 16, 2026 | 6 |
| Oct 15, 2026 | 6 |
| Oct 14, 2026 | 6 |
| Oct 13, 2026 | 6 |
| Oct 12, 2026 | 6 |
| Oct 11, 2026 | 6 |
| Oct 10, 2026 | 6 |
| Oct 9, 2026 | 6 |
| Oct 8, 2026 | 6 |
| Oct 7, 2026 | 6 |
| Oct 6, 2026 | 6 |
| Oct 5, 2026 | 6 |
| Oct 4, 2026 | 6 |
| Oct 3, 2026 | 6 |
Map
Where GOPAS Solutions'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.
| AMS-IX Amsterdam, Netherlands | 200M | Both IPv6 not in PeeringDBSpeed differs | |
| DE-CIX Frankfurt Frankfurt, Germany | 200M | Both IPv6 not in PeeringDBSpeed differs | |
| DE-CIX Hamburg Hamburg, Germany | 1G | Both IPv6 not in PeeringDB | |
| MegaIX Berlin Berlin, Germany | 200M | Both IPv6 not in PeeringDB | |
| MegaIX Dusseldorf Dusseldorf, Germany | 200M | Both IPv6 not in PeeringDB | |
| MegaIX Hamburg Hamburg, Germany | 200M | Both IPv6 not in PeeringDB |
GOPAS Solutions lists no facilities in PeeringDB.