AwanCerahBGP
Home/Germany/AS213230
Autonomous System

Hetzner Online GmbH

AS213230GermanyRIPE NCC · since 2020ContentPeering: Open

HETZNER-CLOUD2-AS

B80/100Good

BGP report

Ranked 1,368 of 2,649 networks in Germany. World rank 24,640.

  • RPKI ROA30/30
  • IRR route objects15/20
  • Upstream redundancy15/15
  • Global visibility0/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation0/5

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

Score history

RPKI ROA

Good
30/30

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

Good
15/20

5 prefixes have an exact route object, 387 are covered by a larger one, 0 have none.

Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.

Covered by a larger object (387)
5.161.8.0/215.161.16.0/245.161.17.0/245.161.18.0/245.161.19.0/245.161.20.0/245.161.21.0/245.161.22.0/245.161.23.0/245.161.24.0/245.161.25.0/245.161.26.0/245.161.27.0/245.161.28.0/245.161.29.0/245.161.30.0/245.161.31.0/245.161.32.0/245.161.33.0/245.161.34.0/245.161.35.0/245.161.36.0/245.161.37.0/245.161.38.0/245.161.39.0/245.161.40.0/245.161.41.0/245.161.42.0/245.161.43.0/245.161.44.0/245.161.45.0/245.161.46.0/245.161.47.0/245.161.48.0/245.161.49.0/245.161.50.0/245.161.51.0/245.161.52.0/245.161.53.0/245.161.54.0/245.161.55.0/245.161.56.0/245.161.57.0/245.161.58.0/245.161.59.0/245.161.60.0/245.161.61.0/245.161.62.0/245.161.63.0/245.161.64.0/245.161.65.0/245.161.66.0/245.161.67.0/245.161.68.0/245.161.69.0/245.161.70.0/245.161.71.0/245.161.72.0/245.161.73.0/245.161.74.0/245.161.75.0/245.161.76.0/245.161.77.0/245.161.78.0/245.161.79.0/245.161.80.0/245.161.81.0/245.161.82.0/245.161.83.0/245.161.84.0/245.161.85.0/245.161.86.0/245.161.87.0/245.161.88.0/245.161.89.0/245.161.90.0/245.161.91.0/245.161.92.0/245.161.93.0/245.161.94.0/245.161.95.0/245.161.96.0/245.161.97.0/245.161.98.0/245.161.99.0/245.161.100.0/245.161.101.0/245.161.102.0/245.161.103.0/245.161.104.0/245.161.105.0/245.161.106.0/245.161.107.0/245.161.108.0/245.161.109.0/245.161.110.0/245.161.111.0/245.161.112.0/245.161.113.0/245.161.114.0/245.161.115.0/245.161.116.0/245.161.117.0/245.161.118.0/245.161.119.0/245.161.120.0/245.161.121.0/245.161.122.0/245.161.123.0/245.161.124.0/245.161.125.0/245.161.126.0/245.161.127.0/245.161.128.0/245.161.129.0/245.161.130.0/245.161.131.0/245.161.132.0/245.161.133.0/245.161.134.0/245.161.135.0/245.161.136.0/245.161.137.0/245.161.138.0/245.161.139.0/245.161.140.0/245.161.141.0/245.161.142.0/245.161.143.0/245.161.144.0/245.161.145.0/245.161.146.0/245.161.147.0/245.161.148.0/245.161.149.0/245.161.150.0/245.161.151.0/245.161.152.0/245.161.153.0/245.161.154.0/245.161.155.0/245.161.156.0/245.161.157.0/245.161.158.0/245.161.159.0/245.161.160.0/225.161.164.0/225.161.176.0/245.161.177.0/245.161.178.0/245.161.179.0/245.161.180.0/245.161.181.0/245.161.182.0/245.161.183.0/245.161.184.0/245.161.185.0/245.161.186.0/245.161.187.0/245.161.188.0/245.161.189.0/245.161.190.0/245.161.191.0/245.161.192.0/245.161.193.0/245.161.194.0/245.161.195.0/245.161.196.0/245.161.197.0/245.161.198.0/245.161.199.0/245.161.200.0/245.161.201.0/245.161.202.0/245.161.203.0/245.161.204.0/245.161.205.0/245.161.206.0/245.161.207.0/245.161.208.0/245.161.209.0/245.161.210.0/245.161.211.0/245.161.212.0/245.161.213.0/245.161.214.0/245.161.215.0/245.161.216.0/245.161.217.0/245.161.218.0/245.161.219.0/245.161.220.0/245.161.221.0/245.161.222.0/245.161.223.0/245.161.224.0/245.161.225.0/245.161.226.0/245.161.227.0/245.161.228.0/24

Upstream redundancy

Good
15/15

8 upstream, 0 peer, 0 downstream.

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

Upstream (8)

Global visibility

Problem
0/10

