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

AS203290 · 

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

Warning: AS203290 (asbliss Limited Liability Company "Blis…) announces 6 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS203290
Holderasbliss Limited Liability Company "Bliss-Pro"
AllocationRIPE NCC, Russia (RU), allocated 2016-02-22
Prefixes (IPv4 / IPv6)6 / 0
RPKI valid0% (0 / 6)
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

    6 of 6 announced prefixes have no ROA (RPKI not found): 185.15.84.0/23, 185.15.84.0/24, 185.15.85.0/24, 185.15.86.0/23, 185.15.86.0/24 (+1).

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

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

    185.15.84.0/23 AS203290 max-length /23
185.15.84.0/24 AS203290 max-length /24
185.15.85.0/24 AS203290 max-length /24
185.15.86.0/23 AS203290 max-length /23
185.15.86.0/24 AS203290 max-length /24
185.15.87.0/24 AS203290 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: AS203290 announces 6 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 6 of 6 announced prefixes have no ROA (RPKI not found): 185.15.84.0/23, 185.15.84.0/24, 185.15.85.0/24, 185.15.86.0/23, 185.15.86.0/24 (+1).
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS198297): an outage there takes the whole network off the internet.
Holderasbliss Limited Liability Company "Bliss-Pro"
IPv4 prefixes6
IPv6 prefixes0
RPKI6 not found
Downstream networks0
Routes to fix
PrefixRPKI
185.15.84.0/23 No ROA
185.15.84.0/24 No ROA
185.15.85.0/24 No ROA
185.15.86.0/23 No ROA
185.15.86.0/24 No ROA
185.15.87.0/24 No ROA

Upstreams and peers seen to the left 1

AS198297 Ul-com Media

Announced prefixes 6

185.15.84.0/23 185.15.84.0/24 185.15.85.0/24 185.15.86.0/23 185.15.86.0/24 185.15.87.0/24

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.
Nameasbliss
HandleAS203290
RangeAS203290
Statusactive
Registered2016-02-22T11:54:00Z
Last changed2018-09-04T11:45:14Z
Abuse contacta234@bliss-pro.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2016-02-22
StatusAllocated
Delegated rangeAS203290

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

Contacts
RoleNameEmail
registrant BLISSPRO-MNT
registrant Limited Liability Company "Bliss-Pro"
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role a234@bliss-pro.ru

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