AwanCerahBGP
Autonomous System

WANSecurity, Inc.

AS1421United StatesARIN · since 2009Peering: Open

WANSEC

A93/100Excellent

BGP report

Ranked 921 of 19,154 networks in United States, 382 of 2,090 ISPs and transit networks. World rank 7,851.

  • RPKI ROA29/30
  • IRR route objects16/20
  • Upstream redundancy15/15
  • Global visibility10/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
29/30

40 of 41 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
16/20

12 prefixes have an exact route object, 28 are covered by a larger one, 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)
Covered by a larger object (28)

Upstream redundancy

Good
15/15

4 upstream, 2 peer, 1 downstream.

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

Upstream (4)

Global visibility

Needs work
10/10

40 of 41 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

Good
10/10

Profile exists, listed at 2 IX.

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

Prefix aggregation

Needs work
3/5

38 IPv4 prefixes could be summarized into 18.

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