BGP report
Ranked 153 of 1,596 networks in Ukraine, 106 of 305 ISPs and transit networks. World rank 10,369.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Good2 of 2 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
Good2 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
Good4 upstream, 6 peer, 1 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Global visibility
Good2 of 2 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
ProblemNo IPv6 prefix is announced.
Most mobile users and large services already run on IPv6.
- Request an IPv6 block from your RIR or NIR if you have none, create its ROA and route6 object, then announce it to your upstreams.
PeeringDB
GoodProfile exists, listed at 2 IX.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
Prefix aggregation
Good2 IPv4 prefixes could be summarized into 2.
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/AS213996/rapor"><img src="https://bgp.awancerah.cloud/en/AS213996/rapor.svg" alt="BGP report AS213996"></a>
[](https://bgp.awancerah.cloud/en/AS213996/rapor)