VeriSign Global Registry Services: PeeringDB fix list

AS26415 · peeringdb.com/net/9897

PeeringDB

18 things to fix in VeriSign Global Registry Services's PeeringDB record, from what its exchanges publish: 3 to add, 14 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on VeriSign Global Registry Services'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 (3)

On the exchange's own member list, but not in VeriSign Global Registry Services's PeeringDB record. Add one entry per connection with these values.

  1. United States DE-CIX Richmond Ashland, United States · PeeringDB 1002From its IX-F export and website members list
    IPv4206.53.137.32
    IPv62001:504:44::672f:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  2. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716From 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.

  3. United States STLIX Saint Louis, MO, United States · PeeringDB 2585From its website members list
    IPv4206.83.12.9
    IPv62001:504:98::9
    SpeedNot published
    RS peerNot published

Correct these entries (14)

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. Austria AAIX Klagenfurt, Austria · PeeringDB 377
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 193.37.144.19: set Speed to 10000 (10G) (now 1000).
  2. Djibouti AMS-IX Djibouti Djibouti, Djibouti · PeeringDB 967
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:43f8:9c1:1::2002001:43f8:9c1:1:0:a502:6415:1
    • In the entry with IPv4 196.223.38.200: set IPv6 to 2001:43f8:9c1:1:0:a502:6415:1 (now 2001:43f8:9c1:1::200).

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

  3. Germany BCIX Berlin, Germany · PeeringDB 87
    ProblemPeeringDB hasThe export has
    Port speed differs1G2G
    • In the entry with IPv4 193.178.185.119: set Speed to 2000 (2G) (now 1000).

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

  4. Thailand BKNIX (Thailand) Bangkok, Thailand · PeeringDB 1025
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 203.159.68.9: set Speed to 10000 (10G) (now 1000).

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

  5. Philippines GetaFIX Manila Manila, Philippines · PeeringDB 2345
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 103.104.19.122: set Speed to 10000 (10G) (now 1000).

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

  6. Australia IX Australia Perth (WA-IX) Perth, Australia · PeeringDB 21
    ProblemPeeringDB hasThe export has
    Port speed differs1G100G
    • In the entry with IPv4 27.106.192.3: set Speed to 100000 (100G) (now 1000).

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

  7. United States IX-Denver Denver, United States · PeeringDB 1207
    ProblemPeeringDB hasThe export has
    Port speed differs1G2 × 1G

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

  8. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 196.60.70.93: set Speed to 10000 (10G) (now 1000).

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

  9. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 196.60.8.93: set Speed to 10000 (10G) (now 1000).

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

  10. United States PhillyIX Philadelphia, United States · PeeringDB 2088
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 206.80.234.9: set Speed to 10000 (10G) (now 1000).
  11. Iceland RIX Reykjavik, Iceland · PeeringDB 228
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 195.130.211.17: set Speed to 10000 (10G) (now 1000).

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

  12. United States SFMIX San Francisco, United States · PeeringDB 155
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 206.197.187.27: set Speed to 10000 (10G) (now 1000).
  13. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 103.16.102.112: set Speed to 10000 (10G) (now 1000).
  14. Italy TOP-IX Turin, Italy · PeeringDB 115
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 194.116.96.46: set Speed to 10000 (10G) (now 1000).

    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 (1)

In PeeringDB, but on none of the exchange's own lists. If VeriSign Global Registry Services has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United States TPAIX Tampa, United States · PeeringDB 833Not on its website members list
    IPv4206.108.114.16
    IPv62001:504:3c::16
    Speed1000 Mbps (1G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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