AwanCerahBGP
Autonomous System

Reseaux IP Europeens Network Coordination Centre (RIPE NCC)

AS3333NetherlandsRIPE NCC · since 1994Non-ProfitPeering: Selective

RIPE-NCC-AS

A97/100Excellent

BGP report

Ranked 201 of 1,130 networks in Netherlands, 79 of 217 ISPs and transit networks. World rank 3,966.

  • RPKI ROA30/30
  • IRR route objects18/20
  • Upstream redundancy15/15
  • Global visibility9/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

Good
30/30

8 of 8 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
18/20

7 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

13 upstream, 896 peer, 2 downstream.

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

Upstream (13)

Global visibility

Needs work
9/10

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

IPv6

Good
10/10

2 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

6 IPv4 prefixes could be summarized into 5.

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

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