DALnet IRC Network
AS31800
Tools: Where can I peer with DALnet IRC Network? · Where should DALnet IRC Network peer next? · Compare DALnet IRC Network with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
7 things to fix in DALnet IRC Network's PeeringDB record, from what its exchanges publish: 1 to add, 6 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on DALnet IRC Network'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 (1)
On the exchange's own member list, but not in DALnet IRC Network's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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:7fa:11:4:0:94d4:0:1 Port speed differs 1G 200G - In the entry with IPv4 218.100.52.34: set IPv6 to 2001:7fa:11:4:0:94d4:0:1 (now empty); set Speed to 200000 (200G) (now 1000).
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:dea:0:40::33 - In the entry with IPv4 43.243.22.51: set IPv6 to 2001:dea:0:40::33 (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:dea:0:20::4d - In the entry with IPv4 103.26.70.77: set IPv6 to 2001:dea:0:20::4d (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:dea:0:30::79 - In the entry with IPv4 103.26.71.121: set IPv6 to 2001:dea:0:30::79 (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:dea:0:50::2a - In the entry with IPv4 202.12.243.42: set IPv6 to 2001:dea:0:50::2a (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:dea:0:10::c8 - In the entry with IPv4 103.26.68.200: set IPv6 to 2001:dea:0:10::c8 (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 | 16 |
| Nov 18, 2026 | 16 |
| Nov 17, 2026 | 16 |
| Nov 16, 2026 | 16 |
| Nov 15, 2026 | 16 |
| Nov 14, 2026 | 16 |
| Nov 13, 2026 | 16 |
| Nov 12, 2026 | 16 |
| Nov 11, 2026 | 16 |
| Nov 10, 2026 | 16 |
| Nov 9, 2026 | 16 |
| Nov 8, 2026 | 16 |
| Nov 7, 2026 | 16 |
| Nov 6, 2026 | 16 |
| Nov 5, 2026 | 16 |
| Nov 4, 2026 | 16 |
| Nov 3, 2026 | 16 |
| Nov 2, 2026 | 16 |
| Nov 1, 2026 | 16 |
| Oct 31, 2026 | 16 |
| Oct 30, 2026 | 16 |
| Oct 29, 2026 | 16 |
| Oct 28, 2026 | 16 |
| Oct 27, 2026 | 16 |
| Oct 26, 2026 | 16 |
| Oct 25, 2026 | 16 |
| Oct 24, 2026 | 16 |
| Oct 23, 2026 | 16 |
| Oct 22, 2026 | 16 |
| Oct 21, 2026 | 16 |
| Oct 20, 2026 | 16 |
| Oct 19, 2026 | 16 |
| Oct 18, 2026 | 16 |
| Oct 17, 2026 | 16 |
| Oct 16, 2026 | 16 |
| Oct 15, 2026 | 16 |
| Oct 14, 2026 | 16 |
| Oct 13, 2026 | 16 |
| Oct 12, 2026 | 16 |
| Oct 11, 2026 | 16 |
| Oct 10, 2026 | 16 |
| Oct 9, 2026 | 16 |
| Oct 8, 2026 | 16 |
| Oct 7, 2026 | 16 |
| Oct 6, 2026 | 16 |
| Oct 5, 2026 | 16 |
| Oct 4, 2026 | 16 |
| Oct 3, 2026 | 16 |
Map
Where DALnet IRC Network'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.
| Digital Realty Atlanta Atlanta, United States | 1G | PeeringDB | |
| EdgeIX - Perth Perth, Australia | 10G | PeeringDB | |
| EdgeIX - Sydney Sydney, Australia | Not in PeeringDB | ||
| Equinix Ashburn Ashburn, United States | 1G | PeeringDB | |
| Equinix Dallas Dallas, United States | 1G | PeeringDB | |
| Equinix San Jose San Jose, United States | 1G | PeeringDB | |
| Equinix Sydney Sydney, Australia | 100M | PeeringDB | |
| FIXO Oslo, Norway | 1G | Both | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 1G | Both IPv6 not in PeeringDBSpeed differs | |
| MegaIX Auckland Auckland, New Zealand | 100M | Both IPv6 not in PeeringDB | |
| MegaIX Brisbane Brisbane, Australia | 100M | Both IPv6 not in PeeringDB | |
| MegaIX Melbourne Melbourne, Australia | 100M | Both IPv6 not in PeeringDB | |
| MegaIX Perth Perth, Australia | 100M | Both IPv6 not in PeeringDB | |
| MegaIX Sydney Sydney, Australia | 100M | Both IPv6 not in PeeringDB | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 1G | Both | |
| SIX Seattle Seattle, United States | 100M | Both |
DALnet IRC Network lists no facilities in PeeringDB.