AwanCerahBGP
Home/AS65521
Autonomous System

AS65521

AS65521
E38/100Bad

BGP report

World rank 82,636.

  • RPKI ROA0/30
  • IRR route objects0/20
  • Upstream redundancy15/15
  • Global visibility8/10
  • IPv610/10
  • PeeringDB0/10
  • Prefix aggregation5/5

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

RPKI ROA

Problem
0/30

0 of 19 prefixes have a matching ROA (valid). 19 invalid, 0 without a ROA.

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

How to fix
  1. Start with the invalid prefixes: networks running ROV already drop them, so part of the internet cannot reach them.
  2. 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.
  3. 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.
Invalid prefixes (19)

IRR route objects

Problem
0/20

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

Upstream redundancy

Good
15/15

4 upstream, 2 peer, 4 downstream.

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

Upstream (4)

Global visibility

Needs work
8/10

15 of 19 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 (4)

IPv6

Good
10/10

2 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

Good
5/5

17 IPv4 prefixes could be summarized into 14.

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

Dropping invalid routes (ROV)

Note

Seen passing on 47 RPKI-invalid routes of other networks in sampled paths. This suggests the AS does not drop all invalid routes, for example those from its customers.

Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.

How to fix
  1. Run an RPKI validator (for example Routinator or rpki-client) and reject invalid routes on your BGP sessions. MikroTik RouterOS 7 supports this through /routing rpki and the rpki-verify filter.
Example invalid routes (4)

Put the badge on your website

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