Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS25490 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS25490"
JSON Docs

Problem: AS25490 (STC-AS PJSC Rostelecom) announces 87 IPv4 and 1 IPv6 prefixes. 1 problem · 3 warnings

AS pageAS25490
HolderSTC-AS PJSC Rostelecom
AllocationRIPE NCC, Russia (RU), allocated 2002-12-09
Prefixes (IPv4 / IPv6)87 / 1
RPKI valid94% (83 / 88)
Upstreams and peers1

What to fix

  1. Problem

    3 of 88 announced prefixes are RPKI invalid: 62.183.38.0/24, 85.174.240.0/22, 85.174.248.0/22.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    2 of 88 announced prefixes have no ROA (RPKI not found): 91.230.54.0/24, 193.33.132.0/23.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS25490 and a max length equal to the prefix length:

    91.230.54.0/24 AS25490 max-length /24
193.33.132.0/23 AS25490 max-length /23

    Open in RPKI / ROA validator Guide

  3. Warning

    7 of 88 announced prefixes have no IRR route object: 85.174.240.0/22, 85.175.2.0/24, 85.174.248.0/22, 85.175.0.0/21, 83.239.207.0/24 (+2).

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS25490 in your RIR’s IRR database (or RADB).

    route: 85.174.240.0/22
origin: AS25490

route: 85.175.2.0/24
origin: AS25490

route: 85.174.248.0/22
origin: AS25490

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 3 of 88 announced prefixes are RPKI invalid: 62.183.38.0/24, 85.174.240.0/22, 85.174.248.0/22.
  • Pass: AS25490 announces 87 IPv4 and 1 IPv6 prefixes.
  • Problem: 3 of 88 announced prefixes are RPKI invalid: 62.183.38.0/24, 85.174.240.0/22, 85.174.248.0/22.
  • Warning: 2 of 88 announced prefixes have no ROA (RPKI not found): 91.230.54.0/24, 193.33.132.0/23.
  • Info: 83 of 88 announced prefixes are RPKI valid.
  • Warning: 7 of 88 announced prefixes have no IRR route object: 85.174.240.0/22, 85.175.2.0/24, 85.174.248.0/22, 85.175.0.0/21, 83.239.207.0/24 (+2).
  • Info: One upstream or peer seen (AS12389): an outage there takes the whole network off the internet.
HolderSTC-AS PJSC Rostelecom
IPv4 prefixes87
IPv6 prefixes1
RPKI83 valid · 3 invalid · 2 not found
Without IRR route object7
Downstream networks1
Routes to fix
PrefixRPKI
62.183.38.0/24 RPKI invalid
85.174.240.0/22 RPKI invalid
85.174.248.0/22 RPKI invalid
91.230.54.0/24 No ROA
193.33.132.0/23 No ROA

Upstreams and peers seen to the left 1

AS12389 Rostelecom

Announced prefixes 88

62.183.0.0/19 62.183.32.0/20 62.183.38.0/24 62.183.48.0/23 62.183.50.0/24 62.183.52.0/22 62.183.56.0/22 62.183.60.0/22 62.183.64.0/21 62.183.64.0/24 62.183.72.0/22 62.183.88.0/22 62.183.92.0/22 62.183.96.0/22 83.239.0.0/18 83.239.0.0/20 83.239.16.0/20 83.239.32.0/19 83.239.32.0/21 83.239.40.0/22 83.239.48.0/20 83.239.64.0/19 83.239.96.0/20 83.239.200.0/21 83.239.207.0/24 83.239.224.0/20 83.239.240.0/22 83.239.244.0/22 85.172.0.0/19 85.172.32.0/19 85.172.64.0/21 85.172.72.0/22 85.172.79.0/24 85.172.82.0/23 85.172.84.0/22 85.172.96.0/21 85.172.104.0/22 85.172.108.0/23 85.172.160.0/21 85.173.144.0/20 85.173.150.0/23 85.173.152.0/22 85.173.156.0/23 85.174.128.0/22 85.174.132.0/23 85.174.134.0/24 85.174.136.0/24 85.174.143.0/24 85.174.190.0/23 85.174.224.0/20 85.174.224.0/24 85.174.227.0/24 85.174.230.0/23 85.174.232.0/21 85.174.240.0/22 85.174.248.0/22 85.174.250.0/23 85.174.252.0/22 85.175.0.0/21 85.175.1.0/24 85.175.2.0/24 85.175.12.0/22 85.175.14.0/23 85.175.32.0/21 85.175.46.0/24 85.175.62.0/23 85.175.65.0/24 85.175.66.0/23 85.175.72.0/22 85.175.72.0/23 85.175.82.0/23 85.175.91.0/24 85.175.96.0/22 85.175.100.0/23 85.175.152.0/23 85.175.170.0/23 85.175.171.0/24 85.175.194.0/23 85.175.194.0/24 85.175.216.0/22 85.175.226.0/23 85.175.236.0/24 91.230.54.0/24 94.233.144.0/21 94.233.160.0/20 109.172.72.0/24 193.33.132.0/23 2a02:8040::/32

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameSTC-AS
HandleAS25490
RangeAS25490
Statusactive
Registered2002-12-09T12:44:11Z
Last changed2024-12-10T09:58:34Z
Abuse contactabuse@rt.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2002-12-09
StatusAllocated
Delegated rangeAS25490

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant PJSC Rostelecom
registrant RIPE-NCC-END-MNT
registrant ROSTELECOM-MNT
abuse PJSC Rostelecom Technical Team abuse@rt.ru

Source: https://rdap.db.ripe.net/autnum/25490. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup