AwanCerahBGP
Home/Russia/AS24739
Autonomous System

JSC "Severen-Telecom"

AS24739RussiaRIPE NCC · since 2002NSPPeering: Selective

SEVEREN-TELECOM

severen.ru
JSC "Severen-Telecom" website
B72/100Good

BGP report

Ranked 1,381 of 5,052 networks in Russia, 381 of 835 ISPs and transit networks. World rank 36,917.

  • RPKI ROA11/30
  • IRR route objects19/20
  • Upstream redundancy7/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation5/5

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

Score history

IRR route objects

Needs work
19/20

85 prefixes have an exact route object, 3 are covered by a larger one, 1 only have objects with another origin, 2 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.
No route object (2)
Route object with another origin (1)
Covered by a larger object (3)

Upstream redundancy

Problem
7/15

1 upstream, 0 peer, 11 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
10/10

89 of 91 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 (2)

IPv6

Good
10/10

1 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 2 IX.

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

Prefix aggregation

Good
5/5

90 IPv4 prefixes could be summarized into 86.

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

Dropping invalid routes (ROV)

Good

Not 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

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