Cogent Communications, LLC
COGENT-1239
BGP report
Ranked 7,524 of 19,165 networks in United States, 1,413 of 2,089 ISPs and transit networks. World rank 54,557.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Needs work9 of 44 prefixes have a matching ROA (valid). 35 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 (35)
IRR route objects
Needs work12 prefixes have an exact route object, 6 are covered by a larger one, 20 only have objects with another origin, 6 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 (6)
Route object with another origin (20)
Covered by a larger object (6)
Upstream redundancy
Needs work0 upstream, 22 peer, 4,199 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.
Global visibility
Good44 of 44 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
Good44 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
GoodProfile exists, listed at 3 IX.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
Prefix aggregation
GoodNo IPv4 prefixes.
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/AS1239/rapor"><img src="https://bgp.awancerah.cloud/en/AS1239/rapor.svg" alt="BGP report AS1239"></a>
[](https://bgp.awancerah.cloud/en/AS1239/rapor)