BGP report
Ranked 383 of 1,098 networks in Argentina. World rank 23,989.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Good25 of 25 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
Good0 prefixes have an exact route object, 25 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 (25)
Upstream redundancy
Good2 upstream, 0 peer, 0 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Upstream (2)
Global visibility
Needs work24 of 25 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 (1)
IPv6
Good16 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
ProblemNo PeeringDB profile.
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
Problem9 IPv4 prefixes could be summarized into 2.
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/AS262156/rapor"><img src="https://bgp.awancerah.cloud/en/AS262156/rapor.svg" alt="BGP report AS262156"></a>
[](https://bgp.awancerah.cloud/en/AS262156/rapor)