BGP report
Ranked 46 of 261 networks in Latvia. World rank 16,175.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Good52 of 52 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
Good52 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
Problem1 upstream, 0 peer, 0 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
- Add a second upstream from a different provider, and join an IXP to peer directly with other networks.
Upstream (1)
Global visibility
Good52 of 52 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
Good4 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
Needs workProfile exists. Missing: IX connections, prefix counts.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
- Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.
Prefix aggregation
Needs work48 IPv4 prefixes could be summarized into 19.
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.
Put the badge on your website
<a href="https://bgp.awancerah.cloud/en/AS24921/rapor"><img src="https://bgp.awancerah.cloud/en/AS24921/rapor.svg" alt="BGP report AS24921"></a>
[](https://bgp.awancerah.cloud/en/AS24921/rapor)