AwanCerahBGP
Autonomous System

Richesin Engineering, LLC

AS18849United StatesARIN · since 2024Network ServicesPeering: Open

RICHESIN-ENG

B83/100Good

BGP report

Ranked 2,474 of 19,165 networks in United States. World rank 20,840.

  • RPKI ROA20/30
  • IRR route objects13/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation5/5

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

Score history

RPKI ROA

Needs work
20/30

2 of 3 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
13/20

2 prefixes have an exact route object, 0 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)

Upstream redundancy

Good
15/15

6 upstream, 16 peer, 0 downstream.

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

Upstream (6)

Global visibility

Good
10/10

3 of 3 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

Good
10/10

1 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

Good
5/5

2 IPv4 prefixes could be summarized into 2.

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

Put the badge on your website

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