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

AS200015 ·

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

Warning: AS200015 (Livetex Omnichannel technologies LLC) announces 1 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS200015
HolderLivetex Omnichannel technologies LLC
AllocationRIPE NCC, Russia (RU), allocated 2013-10-31
Prefixes (IPv4 / IPv6)1 / 0
RPKI valid0% (0 / 1)
Upstreams and peers3
Peering policyRestrictive

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

    1 of 1 announced prefixes have no ROA (RPKI not found): 185.39.80.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 AS200015 and a max length equal to the prefix length:

    185.39.80.0/23 AS200015 max-length /23

    Open in RPKI / ROA validator Guide

  3. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  4. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS200015 announces 1 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 1 of 1 announced prefixes have no ROA (RPKI not found): 185.39.80.0/23.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 3 upstreams and peers, 0 downstream networks seen.
HolderLivetex Omnichannel technologies LLC
IPv4 prefixes1
IPv6 prefixes0
RPKI1 not found
Downstream networks0
Routes to fix
PrefixRPKI
185.39.80.0/23 No ROA

Announced prefixes 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.
NameLivetex
HandleAS200015
RangeAS200015
Statusactive
Registered2013-10-31T09:45:19Z
Last changed2023-10-04T16:46:55Z
Abuse contactabuse@livetex.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2013-10-31
StatusAllocated
Delegated rangeAS200015

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

Contacts
RoleNameEmail
registrant lir-ru-omnichannel-1-MNT
registrant Omnichannel technologies LLC
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@livetex.ru

Source: https://rdap.db.ripe.net/autnum/200015. 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 No IRR as-set is listed.
  • Pass: AS200015 is in PeeringDB as Livetex.
  • Info: Peering policy: Restrictive.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkLivetex (LIVETEX)
AS numberAS200015
TypeContent, Regional
Websitehttps://livetex.ru
Prefixes (IPv4 / IPv6)0 / 0
Traffic100-1000Mbps, Mostly Outbound
Peering policyRestrictive
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup