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

AS24783 ·

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

Warning: AS24783 (ASN-MELS-MurmanElectroSviaz PJSC Rostel…) announces 9 IPv4 and 0 IPv6 prefixes. 2 warnings

AS pageAS24783
HolderASN-MELS-MurmanElectroSviaz PJSC Rostelecom
AllocationRIPE NCC, Russia (RU), allocated 2002-03-26
Prefixes (IPv4 / IPv6)9 / 0
RPKI valid100% (9 / 9)
Upstreams and peers1

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS24783 announces 9 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Pass: All 9 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS12389): an outage there takes the whole network off the internet.
HolderASN-MELS-MurmanElectroSviaz PJSC Rostelecom
IPv4 prefixes9
IPv6 prefixes0
RPKI9 valid
Downstream networks0

Upstreams and peers seen to the left 1

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.
NameASN-MELS-MurmanElectroSviaz
HandleAS24783
RangeAS24783
Statusactive
Registered2002-04-17T08:22:50Z
Last changed2024-12-19T07:43:33Z
Abuse contactabuse@rt.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2002-03-26
StatusAllocated
Delegated rangeAS24783

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/24783. 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