Delion Pty Ltd: PeeringDB fix list
AS55555 · peeringdb.com/net/3934
3 things to fix in Delion Pty Ltd's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Delion Pty Ltd'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 (3)
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 200M - In the entry with IPv4 218.100.76.127: set Speed to 200 (200M) (now 10000).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 200M - In the entry with IPv4 218.100.78.3: set Speed to 200 (200M) (now 10000).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 100M - In the entry with IPv4 27.106.192.15: set Speed to 100 (100M) (now 10000).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
From ixreport.com/net/55555/: 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.