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

AS200613 ·

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

Warning: AS200613 (Imeretinskay_Riviera Imeretinskay Rivie…) announces 4 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS200613
HolderImeretinskay_Riviera Imeretinskay Riviera LLC
AllocationRIPE NCC, Russia (RU), allocated 2015-05-22
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid0% (0 / 4)
Upstreams and peers2

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

    4 of 4 announced prefixes have no ROA (RPKI not found): 89.185.66.0/24, 89.185.67.0/24, 89.185.70.0/24, 92.51.24.0/24.

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

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

    89.185.66.0/24 AS200613 max-length /24
    89.185.67.0/24 AS200613 max-length /24
    89.185.70.0/24 AS200613 max-length /24
    92.51.24.0/24 AS200613 max-length /24

    Open in RPKI / ROA validator Guide

  3. 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: AS200613 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 89.185.66.0/24, 89.185.67.0/24, 89.185.70.0/24, 92.51.24.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderImeretinskay_Riviera Imeretinskay Riviera LLC
IPv4 prefixes4
IPv6 prefixes0
RPKI4 not found
Downstream networks0
Routes to fix
PrefixRPKI
89.185.66.0/24 No ROA
89.185.67.0/24 No ROA
89.185.70.0/24 No ROA
92.51.24.0/24 No ROA

Upstreams and peers seen to the left 2

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.
NameImeretinskay_Riviera
HandleAS200613
RangeAS200613
Statusactive
Registered2015-05-22T09:40:29Z
Last changed2020-04-20T08:33:45Z
Abuse contactsupport@imeretinka.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2015-05-22
StatusAllocated
Delegated rangeAS200613

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

Contacts
RoleNameEmail
registrant Imeretinskay Riviera LLC
registrant RIPE-NCC-END-MNT
registrant ru-permtelecom-1-mnt
registrant ru-permtelecom-2-mnt
abuse Abuse-C Role support@imeretinka.ru

Source: https://rdap.db.ripe.net/autnum/200613. 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