ixreport

Telstra (International): PeeringDB fix list

AS4637 · peeringdb.com/net/1459

PeeringDB

8 things to fix in Telstra (International)'s PeeringDB record, from what its exchanges publish: 4 to add, 4 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Telstra (International)'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 Telstra (International)'s PeeringDB record. Add one entry per connection with these values.

  1. Australia EdgeIX - Sydney Sydney, Australia · PeeringDB 2761From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. India Extreme IX Delhi Delhi, India · PeeringDB 1323From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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

  3. India Extreme IX Mumbai Mumbai, India · PeeringDB 1627From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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

  4. Japan JPNAP Tokyo Tokyo, Japan · PeeringDB 95From its website members list

    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 (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.

  1. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 100G + 2 × 10G

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

  2. India DE-CIX Chennai Chennai, India · PeeringDB 2588
    ProblemPeeringDB hasThe export has
    Port speed differs10G2 × 10G
  3. ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 45.120.251.53: set Speed to 100000 (100G) (now 10000).

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

  4. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 195.66.236.166: set Speed to 100000 (100G) (now 30000).

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