Fortinet
AS40934
Fortinet Inc.
Tools: Where can I peer with Fortinet? · Where should Fortinet peer next? · Compare Fortinet with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
5 things to fix in Fortinet's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct, 1 to check. As of 2026-11-19 12:40 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.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
2 connections, so 2 entries:
IPv4 103.16.102.69 IPv6 2001:de8:12:100::69 Speed 10000 Mbps (10G) RS peer Yes IPv4 103.16.102.209 IPv6 2001:de8:12:100::209 Speed 10000 Mbps (10G) RS peer Yes
Correct these entries (2)
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.
-
Problem PeeringDB has The export has Port speed differs 10G 20G - In the entry with IPv4 185.1.48.65: set Speed to 20000 (20G) (now 10000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2401: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).
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.
-
IPv4 185.1.15.40 IPv6 2001:7f8:7a::4:934:1 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 32 |
| Nov 18, 2026 | 32 |
| Nov 17, 2026 | 32 |
| Nov 16, 2026 | 31 |
| Nov 15, 2026 | 31 |
| Nov 14, 2026 | 31 |
| Nov 13, 2026 | 31 |
| Nov 12, 2026 | 31 |
| Nov 11, 2026 | 31 |
| Nov 10, 2026 | 31 |
| Nov 9, 2026 | 31 |
| Nov 8, 2026 | 32 |
| Nov 7, 2026 | 32 |
| Nov 6, 2026 | 32 |
| Nov 5, 2026 | 32 |
| Nov 4, 2026 | 32 |
| Nov 3, 2026 | 32 |
| Nov 2, 2026 | 32 |
| Nov 1, 2026 | 32 |
| Oct 31, 2026 | 32 |
| Oct 30, 2026 | 32 |
| Oct 29, 2026 | 32 |
| Oct 28, 2026 | 32 |
| Oct 27, 2026 | 32 |
| Oct 26, 2026 | 32 |
| Oct 25, 2026 | 31 |
| Oct 24, 2026 | 31 |
| Oct 23, 2026 | 31 |
| Oct 22, 2026 | 31 |
| Oct 21, 2026 | 32 |
| Oct 20, 2026 | 32 |
| Oct 19, 2026 | 32 |
| Oct 18, 2026 | 32 |
| Oct 17, 2026 | 32 |
| Oct 16, 2026 | 32 |
| Oct 15, 2026 | 32 |
| Oct 14, 2026 | 32 |
| Oct 13, 2026 | 32 |
| Oct 12, 2026 | 32 |
| Oct 11, 2026 | 32 |
| Oct 10, 2026 | 32 |
| Oct 9, 2026 | 32 |
| Oct 8, 2026 | 32 |
| Oct 7, 2026 | 32 |
| Oct 6, 2026 | 32 |
| Oct 5, 2026 | 32 |
| Oct 4, 2026 | 32 |
| Oct 3, 2026 | 32 |
In the last 30 days Fortinet joined 1 exchange and left 1. Growing networks
Joined
- SIX Seattle Seattle Nov 17, 2026
Left
- Equinix San Jose San Jose Nov 9, 2026 PeeringDB only
Map
Where Fortinet's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| DE-CIX Frankfurt Frankfurt, Germany | 10G | Both | |
| DE-CIX Istanbul Istanbul, Türkiye | 10G | Both Speed differs | |
| DE-CIX Madrid Madrid, Spain | 100G | Both | |
| DE-CIX Mumbai Mumbai, India | 2 × 10G | Both IPv6 not in PeeringDB | |
| Equinix Ashburn Ashburn, United States | 2 × 10G | PeeringDB | |
| Equinix Dallas Dallas, United States | 2 × 10G | PeeringDB | |
| Equinix Denver Denver, United States | 10G | PeeringDB | |
| Equinix Frankfurt Frankfurt, Germany | 2 × 10G | PeeringDB | |
| Equinix London London, United Kingdom | 2 × 10G | PeeringDB | |
| Equinix Miami Miami, United States | 2 × 10G | PeeringDB | |
| Equinix Paris Paris, France | 2 × 10G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 2 × 20G | PeeringDB | |
| Equinix Sydney Sydney, Australia | 2 × 10G | PeeringDB | |
| Equinix Tokyo Tokyo, Japan | 2 × 10G | PeeringDB | |
| Extreme IX Chennai Chennai, India | 2 × 10G | PeeringDB | |
| FL-IX Miami, United States | 20G + 10G | Both | |
| France-IX Paris Paris, France | 10G | PeeringDB | |
| HKIX Hong Kong, Hong Kong | 10G | Both | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 2 × 10G | Both | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 10G | PeeringDB only | |
| JPIX TOKYO Tokyo, Japan | Not in PeeringDB | ||
| JPNAP Tokyo Tokyo, Japan | 2 × 10G | PeeringDB | |
| LINX LON1 London, United Kingdom | 2 × 10G | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 10G | Both | |
| SFMIX San Francisco, United States | 10G | Both | |
| SGIX Singapore, Singapore | 2 × 10G | Not in PeeringDB | |
| SH-IX Fujairah, United Arab Emirates | 10G | PeeringDB only | |
| SIX Seattle Seattle, United States | Both | ||
| TorIX Toronto, Canada | 2 × 100G | PeeringDB | |
| TPIX-TW Taipei/Taiwan, Taiwan | 10G | PeeringDB | |
| UAE-IX Dubai, United Arab Emirates | 2 × 10G | Both | |
| VANIX Vancouver, Canada | 10G | Both |
Fortinet lists no facilities in PeeringDB.
Recent changes Search them
- Nov 17, 2026 [PDB] AS40934 Fortinet now in PeeringDB at SIX Seattle
- Nov 17, 2026 [IXF] [WEB] AS40934 Fortinet added to SIX Seattle
- Nov 9, 2026 [PDB] AS40934 Fortinet left Equinix San Jose