AwanCerahBGP
Autonomous System

Jefferies LLC

AS20249United StatesARIN · since 2019

AS20249

B75/100Good

BGP report

Ranked 4,781 of 19,159 networks in United States. World rank 35,151.

  • RPKI ROA29/30
  • IRR route objects18/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv60/10
  • PeeringDB0/10
  • Prefix aggregation3/5

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

RPKI ROA

Needs work
29/30

52 of 53 prefixes have a matching ROA (valid). 1 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 (1)

IRR route objects

Needs work
18/20

40 prefixes have an exact route object, 12 are covered by a larger one, 1 only have objects with another origin, 0 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.
Route object with another origin (1)
Covered by a larger object (12)

Global visibility

Good
10/10

53 of 53 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.

IPv6

Problem
0/10

No IPv6 prefix is announced.

Most mobile users and large services already run on IPv6.

How to fix
  1. Request an IPv6 block from your RIR or NIR if you have none, create its ROA and route6 object, then announce it to your upstreams.

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

53 IPv4 prefixes could be summarized into 24.

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 AS20249The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS20249/rapor"><img src="https://bgp.awancerah.cloud/en/AS20249/rapor.svg" alt="BGP report AS20249"></a>
Markdown
[![BGP report AS20249](https://bgp.awancerah.cloud/en/AS20249/rapor.svg)](https://bgp.awancerah.cloud/en/AS20249/rapor)