Conversant, Inc.
VALUECLICK
BGP report
Ranked 6,485 of 19,165 networks in United States. World rank 45,663.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Needs work0 of 18 prefixes have a matching ROA (valid). 18 without a ROA.
Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.
- 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.
Prefixes without a ROA (18)
IRR route objects
Good14 prefixes have an exact route object, 4 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 (4)
Upstream redundancy
Good15 upstream, 24 peer, 0 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Global visibility
Good18 of 18 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
Good7 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
GoodProfile exists, listed at 1 IX.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
Prefix aggregation
Good11 IPv4 prefixes could be summarized into 9.
Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.
Put the badge on your website
<a href="https://bgp.awancerah.cloud/en/AS25751/rapor"><img src="https://bgp.awancerah.cloud/en/AS25751/rapor.svg" alt="BGP report AS25751"></a>
[](https://bgp.awancerah.cloud/en/AS25751/rapor)