AwanCerahBGP
Home/Russia/AS41682
Autonomous System

JSC "ER-Telecom Holding"

AS41682RussiaRIPE NCC · since 2006

ERTH-TMN-AS

D50/100Poor

BGP report

Ranked 2,615 of 5,051 networks in Russia. World rank 63,612.

  • RPKI ROA3/30
  • IRR route objects19/20
  • Upstream redundancy7/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB0/10
  • Prefix aggregation1/5

Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored

Score history

RPKI ROA

Needs work
3/30

6 of 60 prefixes have a matching ROA (valid). 54 without a ROA.

Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.

How to fix
  1. 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.
  2. 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 (54)

IRR route objects

Good
19/20

53 prefixes have an exact route object, 7 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 (7)

Upstream redundancy

Problem
7/15

1 upstream, 0 peer, 0 downstream.

With a single upstream, any outage there cuts your whole network off the internet.

How to fix
  1. Add a second upstream from a different provider, and join an IXP to peer directly with other networks.
Upstream (1)

Global visibility

Good
10/10

60 of 60 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

Good
10/10

6 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Problem
0/10

No PeeringDB profile.

Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.

How to fix
  1. Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.

Prefix aggregation

Problem
1/5

54 IPv4 prefixes could be summarized into 12.

Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.

How to fix
  1. 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

BGP report AS41682The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS41682/rapor"><img src="https://bgp.awancerah.cloud/en/AS41682/rapor.svg" alt="BGP report AS41682"></a>
Markdown
[![BGP report AS41682](https://bgp.awancerah.cloud/en/AS41682/rapor.svg)](https://bgp.awancerah.cloud/en/AS41682/rapor)