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

83.239.0.0/18 ·

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

Problem: 83.239.0.0/18 is announced by AS25490 (STC-AS PJSC Rostelecom). 1 problem

Announced as83.239.0.0/18
Origin ASAS25490 STC-AS PJSC Rostelecom
HolderPJSC Rostelecom
AllocationRIPE NCC, Russia (RU), allocated 2004-02-25
Size16,384 addresses
Abuse contactabuse@rt.ru

What to fix

  1. Problem

    83.239.47.0/24 from AS44467 is RPKI invalid: no ROA authorises this origin. 83.239.47.0/24

    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 AS44467 (keep the old one until the move is finished), or stop announcing the route from this AS.

    prefix: 83.239.47.0/24
    origin: AS44467
    max-length: 24

    Open in RPKI / ROA validator Guide

Checks

Routing and RPKI 83.239.47.0/24 from AS44467 is RPKI invalid: no ROA authorises this origin.
  • Pass: Announced as 83.239.0.0/18 by AS25490.
  • Pass: 83.239.0.0/18 from AS25490 is RPKI valid.
  • Pass: 83.239.32.0/19 from AS25490 is RPKI valid. 83.239.32.0/19
  • Pass: 83.239.0.0/20 from AS25490 is RPKI valid. 83.239.0.0/20
  • Pass: 83.239.16.0/20 from AS25490 is RPKI valid. 83.239.16.0/20
  • Pass: 83.239.48.0/20 from AS25490 is RPKI valid. 83.239.48.0/20
  • Pass: 83.239.32.0/21 from AS25490 is RPKI valid. 83.239.32.0/21
  • Pass: 83.239.40.0/22 from AS25490 is RPKI valid. 83.239.40.0/22
  • Pass: 83.239.44.0/24 from AS44467 is RPKI valid. 83.239.44.0/24
  • Pass: 83.239.45.0/24 from AS44467 is RPKI valid. 83.239.45.0/24
  • Pass: 83.239.46.0/24 from AS44467 is RPKI valid. 83.239.46.0/24
  • Problem: 83.239.47.0/24 from AS44467 is RPKI invalid: no ROA authorises this origin. 83.239.47.0/24
  • Pass: Seen by 100% of RIPE RIS peers.
Route83.239.0.0/18
Origin ASAS25490 STC-AS PJSC Rostelecom RPKI valid
IRR route objectsRIPE
Visibility (RIS peers)321 / 321
First seen2011-03-04
Covering prefixes83.239.0.0/16
More-specific routes 10
More-specific routeOrigin ASRPKI
83.239.32.0/19 AS25490 RPKI valid
83.239.0.0/20 AS25490 RPKI valid
83.239.16.0/20 AS25490 RPKI valid
83.239.48.0/20 AS25490 RPKI valid
83.239.32.0/21 AS25490 RPKI valid
83.239.40.0/22 AS25490 RPKI valid
83.239.44.0/24 AS44467 RPKI valid
83.239.45.0/24 AS44467 RPKI valid
83.239.46.0/24 AS44467 RPKI valid
83.239.47.0/24 AS44467 RPKI invalid
ROAs covering this prefix
ROA prefixMax lengthOrigin AS
83.239.0.0/18 /18 AS25490
83.239.0.0/16 /16 AS12389

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is delegated for all 10 zones checked.
  • Pass: Reverse DNS is delegated for all 10 zones checked.
  • Info: Only the first 10 of 64 reverse zones were checked.
Reverse zones 64
ZoneNameservers
0.239.83.in-addr.arpa ns.krdn.ru, ns.kuban.ru
1.239.83.in-addr.arpa ns.krdn.ru, ns.kuban.ru
2.239.83.in-addr.arpa adns2.south.rt.ru, ns.kuban.ru
3.239.83.in-addr.arpa ns.krdn.ru, ns.kuban.ru
4.239.83.in-addr.arpa ns.krdn.ru, ns.kuban.ru
5.239.83.in-addr.arpa ns.krdn.ru, ns.kuban.ru
6.239.83.in-addr.arpa ns.krdn.ru, ns.kuban.ru
7.239.83.in-addr.arpa ns.krdn.ru, ns.kuban.ru
8.239.83.in-addr.arpa ns.krdn.ru, ns.kuban.ru
9.239.83.in-addr.arpa ns.krdn.ru, ns.kuban.ru
Open in DNS lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameRU-RTK-20040225
Handle83.239.0.0 - 83.239.255.255
Range83.239.0.0 – 83.239.255.255
CountryRU
Statusactive
Registered2004-02-25T10:18:03Z
Last changed2024-06-05T10:29:33Z
Abuse contactabuse@rt.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2004-02-25
StatusAllocated
Delegated range83.239.0.0/16 (83.239.0.0 – 83.239.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 PJSC Rostelecom
registrant RIPE-NCC-HM-MNT
registrant ROSTELECOM-MNT
abuse PJSC Rostelecom Technical Team abuse@rt.ru

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