BGP report
Ranked 1,008 of 1,597 networks in Ukraine, 257 of 305 ISPs and transit networks. World rank 60,960.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Problem42 of 562 prefixes have a matching ROA (valid). 16 invalid, 504 without a ROA.
Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.
- Start with the invalid prefixes: networks running ROV already drop them, so part of the internet cannot reach them.
- Create a ROA for every prefix in the portal of the RIR or NIR that holds it: MyAPNIC, the IDNIC member portal, the RIPE NCC LIR Portal, ARIN Online, MyAFRINIC or MiLACNIC.
- The ROA origin must be the AS that actually announces the prefix. Set maxLength to the announced length; a loose maxLength leaves room for sub-prefix hijacks.
Invalid prefixes (16)
Prefixes without a ROA (504)
IRR route objects
Good425 prefixes have an exact route object, 137 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 (137)
Upstream redundancy
Good29 upstream, 44 peer, 56 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Upstream (29)
Global visibility
Needs work437 of 562 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.
- 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 (125)
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 5 IX.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
Prefix aggregation
Problem562 IPv4 prefixes could be summarized into 32.
Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.
- 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)
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/AS6849/rapor"><img src="https://bgp.awancerah.cloud/en/AS6849/rapor.svg" alt="BGP report AS6849"></a>
[](https://bgp.awancerah.cloud/en/AS6849/rapor)