Servcorp Australian Holdings Pty Ltd: PeeringDB fix list

AS17978 · peeringdb.com/net/7322

PeeringDB

3 things to fix in Servcorp Australian Holdings Pty Ltd's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 21:35 UTC.

Make the changes on Servcorp Australian Holdings 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.

  1. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:4:0:463a:0:1
    • In the entry with IPv4 218.100.52.86: set IPv6 to 2001:7fa:11:4:0:463a:0:1 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::463a:1
    Port speed differs10G4G
    • In the entry with IPv4 195.66.227.198: set IPv6 to 2001:7f8:4::463a:1 (now empty); set Speed to 4000 (4G) (now 10000).
  3. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:73::463a:0:1
    • In the entry with IPv4 185.1.8.77: set IPv6 to 2001:7f8:73::463a:0:1 (now empty).

From ixreport.com/net/17978/: 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.