ixreport

Fastly, Inc.: PeeringDB fix list

AS54113 · peeringdb.com/net/5520

PeeringDB

8 things to fix in Fastly, Inc.'s PeeringDB record, from what its exchanges publish: 5 to add, 3 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Fastly, Inc.'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 Fastly, Inc.'s PeeringDB record. Add one entry per connection with these values.

  1. India AMS-IX Mumbai Mumbai, India · PeeringDB 1623From its IX-F export

    2 connections, so 2 entries:

    IPv4223.31.200.108
    IPv62001:e48:44:100b:0:a505:4113:1
    Speed10000 Mbps (10G)
    RS peerNo
    IPv4223.31.200.109
    IPv62001:e48:44:100b:0:a505:4113:2
    Speed10000 Mbps (10G)
    RS peerNo

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

  2. India Extreme IX Pune Pune, India · PeeringDB 4805From 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.

  3. Ghana GIXA Accra, Ghana · PeeringDB 694From 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.

  4. Thailand THAILAND IX (TH-IX) Bangkok, Thailand · PeeringDB 225From 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.

  5. Bulgaria TurkIX Sofia Sofia, Bulgaria · PeeringDB 4186From its IX-F export and website members list
    IPv4194.42.47.10
    IPv62001:7f8:161::10
    Speed100000 Mbps (100G)
    RS peerYes

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

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. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 300G
    • In the entry with IPv4 196.60.8.13: set Speed to 300000 (300G) (now 100000).
    • In the entry with IPv4 196.60.9.103: set Speed to 300000 (300G) (now 100000).

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

  2. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.239.118.116 193.239.118.126 193.239.118.130 193.239.118.162193.239.118.116 193.239.118.126 193.239.118.130 193.239.118.156 193.239.118.159 193.239.118.162
    IPv6 address missing from PeeringDB2001:7f8:13::a505:4113:1 2001:7f8:13::a505:4113:2 2001:7f8:13::a505:4113:3 2001:7f8:13::a505:4113:42001:7f8:13::a505:4113:1 2001:7f8:13::a505:4113:2 2001:7f8:13::a505:4113:3 2001:7f8:13::a505:4113:4 2001:7f8:13::a505:4113:10 2001:7f8:13::a505:4113:11
    • Add an entry: IPv4 193.239.118.156, IPv6 2001:7f8:13::a505:4113:10, RS peer yes.
    • Add an entry: IPv4 193.239.118.159, IPv6 2001:7f8:13::a505:4113:11, 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.

  3. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs200G25G
    • In the entry with IPv4 185.0.20.133: set Speed to 25000 (25G) (now 200000).

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