BGP report
Ranked 1,122 of 5,050 networks in Russia, 331 of 841 ISPs and transit networks. World rank 31,039.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Problem231 of 535 prefixes have a matching ROA (valid). 9 invalid, 295 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 (9)
Prefixes without a ROA (295)
IRR route objects
Needs work441 prefixes have an exact route object, 88 are covered by a larger one, 3 only have objects with another origin, 3 have none.
Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.
- 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.
- Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
No route object (3)
Route object with another origin (3)
Covered by a larger object (88)
Upstream redundancy
Good36 upstream, 139 peer, 800 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Upstream (36)
Global visibility
Needs work488 of 535 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 (47)
IPv6
Good72 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
GoodProfile exists, listed at 15 IX.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
Prefix aggregation
Needs work463 IPv4 prefixes could be summarized into 171.
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)
NoteSeen passing on 143 RPKI-invalid routes of other networks in sampled paths. This suggests the AS does not drop all invalid routes, for example those from its customers.
Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.
- Run an RPKI validator (for example Routinator or rpki-client) and reject invalid routes on your BGP sessions. MikroTik RouterOS 7 supports this through /routing rpki and the rpki-verify filter.
Example invalid routes (4)
Put the badge on your website
<a href="https://bgp.awancerah.cloud/en/AS8359/rapor"><img src="https://bgp.awancerah.cloud/en/AS8359/rapor.svg" alt="BGP report AS8359"></a>
[](https://bgp.awancerah.cloud/en/AS8359/rapor)