AwanCerahBGP
Autonomous System

Fortinet Inc.

AS40934United StatesARIN · since 2008EnterprisePeering: Selective

FORTINET

fortinet.com
Fortinet Inc. website
B84/100Good

BGP report

Ranked 2,324 of 19,168 networks in United States, 753 of 2,088 ISPs and transit networks. World rank 19,594.

  • RPKI ROA18/30
  • IRR route objects19/20
  • Upstream redundancy15/15
  • Global visibility9/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation3/5

Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored

Score history

RPKI ROA

Needs work
18/30

227 of 388 prefixes have a matching ROA (valid). 161 without a ROA.

Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.

How to fix
  1. Create a ROA for every prefix in the portal of the RIR or NIR that holds it: MyAPNIC, the IDNIC member portal, the RIPE NCC LIR Portal, ARIN Online, MyAFRINIC or MiLACNIC.
  2. The ROA origin must be the AS that actually announces the prefix. Set maxLength to the announced length; a loose maxLength leaves room for sub-prefix hijacks.
Prefixes without a ROA (161)
12.34.97.0/2423.249.53.0/2423.249.62.0/2423.249.63.0/2438.21.192.0/2438.21.197.0/2438.21.198.0/2438.21.199.0/2438.21.200.0/2438.21.201.0/2438.21.202.0/2438.21.203.0/2438.21.204.0/2438.21.206.0/2438.21.207.0/2438.150.20.0/2466.35.16.0/2466.35.17.0/2466.35.18.0/2466.35.25.0/2466.35.26.0/2469.167.104.0/2169.167.104.0/2469.167.105.0/2469.167.107.0/2469.167.108.0/2469.167.109.0/2469.167.110.0/2469.167.112.0/2469.167.113.0/2469.167.114.0/2469.167.115.0/2469.167.117.0/2469.167.118.0/2469.167.119.0/2472.1.73.0/2472.1.75.0/2472.1.78.0/2472.1.79.0/2496.45.47.0/24104.204.184.0/24141.109.160.0/24141.109.164.0/24141.109.165.0/24141.109.166.0/24141.109.167.0/24141.109.168.0/24141.109.169.0/24141.109.170.0/24141.109.171.0/24141.109.172.0/24141.109.173.0/24141.109.174.0/24141.109.175.0/24149.5.232.0/24149.5.233.0/24149.5.234.0/24154.45.1.0/24154.45.6.0/24154.52.0.0/24154.52.1.0/24154.52.2.0/24154.52.3.0/24154.52.4.0/24154.52.5.0/24154.52.6.0/24154.52.7.0/24154.52.8.0/24154.52.9.0/24154.52.10.0/24154.52.11.0/24154.52.12.0/24154.52.13.0/24154.52.14.0/24154.52.15.0/24154.52.16.0/24154.52.17.0/24154.52.18.0/24154.52.20.0/24154.52.21.0/24154.52.22.0/24154.52.23.0/24154.52.24.0/24154.52.25.0/24154.52.26.0/24154.52.27.0/24154.52.29.0/24154.52.30.0/24154.52.31.0/24159.48.160.0/24159.48.170.0/24159.48.171.0/24160.223.160.0/24160.223.161.0/24160.223.162.0/24160.223.163.0/24160.223.164.0/24160.223.165.0/24160.223.166.0/24160.223.167.0/24160.223.168.0/24160.223.169.0/24160.223.171.0/24160.223.172.0/24160.223.173.0/24173.243.128.0/24173.243.132.0/24173.243.133.0/24173.243.134.0/24173.243.135.0/24173.243.136.0/24173.243.137.0/24173.243.138.0/24173.243.139.0/24173.243.141.0/24173.243.142.0/24173.243.143.0/24176.23.152.0/24189.25.40.0/24189.25.41.0/24189.25.48.0/24189.25.63.0/24189.25.115.0/24189.25.127.0/24189.25.163.0/24193.149.130.0/24193.149.134.0/23193.149.139.0/24194.69.172.0/24194.69.174.0/24208.91.113.0/24208.91.114.0/24208.91.115.0/24208.97.222.0/24209.40.96.0/24209.40.97.0/24209.40.98.0/24209.40.99.0/24209.40.100.0/24209.40.102.0/24209.40.104.0/24209.40.105.0/24209.40.106.0/24209.40.107.0/24209.40.111.0/24209.40.112.0/24209.40.116.0/24209.40.117.0/24209.40.119.0/24209.40.124.0/24209.40.125.0/24209.40.126.0/24209.40.127.0/24210.7.96.0/242602:fc4e:2::/482602:fc4e:43::/482620:101:9000::/482620:101:9004::/482620:101:9005::/482620:101:900c::/482620:101:900d::/48

IPv6

Good
10/10

9 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 30 IX.

Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.

Prefix aggregation

Needs work
3/5

379 IPv4 prefixes could be summarized into 146.

Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.

How to fix
  1. Announce the aggregate when the split is not needed. If it is intended, give every piece its own ROA and route object.

Dropping invalid routes (ROV)

Good

Not seen passing on RPKI-invalid routes of other networks in sampled paths.

Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.

Put the badge on your website

BGP report AS40934The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS40934/rapor"><img src="https://bgp.awancerah.cloud/en/AS40934/rapor.svg" alt="BGP report AS40934"></a>
Markdown
[![BGP report AS40934](https://bgp.awancerah.cloud/en/AS40934/rapor.svg)](https://bgp.awancerah.cloud/en/AS40934/rapor)