AwanCerahBGP
Autonomous System

The Internet Business Ltd

AS41678United KingdomRIPE NCC · since 2006ContentPeering: Open

TIBUS

B80/100Good

BGP report

Ranked 927 of 2,317 networks in United Kingdom, 282 of 385 ISPs and transit networks. World rank 24,800.

  • RPKI ROA30/30
  • IRR route objects13/20
  • Upstream redundancy15/15
  • Global visibility9/10
  • IPv60/10
  • PeeringDB10/10
  • Prefix aggregation3/5

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

Score history

RPKI ROA

Good
30/30

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

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

IRR route objects

Needs work
13/20

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

Upstream redundancy

Good
15/15

12 upstream, 68 peer, 2 downstream.

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

Upstream (12)

Global visibility

Needs work
9/10

17 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 (2)

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

Good
10/10

Profile exists, listed at 4 IX.

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

Prefix aggregation

Needs work
3/5

19 IPv4 prefixes could be summarized into 12.

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