5 of 392 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 (387)
5.161.8.0/2115.8%5.161.16.0/2415.6%5.161.17.0/2415.6%5.161.18.0/2415.6%5.161.19.0/2415.6%5.161.20.0/2415.6%5.161.21.0/2415.6%5.161.22.0/2415.6%5.161.23.0/2415.6%5.161.24.0/2415.6%5.161.25.0/2415.6%5.161.26.0/2415.6%5.161.27.0/2415.6%5.161.28.0/2415.6%5.161.29.0/2415.6%5.161.30.0/2415.6%5.161.31.0/2415.6%5.161.32.0/2415.6%5.161.33.0/2415.6%5.161.34.0/2415.6%5.161.35.0/2415.6%5.161.36.0/2415.6%5.161.37.0/2415.6%5.161.38.0/2415.6%5.161.39.0/2415.6%5.161.40.0/2415.6%5.161.41.0/2415.6%5.161.42.0/2415.6%5.161.43.0/2415.6%5.161.44.0/2415.6%5.161.45.0/2415.6%5.161.46.0/2415.6%5.161.47.0/2415.6%5.161.48.0/2415.6%5.161.49.0/2415.6%5.161.50.0/2415.6%5.161.51.0/2415.6%5.161.52.0/2415.6%5.161.53.0/2415.6%5.161.54.0/2415.6%5.161.55.0/2415.6%5.161.56.0/2415.6%5.161.57.0/2415.6%5.161.58.0/2415.6%5.161.59.0/2415.6%5.161.60.0/2415.6%5.161.61.0/2415.6%5.161.62.0/2415.6%5.161.63.0/2415.6%5.161.64.0/2415.6%5.161.65.0/2415.6%5.161.66.0/2415.6%5.161.67.0/2415.6%5.161.68.0/2415.6%5.161.69.0/2415.6%5.161.70.0/2415.6%5.161.71.0/2415.6%5.161.72.0/2415.6%5.161.73.0/2415.6%5.161.74.0/2415.6%5.161.75.0/2415.6%5.161.76.0/2415.6%5.161.77.0/2415.6%5.161.78.0/2415.6%5.161.79.0/2415.6%5.161.80.0/2415.6%5.161.81.0/2415.6%5.161.82.0/2415.6%5.161.83.0/2415.6%5.161.84.0/2415.6%5.161.85.0/2415.6%5.161.86.0/2415.6%5.161.87.0/2415.6%5.161.88.0/2415.6%5.161.89.0/2415.6%5.161.90.0/2415.6%5.161.91.0/2415.6%5.161.92.0/2415.6%5.161.93.0/2415.6%5.161.94.0/2415.6%5.161.95.0/2415.6%5.161.96.0/2415.6%5.161.97.0/2415.6%5.161.98.0/2415.6%5.161.99.0/2415.6%5.161.100.0/2415.6%5.161.101.0/2415.6%5.161.102.0/2415.6%5.161.103.0/2415.6%5.161.104.0/2415.6%5.161.105.0/2415.6%5.161.106.0/2415.6%5.161.107.0/2415.6%5.161.108.0/2415.6%5.161.109.0/2415.6%5.161.110.0/2415.6%5.161.111.0/2415.6%5.161.112.0/2415.6%5.161.113.0/2415.6%5.161.114.0/2415.6%5.161.115.0/2415.6%5.161.116.0/2415.6%5.161.117.0/2415.6%5.161.118.0/2415.6%5.161.119.0/2415.6%5.161.120.0/2415.6%5.161.121.0/2415.6%5.161.122.0/2415.6%5.161.123.0/2415.6%5.161.124.0/2415.6%5.161.125.0/2415.6%5.161.126.0/2415.6%5.161.127.0/2415.6%5.161.128.0/2415.6%5.161.129.0/2415.6%5.161.130.0/2415.6%5.161.131.0/2415.6%5.161.132.0/2415.6%5.161.133.0/2415.6%5.161.134.0/2415.6%5.161.135.0/2415.6%5.161.136.0/2415.6%5.161.137.0/2415.6%5.161.138.0/2415.6%5.161.139.0/2415.6%5.161.140.0/2415.6%5.161.141.0/2415.6%5.161.142.0/2415.6%5.161.143.0/2415.6%5.161.144.0/2415.6%5.161.145.0/2415.6%5.161.146.0/2415.6%5.161.147.0/2415.6%5.161.148.0/2415.6%5.161.149.0/2415.6%5.161.150.0/2415.6%5.161.151.0/2415.6%5.161.152.0/2415.6%5.161.153.0/2415.6%5.161.154.0/2415.6%5.161.155.0/2415.6%5.161.156.0/2415.6%5.161.157.0/2415.6%5.161.158.0/2415.6%5.161.159.0/2415.6%5.161.160.0/2215.6%5.161.164.0/2215.6%5.161.176.0/2415.6%5.161.177.0/2415.6%5.161.178.0/2415.6%5.161.179.0/2415.6%5.161.180.0/2415.6%5.161.181.0/2415.6%5.161.182.0/2415.6%5.161.183.0/2415.6%5.161.184.0/2415.6%5.161.185.0/2415.6%5.161.186.0/2415.6%5.161.187.0/2415.6%5.161.188.0/2415.6%5.161.189.0/2415.6%5.161.190.0/2415.6%5.161.191.0/2415.6%5.161.192.0/2415.6%5.161.193.0/2415.6%5.161.194.0/2415.6%5.161.195.0/2415.6%5.161.196.0/2415.6%5.161.197.0/2415.6%5.161.198.0/2415.6%5.161.199.0/2415.6%5.161.200.0/2415.6%5.161.201.0/2415.6%5.161.202.0/2415.6%5.161.203.0/2415.6%5.161.204.0/2415.6%5.161.205.0/2415.6%5.161.206.0/2415.6%5.161.207.0/2415.6%5.161.208.0/2415.6%5.161.209.0/2415.6%5.161.210.0/2415.6%5.161.211.0/2415.6%5.161.212.0/2415.6%5.161.213.0/2415.6%5.161.214.0/2415.6%5.161.215.0/2415.6%5.161.216.0/2415.6%5.161.217.0/2415.6%5.161.218.0/2415.6%5.161.219.0/2415.6%5.161.220.0/2415.6%5.161.221.0/2415.6%5.161.222.0/2415.6%5.161.223.0/2415.6%5.161.224.0/2415.6%5.161.225.0/2415.6%5.161.226.0/2415.6%5.161.227.0/2415.6%5.161.228.0/2415.6%

IPv6

Good
10/10

1 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 1 IX.

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

Prefix aggregation

Problem
0/5

391 IPv4 prefixes could be summarized into 4.

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