Cloudflare: PeeringDB fix list
AS13335 · peeringdb.com/net/4224
27 things to fix in Cloudflare's PeeringDB record, from what its exchanges publish: 5 to add, 12 to correct, 6 to check, 4 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.
Make the changes on Cloudflare'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 (5)
On the exchange's own member list, but not in Cloudflare'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.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 195.69.116.246 IPv6 2001:7f8:d:101::246 Speed Not published RS peer No -
IPv4 95.133.136.30 IPv6 2001:7f8:171::1e Speed 10000 Mbps (10G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
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 (12)
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:504:9a::11 - In the entry with IPv4 206.83.42.11: set IPv6 to 2001:504:9a::11 (now empty).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 196.223.38.207 196.223.38.207 196.223.38.248 IPv6 address missing from PeeringDB 2001:43f8:9c1:1:0:a501:3335:1 2001:43f8:9c1:1:0:a501:3335:1 2001:43f8:9c1:1:0:a501:3335:2 Port speed differs 100G 100G + 60G - Add an entry: IPv4 196.223.38.248, IPv6 2001:43f8:9c1:1:0:a501:3335:2, speed 60000 (60G), RS peer yes.
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 100G 110G - In the entry with IPv4 185.1.30.67: set Speed to 110000 (110G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 77.241.206.33: set Speed to 10000 (10G) (now 100000).
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 20G - In the entry with IPv4 103.129.62.23: set Speed to 20000 (20G) (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 20G - In the entry with IPv4 149.112.27.8: set Speed to 20000 (20G) (now 10000).
-
Problem PeeringDB has The export has IPv6 address differs 2001:504:44::1:3335:1 2001:504:44::3417:0:1 - In the entry with IPv4 206.53.137.36: set IPv6 to 2001:504:44::3417:0:1 (now 2001:504:44::1:3335:1).
-
Problem PeeringDB has The export has Port speed differs 200G 1G - In the entry with IPv4 123.108.9.176: set Speed to 1000 (1G) (now 200000).
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 2 × 100G 200G + 100G - In the entry with IPv4 218.100.78.12: set Speed to 200000 (200G) (now 100000).
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 IPv4 address missing from PeeringDB 206.108.255.45 206.108.255.13 206.108.255.45 IPv6 address missing from PeeringDB 2001:504:27::3417:0:1 2001:504:27::3417:0:1 2001:504:27::3417:0:2 Port speed differs 100G 2 × 100G - Add an entry: IPv4 206.108.255.13, IPv6 2001:504:27::3417:0:2, speed 100000 (100G), RS peer yes.
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 200G 25G - In the entry with IPv4 185.0.20.102: set Speed to 25000 (25G) (now 200000).
-
Problem PeeringDB has The export has Port speed differs 100G 40G - In the entry with IPv4 185.1.88.20: set Speed to 40000 (40G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (6)
In PeeringDB, but on none of the exchange's own lists. If Cloudflare has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 196.223.47.210 IPv6 2001:43f8:b60::210 Speed 30000 Mbps (30G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 196.60.122.40 IPv6 2001:43f8:1720::40 Speed 20000 Mbps (20G) -
IPv4 194.68.128.246 IPv6 2001:7f8:d:fe::246 Speed 200000 Mbps (200G) -
IPv4 194.68.123.246 IPv6 2001:7f8:d:ff::246 Speed 200000 Mbps (200G) -
IPv4 204.138.0.47 IPv6 2620:102:b000::47 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 91.220.194.44 IPv6 2001:7f8:46:0:1:0:1:3335 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges that look shut down (4)
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 101.203.75.12 IPv6 2403:c780:7200:b075:0:1:3335:1 Speed 10000 Mbps (10G) -
Only one outside network
IPv4 101.203.73.12 IPv6 2403:c780:7200:b073:0:1:3335:1 Speed 10000 Mbps (10G) -
Only one outside network
IPv4 101.203.76.12 IPv6 2403:c780:7200:b076:0:1:3335:1 Speed 10000 Mbps (10G) -
Only one outside network
IPv4 202.88.42.209 IPv6 2400:1560:6::a501:3335:1 Speed 30000 Mbps (30G)
From ixreport.com/net/13335/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.