AwanCerahBGP
Autonomous System

Amazon Technologies Inc.

AS801United StatesARIN · since 2021

AMAZON-LEO

B72/100Good

BGP report

Ranked 5,167 of 19,168 networks in United States. World rank 37,051.

  • RPKI ROA30/30
  • IRR route objects4/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB0/10
  • Prefix aggregation3/5

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

Score history

RPKI ROA

Good
30/30

252 of 252 prefixes have a matching ROA (valid). 0 without a ROA.

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

IRR route objects

Needs work
4/20

25 prefixes have an exact route object, 42 are covered by a larger one, 18 only have objects with another origin, 167 have none.

Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.

How to fix
  1. Create route (IPv4) and route6 (IPv6) objects with your AS as origin in your RIR's IRR (for example APNIC via MyAPNIC, or IDNIC), or in RADB.
  2. Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
No route object (167)
35.100.0.0/2035.100.16.0/2035.100.32.0/2235.100.36.0/2235.100.40.0/2435.100.41.0/2435.101.0.0/2035.101.16.0/2035.101.32.0/2135.101.40.0/2135.101.48.0/2235.101.52.0/2235.101.56.0/2335.101.58.0/2335.101.60.0/2435.101.61.0/2435.102.0.0/2035.102.16.0/2035.102.32.0/2135.102.40.0/2135.102.48.0/2335.102.50.0/2335.102.52.0/2435.108.0.0/2035.108.16.0/2035.108.32.0/2335.108.34.0/2335.108.36.0/2335.108.38.0/2335.108.40.0/2335.108.42.0/2335.108.44.0/2335.108.46.0/2335.108.48.0/2335.108.50.0/2335.109.0.0/2435.109.1.0/2435.109.2.0/2435.109.3.0/2435.109.4.0/2335.109.64.0/2335.109.66.0/2335.109.96.0/2435.109.97.0/2435.109.98.0/2435.109.99.0/2435.109.100.0/2435.109.128.0/2435.109.129.0/2435.109.130.0/2435.109.144.0/2135.109.152.0/2135.109.160.0/2135.109.168.0/2135.109.176.0/2135.109.184.0/2135.110.0.0/2235.110.4.0/2235.110.128.0/2335.110.130.0/2335.111.0.0/2335.111.2.0/2335.111.64.0/2335.111.66.0/2335.111.68.0/2335.111.70.0/232631:0:1::/482631:0:2::/482631:0:3::/482631:0:4::/482631:0:200::/402631:0:300::/402631:0:400::/402631:0:500::/402631:0:600::/402631:0:700::/402631:0:800::/402631:0:900::/402631:0:a00::/402631:0:b00::/402631:0:e00::/402631:0:f00::/402631:0:1000::/402631:0:1100::/402631:0:1200::/402631:0:1300::/402631:0:1400::/402631:0:1500::/402631:0:1800::/482631:0:2000::/402631:0:2100::/402631:0:2200::/402631:0:2300::/402631:0:2400::/402631:0:2500::/402631:0:2600::/402631:0:2700::/402631:0:2800::/402631:0:2900::/402631:0:2a00::/402631:0:2b00::/402631:0:3000::/402631:0:3100::/402631:0:3200::/402631:0:3300::/402631:0:3400::/402631:0:3500::/402631:0:3600::/402631:0:3700::/402631:0:3800::/402631:0:3900::/402631:0:3e00::/402631:0:3f00::/402631:0:4000::/402631:0:4100::/402631:0:4200::/402631:0:4300::/402631:0:4600::/402631:0:4700::/402631:0:4800::/402631:0:4900::/402631:0:4a00::/402631:0:4b00::/402631:0:4c00::/402631:0:4d00::/402631:80::/452631:80:8::/452631:80:10::/482631:80:11::/482631:80:200::/452631:80:208::/452631:80:210::/462631:80:214::/462631:80:218::/482631:80:400::/442631:80:400::/452631:80:408::/452631:80:410::/442631:80:410::/472631:80:412::/472631:80:414::/482631:80:420::/472631:80:422::/472631:80:424::/482631:80:425::/482631:80:426::/482631:80:600::/482631:80:601::/482631:80:800::/482631:80:a00::/482631:80:a01::/482631:80:a02::/482631:80:a03::/482631:80:a04::/482631:80:a05::/482631:80:a06::/482631:80:c00::/482631:80:e00::/482631:80:e01::/482631:80:1000::/472631:80:1200::/482631:80:1400::/482631:80:1401::/482631:80:1600::/482631:80:1800::/482631:80:1a00::/482631:80:1c00::/48
Route object with another origin (18)
Covered by a larger object (42)

Upstream redundancy

Good
15/15

2 upstream, 0 peer, 0 downstream.

With a single upstream, any outage there cuts your whole network off the internet.

Upstream (2)

Global visibility

Needs work
10/10

247 of 252 prefixes are seen by at least half of the full-table feeds worldwide.

Prefixes seen only partly are usually caught by filters (no ROA or route object), too specific, or announced to domestic IXPs only.

How to fix
  1. Check the ROA and route object of those prefixes, and keep them no longer than /24 for IPv4 or /48 for IPv6.
Prefixes with low visibility (5)

IPv6

Good
10/10

102 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Problem
0/10

No PeeringDB profile.

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

How to fix
  1. Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.

Prefix aggregation

Needs work
3/5

150 IPv4 prefixes could be summarized into 59.

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.

Put the badge on your website

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