AwanCerahBGP
Autonomous System

AOFB Telecom Networks Ltd

AS213990United KingdomRIPE NCC · since 2024Peering: Open

AOFB

C56/100Fair

BGP report

Ranked 1,697 of 2,318 networks in United Kingdom. World rank 59,037.

  • RPKI ROA12/30
  • IRR route objects12/20
  • Upstream redundancy15/15
  • Global visibility6/10
  • IPv60/10
  • PeeringDB6/10
  • Prefix aggregation5/5

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

Score history

RPKI ROA

Problem
12/30

8 of 13 prefixes have a matching ROA (valid). 3 invalid, 2 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 (3)
Prefixes without a ROA (2)

IRR route objects

Needs work
12/20

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

Upstream redundancy

Good
15/15

2 upstream, 0 peer, 0 downstream.

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

Upstream (2)

Global visibility

Needs work
6/10

8 of 13 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 (5)

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

Needs work
6/10

Profile exists. Missing: IRR as-set, IX connections.

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

13 IPv4 prefixes could be summarized into 13.

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

Put the badge on your website

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