CommunityDNS Ltd
AS42909 · 1628
Tools: Where can I peer with CommunityDNS Ltd? · Where should CommunityDNS Ltd peer next? · Compare CommunityDNS Ltd with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
9 things to fix in CommunityDNS Ltd's PeeringDB record, from what its exchanges publish: 4 to add, 4 to correct, 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on CommunityDNS Ltd'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 (4)
On the exchange's own member list, but not in CommunityDNS Ltd'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.
-
IX.br (PTT.br) Curitiba Curitiba, Brazil · PeeringDB 174From its IX-F export and website members list
The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 196.216.148.29 IPv6 – Speed 1000 Mbps (1G) RS peer Yes -
IPv4 185.1.19.11 IPv6 2001:7f8:7d::a79d:1 Speed Not published RS peer Not published
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 10G 1G - In the entry with IPv4 203.159.68.8: set Speed to 1000 (1G) (now 10000).
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 Port speed differs 10G 1G - In the entry with IPv4 185.79.213.68: set Speed to 1000 (1G) (now 10000).
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 Port speed differs 10G 1G - In the entry with IPv4 188.93.170.77: set Speed to 1000 (1G) (now 10000).
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 Port speed differs 10G 1G - In the entry with IPv4 103.16.102.68: set Speed to 1000 (1G) (now 10000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If CommunityDNS Ltd has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 91.218.7.73 IPv6 2001:7f8:94::cd Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
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 CommunityDNS Ltd'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.
| AKL-IX (Auckland NZ) Auckland, New Zealand | 10G | Both | |
| ArmIX Yerevan, Armenia | 1G | PeeringDB only | |
| BKNIX (Thailand) Bangkok, Thailand | 10G | Both Speed differs | |
| IX Australia Perth (WA-IX) Perth, Australia | 100G | Both | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | Website list only | ||
| IX.br (PTT.br) Curitiba Curitiba, Brazil | Not in PeeringDB | ||
| IXPN Lagos Lagos, Nigeria | 1G | Not in PeeringDB | |
| JINX Johannesburg, South Africa | 10G | Both | |
| KazNIX Semey, Kazakhstan | 10G | Both Speed differs | |
| LU-CIX Luxembourg, Luxembourg | 10G | Both Speed differs | |
| MSK-IX Moscow Moscow, Russia | 1G | Both | |
| MSK-IX Saint-Petersburg St.Petersburg, Russia | 2 × 1G | Both | |
| OpenIXP / NiCE Indonesia, Indonesia | 10G | PeeringDB | |
| SGIX Singapore, Singapore | 10G | Both Speed differs | |
| TREX Tampere Tampere, Finland | 10G | Both | |
| ULN-IX Ulyanovsk, Russia | Not in PeeringDB |
CommunityDNS Ltd lists no facilities in PeeringDB.