TELEMARCH S.R.L
AS272011

BGP report
Ranked 160 of 203 networks in Dominican Republic, 37 of 42 ISPs and transit networks. World rank 58,167.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Problem4 of 20 prefixes have a matching ROA (valid). 14 invalid, 2 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 (14)
Prefixes without a ROA (2)
IRR route objects
Good4 prefixes have an exact route object, 16 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
Good3 upstream, 0 peer, 2 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Global visibility
Problem6 of 20 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 (14)
IPv6
Good15 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
Needs workProfile exists, listed at 2 IX. Missing: IRR as-set.
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
Good5 IPv4 prefixes could be summarized into 4.
Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.
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/AS272011/rapor"><img src="https://bgp.awancerah.cloud/en/AS272011/rapor.svg" alt="BGP report AS272011"></a>
[](https://bgp.awancerah.cloud/en/AS272011/rapor)