BGP report
Ranked 1 of 2,649 networks in Germany, 1 of 408 ISPs and transit networks. World rank 20.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Good19 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
Good19 prefixes have an exact route object, 0 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.
Upstream redundancy
Good24 upstream, 166 peer, 32 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Upstream (24)
Global visibility
Good19 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.
IPv6
Good10 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
GoodProfile exists, listed at 11 IX.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
Prefix aggregation
Good9 IPv4 prefixes could be summarized into 9.
Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.
Dropping invalid routes (ROV)
GoodNot 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
<a href="https://bgp.awancerah.cloud/en/AS9136/rapor"><img src="https://bgp.awancerah.cloud/en/AS9136/rapor.svg" alt="BGP report AS9136"></a>
[](https://bgp.awancerah.cloud/en/AS9136/rapor)
