AwanCerahBGP
Home/Russia/AS15672
Autonomous System

OOO Telecom TZ

AS15672RussiaRIPE NCC · since 2000NSPPeering: Open

TZTELECOM

tz.ru
OOO Telecom TZ website
C65/100Fair

BGP report

Ranked 2,006 of 5,051 networks in Russia, 472 of 836 ISPs and transit networks. World rank 47,821.

  • RPKI ROA0/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation0/5

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

Score history

RPKI ROA

Problem
0/30

0 of 86 prefixes have a matching ROA (valid). 1 invalid, 85 without a ROA.

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

How to fix
  1. Start with the invalid prefixes: networks running ROV already drop them, so part of the internet cannot reach them.
  2. 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.
  3. 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.
Invalid prefixes (1)
Prefixes without a ROA (85)

IRR route objects

Needs work
20/20

85 prefixes have an exact route object, 0 are covered by a larger one, 1 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 (1)

Upstream redundancy

Good
15/15

13 upstream, 36 peer, 8 downstream.

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

Upstream (13)

Global visibility

Good
10/10

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

1 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 4 IX.

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

Prefix aggregation

Problem
0/5

85 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.

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