net services
AS42965
net services GmbH & Co. KG
Tools: Where can I peer with net services? · Where should net services peer next? · Compare net services with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in net services's PeeringDB record, from what its exchanges publish: 7 to add, 1 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on net services'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 (7)
On the exchange's own member list, but not in net services's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.0.4.7 IPv6 2001:7f8:139::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.1.170.165 IPv6 2001:7f8:9e::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.0.17.3 IPv6 2001:7f8:143::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.0.5.9 IPv6 2001:7f8:13a::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
DE-CIX Kristiansand Kristiansand, Norway · PeeringDB 4042From its IX-F export and website members list
IPv4 185.0.6.4 IPv6 2001:7f8:13b::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.1.208.164 IPv6 2001:7f8:44::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.0.7.7 IPv6 2001:7f8:13c::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes
Correct these entries (1)
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 IPv4 address missing from PeeringDB 185.1.210.58 185.1.210.17 185.1.210.58 IPv6 address missing from PeeringDB 2001:7f8:3d::a7d5:0:2 2001:7f8:3d::a7d5:0:1 2001:7f8:3d::a7d5:0:2 Port speed differs 40G 2 × 100G - In the entry with IPv4 185.1.210.58: set Speed to 100000 (100G) (now 40000).
- Add an entry: IPv4 185.1.210.17, IPv6 2001:7f8:3d::a7d5:0:1, speed 100000 (100G), RS peer yes.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 9 |
| Nov 18, 2026 | 9 |
| Nov 17, 2026 | 9 |
| Nov 16, 2026 | 9 |
| Nov 15, 2026 | 9 |
| Nov 14, 2026 | 9 |
| Nov 13, 2026 | 9 |
| Nov 12, 2026 | 9 |
| Nov 11, 2026 | 9 |
| Nov 10, 2026 | 9 |
| Nov 9, 2026 | 9 |
| Nov 8, 2026 | 9 |
| Nov 7, 2026 | 9 |
| Nov 6, 2026 | 9 |
| Nov 5, 2026 | 9 |
| Nov 4, 2026 | 9 |
| Nov 3, 2026 | 9 |
| Nov 2, 2026 | 9 |
| Nov 1, 2026 | 9 |
| Oct 31, 2026 | 9 |
| Oct 30, 2026 | 9 |
| Oct 29, 2026 | 9 |
| Oct 28, 2026 | 9 |
| Oct 27, 2026 | 9 |
| Oct 26, 2026 | 9 |
| Oct 25, 2026 | 9 |
| Oct 24, 2026 | 9 |
| Oct 23, 2026 | 9 |
| Oct 22, 2026 | 9 |
| Oct 21, 2026 | 9 |
| Oct 20, 2026 | 9 |
| Oct 19, 2026 | 9 |
| Oct 18, 2026 | 9 |
| Oct 17, 2026 | 9 |
| Oct 16, 2026 | 9 |
| Oct 15, 2026 | 9 |
| Oct 14, 2026 | 9 |
| Oct 13, 2026 | 9 |
| Oct 12, 2026 | 9 |
| Oct 11, 2026 | 9 |
| Oct 10, 2026 | 9 |
| Oct 9, 2026 | 9 |
| Oct 8, 2026 | 9 |
| Oct 7, 2026 | 9 |
| Oct 6, 2026 | 9 |
| Oct 5, 2026 | 9 |
| Oct 4, 2026 | 9 |
| Oct 3, 2026 | 9 |
Map
Where net services'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.
| DE-CIX Copenhagen Copenhagen, Denmark | 100G | Not in PeeringDB | |
| DE-CIX Dusseldorf Düsseldorf, Germany | 100G | Not in PeeringDB | |
| DE-CIX Esbjerg Esbjerg, Denmark | 100G | Not in PeeringDB | |
| DE-CIX Frankfurt Frankfurt, Germany | 100G | Both | |
| DE-CIX Hamburg Hamburg, Germany | 40G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| DE-CIX Helsinki Helsinki, Finland | 100G | Not in PeeringDB | |
| DE-CIX Kristiansand Kristiansand, Norway | 100G | Not in PeeringDB | |
| DE-CIX Munich Munich, Germany | 100G | Not in PeeringDB | |
| DE-CIX Oslo Oslo, Norway | 100G | Not in PeeringDB |
net services lists no facilities in PeeringDB.