AwanCerahBGP
Home/Russia/AS25513
Autonomous System

PJSC Moscow city telephone network

AS25513RussiaRIPE NCC · since 2002Peering: Open

ASN-MGTS-USPD

C63/100Fair

BGP report

Ranked 2,083 of 5,052 networks in Russia, 493 of 836 ISPs and transit networks. World rank 49,115.

  • RPKI ROA1/30
  • IRR route objects17/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB5/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
17/20

42 prefixes have an exact route object, 7 are covered by a larger one, 8 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 (8)
Covered by a larger object (7)

Upstream redundancy

Good
15/15

2 upstream, 0 peer, 20 downstream.

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

Upstream (2)

Global visibility

Good
10/10

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

4 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
5/10

Profile exists. Missing: IRR as-set, IX connections, prefix counts.

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

Good
5/5

53 IPv4 prefixes could be summarized into 39.

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