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

85.174.248.0/22 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=85.174.248.0%2F22"
JSON Docs

Problem: 85.174.248.0/22 is announced by AS25490 (STC-AS PJSC Rostelecom). 1 problem · 2 warnings

Announced as85.174.248.0/22
Origin ASAS25490 STC-AS PJSC Rostelecom
HolderROSTELECOM-MNT
AllocationRIPE NCC, Russia (RU), allocated 2004-12-22
Size1,024 addresses
Abuse contactabuse@rt.ru

What to fix

  1. Problem

    85.174.248.0/22 from AS25490 is RPKI invalid: no ROA authorises this origin.

    ROAs for this space name AS12389, AS25490. Networks that filter will drop the route – the usual cause of an outage after moving to a new provider or adding DDoS protection.

    Fix: Create a ROA for AS25490 (keep the old one until the move is finished), or stop announcing the route from this AS.

    prefix: 85.174.248.0/22
    origin: AS25490
    max-length: 22

    Open in RPKI / ROA validator Guide

  2. Warning

    Seen by only 8% of RIPE RIS peers.

    Partial visibility points to filtering, a missing IRR route object, or an RPKI problem.

    Open in ASN & BGP prefix lookup

  3. Warning

    Reverse DNS is delegated for only 2 of the 4 zones checked.

    Addresses in the zones without a delegation have no PTR records.

    Fix: Create the missing reverse zones at your RIR.

    Open in DNS lookup

Checks

Routing and RPKI 85.174.248.0/22 from AS25490 is RPKI invalid: no ROA authorises this origin.
  • Pass: Announced as 85.174.248.0/22 by AS25490.
  • Problem: 85.174.248.0/22 from AS25490 is RPKI invalid: no ROA authorises this origin.
  • Pass: 85.174.250.0/23 from AS25490 is RPKI valid. 85.174.250.0/23
  • Warning: Seen by only 8% of RIPE RIS peers.
  • Info: The ROA 85.172.0.0/14 AS12389 allows announcements up to /24.
Route85.174.248.0/22
Origin ASAS25490 STC-AS PJSC Rostelecom RPKI invalid
IRR route objectsRIPE
Visibility (RIS peers)27 / 321
First seen2026-02-20
Covering prefixes85.172.0.0/14
More-specific routes 1
More-specific routeOrigin ASRPKI
85.174.250.0/23 AS25490 RPKI valid
ROAs covering this prefix
ROA prefixMax lengthOrigin AS
85.174.240.0/20 /20 AS25490
85.172.0.0/14 /24 AS12389

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is delegated for only 2 of the 4 zones checked.
  • Warning: Reverse DNS is delegated for only 2 of the 4 zones checked.
Reverse zones 4
ZoneNameservers
248.174.85.in-addr.arpa Not delegated
249.174.85.in-addr.arpa adns2.south.rt.ru, ns.kes.ru
250.174.85.in-addr.arpa Not delegated
251.174.85.in-addr.arpa ns.kes.ru, ns.krdn.ru, ns.radnet.ru, ns2.radnet.ru
Open in DNS lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameRADNET
Handle85.174.240.0 - 85.174.255.255
Range85.174.240.0 – 85.174.255.255
CountryRU
Statusactive
Registered2026-03-31T08:06:10Z
Last changed2026-03-31T08:06:10Z
Abuse contactabuse@rt.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2004-12-22
StatusAllocated
Delegated range85.172.0.0/14 (85.172.0.0 – 85.175.255.255)

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

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

Source: https://rdap.db.ripe.net/ip/85.174.248.0/22. 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

About the network that announces this space, so not in the fix list.

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup