AwanCerahBGP
Home/Germany/AS8560
Autonomous System

IONOS SE

AS8560GermanyRIPE NCC · since 1997NSPPeering: Open

IONOS-AS

ionos.com
IONOS SE website
A96/100Excellent

BGP report

Ranked 403 of 2,650 networks in Germany, 134 of 411 ISPs and transit networks. World rank 4,394.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation1/5

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

Score history

RPKI ROA

Good
30/30

548 of 548 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
20/20

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

Global visibility

Needs work
10/10

547 of 548 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

20 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 17 IX.

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

Prefix aggregation

Problem
1/5

528 IPv4 prefixes could be summarized into 165.

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