AwanCerahBGP
Autonomous System

Vlan24

AS14821United StatesARIN · since 2015

VLAN24-INC

C55/100Fair

BGP report

Ranked 8,604 of 19,154 networks in United States. World rank 59,741.

  • RPKI ROA1/30
  • IRR route objects18/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB0/10
  • Prefix aggregation1/5

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

Score history

RPKI ROA

Needs work
1/30

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

IRR route objects

Needs work
18/20

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

Upstream redundancy

Good
15/15

7 upstream, 1 peer, 0 downstream.

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

Upstream (7)

Global visibility

Needs work
10/10

34 of 35 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 (1)

IPv6

Good
10/10

3 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

Problem
1/5

32 IPv4 prefixes could be summarized into 6.

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