DE-CIX Monitoring
AS205529
DE-CIX Group AG
Tools: Where can I peer with DE-CIX Monitoring? · Where should DE-CIX Monitoring peer next? · Compare DE-CIX Monitoring with another network
This network elsewhere: its registry history on RIR Tracker
PeeringDB fix list Printable page · CSV
12 things to fix in DE-CIX Monitoring's PeeringDB record, from what its exchanges publish: 4 to correct, 5 to check, 3 at exchanges that look shut down. As of 2026-11-19 12:40 UTC.
Make the changes on DE-CIX Monitoring'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.
-
Problem PeeringDB has The export has Port speed differs 20G 2G - In the entry with IPv4 103.162.82.249: set Speed to 2000 (2G) (now 20000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2607:1780:8000:c64:6:1ca4:c:1 - In the entry with IPv4 216.59.36.249: set IPv6 to 2607:1780:8000:c64:6:1ca4:c:1 (now empty).
-
Problem PeeringDB has The export has Port speed differs 20G 2G - In the entry with IPv4 185.1.172.249: set Speed to 2000 (2G) (now 20000).
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 206.53.202.252 is AS62499 DE-CIX Dallas Route Servers 206.53.202.252 Address belongs to another network in PeeringDB 2001:504:61::f423:fc:1 is AS62499 DE-CIX Dallas Route Servers 2001:504:61::f423:fc:1 Port speed differs 20G 2 × 20G 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.
- Add an entry: IPv4 –, IPv6 –, speed 20000 (20G), RS peer no.
Check these entries (5)
In PeeringDB, but on none of the exchange's own lists. If DE-CIX Monitoring has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 84.252.106.249 IPv6 2a10:1100::3:2a9b:c:1 Speed 20000 Mbps (20G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 49.213.56.249 IPv6 2001:df5:7880::2614:c:1 Speed 20000 Mbps (20G) -
IPv4 45.68.93.249 IPv6 2801:81:c0:2:4:310f:c:1 Speed 20000 Mbps (20G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 45.68.92.249 IPv6 2801:81:c0:1:4:30fa:c:1 Speed 20000 Mbps (20G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
Pakistan Internet Exchange (PIE) Karachi Karachi, Pakistan · PeeringDB 4271Not on its website members list
IPv4 58.181.127.249 IPv6 2001:df2:b940:0:2:2413:c:1 Speed 20000 Mbps (20G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges that look shut down (3)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 195.60.85.249 IPv6 2001:7f8:170:0:3:c85:c:1 Speed 20000 Mbps (20G) -
Only the operator's own networks
IPv4 216.59.37.249 IPv6 2607:1780:8000:c1d:6:1ca5:c:1 Speed 20000 Mbps (20G) -
Only one outside network
IPv4 185.0.8.121 IPv6 2001:7f8:13e:0:3:12c2:c:1 Speed 20000 Mbps (20G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 45 |
| Nov 18, 2026 | 45 |
| Nov 17, 2026 | 45 |
| Nov 16, 2026 | 45 |
| Nov 15, 2026 | 45 |
| Nov 14, 2026 | 45 |
| Nov 13, 2026 | 45 |
| Nov 12, 2026 | 45 |
| Nov 11, 2026 | 45 |
| Nov 10, 2026 | 45 |
| Nov 9, 2026 | 45 |
| Nov 8, 2026 | 45 |
| Nov 7, 2026 | 45 |
| Nov 6, 2026 | 45 |
| Nov 5, 2026 | 45 |
| Nov 4, 2026 | 44 |
| Nov 3, 2026 | 44 |
| Nov 2, 2026 | 44 |
| Nov 1, 2026 | 44 |
| Oct 31, 2026 | 44 |
| Oct 30, 2026 | 44 |
| Oct 29, 2026 | 44 |
| Oct 28, 2026 | 44 |
| Oct 27, 2026 | 44 |
| Oct 26, 2026 | 44 |
| Oct 25, 2026 | 44 |
| Oct 24, 2026 | 44 |
| Oct 23, 2026 | 44 |
| Oct 22, 2026 | 44 |
| Oct 21, 2026 | 44 |
| Oct 20, 2026 | 44 |
| Oct 19, 2026 | 44 |
| Oct 18, 2026 | 44 |
| Oct 17, 2026 | 44 |
| Oct 16, 2026 | 44 |
| Oct 15, 2026 | 44 |
| Oct 14, 2026 | 44 |
| Oct 13, 2026 | 44 |
| Oct 12, 2026 | 44 |
| Oct 11, 2026 | 44 |
| Oct 10, 2026 | 44 |
| Oct 9, 2026 | 44 |
| Oct 8, 2026 | 44 |
| Oct 7, 2026 | 44 |
| Oct 6, 2026 | 44 |
| Oct 5, 2026 | 44 |
| Oct 4, 2026 | 44 |
| Oct 3, 2026 | 44 |
Map
Where DE-CIX Monitoring'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.
| ACIX Kinshasa, DR Congo | 20G | Both | |
| AF-CIX Lagos, Nigeria | 20G | Both | |
| ALPSiXghost Klagenfurt/Villach, Austria | 20G | PeeringDB only | |
| Aqaba IX Aqaba, Jordan | 20G | PeeringDB only | |
| Borneo-IX Bandar Seri Begawan, Brunei | 20G | Both Speed differs | |
| DartPoints Bridge IX Baton Rouge, LAghost Baton Rouge, United States | 20G | PeeringDB only | |
| DartPoints Bridge IX Dublinghost Dublin, United States | 20G | Both IPv6 not in PeeringDB | |
| DE-CIX ASEAN Singapore, Singapore | 20G | Both | |
| DE-CIX Athens Athens, Greece | 20G | Both Speed differs | |
| DE-CIX Barcelona Barcelona, Spain | 20G | Both | |
| DE-CIX Chicago Chicago, United States | 20G | Both | |
| DE-CIX Copenhagen Copenhagen, Denmark | 20G | Both | |
| DE-CIX Dallas Dallas, United States | 20G | Both Address takenSpeed differs | |
| DE-CIX Dusseldorf Düsseldorf, Germany | 20G | Both | |
| DE-CIX Esbjerg Esbjerg, Denmark | 20G | Both | |
| DE-CIX Frankfurt Frankfurt, Germany | 20G | Both | |
| DE-CIX Hamburg Hamburg, Germany | 20G | Both | |
| DE-CIX Helsinki Helsinki, Finland | 20G | Both | |
| DE-CIX Houston Houston, United States | 20G | Both | |
| DE-CIX Istanbul Istanbul, Türkiye | 20G | Both | |
| DE-CIX Jakarta Jakarta, Indonesia | 20G | PeeringDB only | |
| DE-CIX Kristiansand Kristiansand, Norway | 20G | Both | |
| DE-CIX Kuala Lumpur Kuala Lumpur, Malaysia | 20G | Both | |
| DE-CIX Leipzig Leipzig, Germany | 20G | Both | |
| DE-CIX Lisbon Lisbon, Portugal | 20G | Both | |
| DE-CIX Madrid Madrid, Spain | 20G | Both | |
| DE-CIX Malaysia Kuala Lumpur, Cyberjaya, Johor Bahru, Malaysia | 20G | Both | |
| DE-CIX Marseille Marseille, France | 20G | Both | |
| DE-CIX Mexico Mexico City, Mexico | 20G | Both | |
| DE-CIX Munich Munich, Germany | 20G | Both | |
| DE-CIX New York New York, United States | 20G | Both | |
| DE-CIX Oslo Oslo, Norway | 20G | Both | |
| DE-CIX Palermo Palermo, Italy | 20G | Both | |
| DE-CIX Phoenix Phoenix, United States | 20G | Both | |
| DE-CIX Richmond Ashland, United States | 20G | Both | |
| DE-CIX Rio de Janeiro Rio de Janeiro, Brazil | 20G | PeeringDB only | |
| DE-CIX Sao Paulo Sao Paulo, Brazil | 20G | PeeringDB only | |
| DE-CIX Stockholmghost Stockholm, Sweden | 20G | PeeringDB only | |
| Doha IX Doha, Qatar | 20G | Both | |
| IRAQ-IXP Baghdad, Iraq | 20G | PeeringDB | |
| Pakistan Internet Exchange (PIE) Karachi Karachi, Pakistan | 20G | PeeringDB only | |
| Penang IX Penang, Malaysia | 20G | Both | |
| Ruhr-CIX Ruhr Region, Germany | 20G | Both | |
| SwissIX Zurich, Switzerland | 20G | Both | |
| UAE-IX Dubai, United Arab Emirates | 20G | Both |
DE-CIX Monitoring lists no facilities in PeeringDB.
Recent changes Search them
- Nov 5, 2026 [PDB] AS205529 DE-CIX Monitoring added to ALPSiX