ixreport

Fortinet: PeeringDB fix list

AS40934 · peeringdb.com/net/25888

PeeringDB

6 things to fix in Fortinet's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Fortinet'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 (2)

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

  1. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30From 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. Singapore SGIX Singapore, Singapore · PeeringDB 429From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4103.16.102.69
    IPv62001:de8:12:100::69
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4103.16.102.209
    IPv62001:de8:12:100::209
    Speed10000 Mbps (10G)
    RS peerYes

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. Türkiye DE-CIX Istanbul Istanbul, Türkiye · PeeringDB 1150
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 185.1.48.65: set Speed to 20000 (20G) (now 10000).
  2. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:7500:fff6::6 2401:7500:fff6::62
    • In the entry with IPv4 103.27.170.166: set IPv6 to 2401:7500:fff6::62 (now empty).
    • In the entry with IPv4 103.27.170.207: set IPv6 to 2401:7500:fff6::6 (now empty).
  3. United States FL-IX Miami, United States · PeeringDB 954
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.41.108.113206.41.108.113 206.41.108.236
    IPv6 address missing from PeeringDB2001:504:40:108::1:1132001:504:40:108::1:113 2001:504:40:108::1:236
    Port speed differs10G20G + 10G
    • Add an entry: IPv4 206.41.108.236, IPv6 2001:504:40:108::1:236, speed 20000 (20G), RS peer yes.

Check these entries (1)

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

  1. United Arab Emirates SH-IX Fujairah, United Arab Emirates · PeeringDB 866Not on its website members list
    IPv4185.1.15.40
    IPv62001:7f8:7a::4:934:1
    Speed10000 Mbps (10G)

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

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