AwanCerahBGP
Home/Netherlands/AS213120
Autonomous System

Akamai International B.V.

AS213120NetherlandsRIPE NCC · since 2020

PROLEXIC-IP-PROTECT

C65/100Fair

BGP report

Ranked 912 of 1,130 networks in Netherlands. World rank 47,928.

  • RPKI ROA30/30
  • IRR route objects5/20
  • Upstream redundancy7/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB0/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

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

Problem
5/20

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

Upstream redundancy

Problem
7/15

1 upstream, 0 peer, 0 downstream.

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

How to fix
  1. Add a second upstream from a different provider, and join an IXP to peer directly with other networks.
Upstream (1)

Global visibility

Good
10/10

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

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

Needs work
3/5

28 IPv4 prefixes could be summarized into 15.

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.

Put the badge on your website

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