AwanCerahBGP
Home/Russia/AS21353
Autonomous System

JSC "ER-Telecom Holding"

AS21353RussiaRIPE NCC · since 2001

ARTCOMS-AS

E38/100Bad

BGP report

Ranked 4,880 of 5,052 networks in Russia. World rank 82,654.

  • RPKI ROA0/30
  • IRR route objects19/20
  • Upstream redundancy7/15
  • Global visibility9/10
  • IPv60/10
  • PeeringDB0/10
  • Prefix aggregation3/5

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

Score history

IRR route objects

Needs work
19/20

53 prefixes have an exact route object, 8 are covered by a larger one, 2 only have objects with another origin, 0 have none.

Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.

How to fix
  1. 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.
  2. Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
Route object with another origin (2)
Covered by a larger object (8)

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

Needs work
9/10

55 of 63 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.

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

IPv6

Problem
0/10

No IPv6 prefix is announced.

Most mobile users and large services already run on IPv6.

How to fix
  1. Request an IPv6 block from your RIR or NIR if you have none, create its ROA and route6 object, then announce it to your upstreams.

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

Needs work
3/5

63 IPv4 prefixes could be summarized into 41.

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 AS21353The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS21353/rapor"><img src="https://bgp.awancerah.cloud/en/AS21353/rapor.svg" alt="BGP report AS21353"></a>
Markdown
[![BGP report AS21353](https://bgp.awancerah.cloud/en/AS21353/rapor.svg)](https://bgp.awancerah.cloud/en/AS21353/rapor)