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

AS50009 ·

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

Warning: AS50009 (QUARTZ-AS) announces 12 IPv4 and 2 IPv6 prefixes. 2 warnings

AS pageAS50009
HolderQUARTZ-AS QUARTZ TELECOM LLC
AllocationRIPE NCC, Russia (RU), allocated 2009-10-26
Prefixes (IPv4 / IPv6)12 / 2
RPKI valid21% (3 / 14)
Upstreams and peers12
Peering policyOpen

What to fix

  1. Warning

    10 of 14 announced prefixes have no ROA (RPKI not found): 109.94.0.0/19, 109.94.0.0/20, 109.94.16.0/20, 176.109.32.0/20, 176.109.32.0/21 (+5).

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

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

    109.94.0.0/19 AS50009 max-length /19
    109.94.0.0/20 AS50009 max-length /20
    109.94.16.0/20 AS50009 max-length /20
    176.109.32.0/20 AS50009 max-length /20
    176.109.32.0/21 AS50009 max-length /21
    176.109.40.0/21 AS50009 max-length /21
    185.80.248.0/22 AS50009 max-length /22
    185.80.248.0/23 AS50009 max-length /23
    185.80.250.0/23 AS50009 max-length /23
    2a05:7e80::/29 AS50009 max-length /29

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 14 announced prefixes have no IRR route object: 2a05:7e83::/32.

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS50009 in your RIR’s IRR database (or RADB).

    route6: 2a05:7e83::/32
    origin: AS50009

    Open in ASN & BGP prefix lookup

Checks

Routing and RPKI 10 of 14 announced prefixes have no ROA (RPKI not found): 109.94.0.0/19, 109.94.0.0/20, 109.94.16.0/20, 176.109.32.0/20, 176.109.32.0/21 (+5).
  • Pass: AS50009 announces 12 IPv4 and 2 IPv6 prefixes.
  • Warning: 10 of 14 announced prefixes have no ROA (RPKI not found): 109.94.0.0/19, 109.94.0.0/20, 109.94.16.0/20, 176.109.32.0/20, 176.109.32.0/21 (+5).
  • Info: 3 of 14 announced prefixes are RPKI valid.
  • Info: The RPKI state of 1 prefixes was not looked up (no ROA of AS50009 covers them; only the first 10 are checked).
  • Warning: 1 of 14 announced prefixes have no IRR route object: 2a05:7e83::/32.
  • Info: 12 upstreams and peers, 1 downstream networks seen.
HolderQUARTZ-AS QUARTZ TELECOM LLC
IPv4 prefixes12
IPv6 prefixes2
RPKI3 valid · 10 not found · 1 not looked up
Without IRR route object1
Downstream networks1
Routes to fix

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.
NameQUARTZ-AS
HandleAS50009
RangeAS50009
Statusactive
Registered2009-10-26T11:43:33Z
Last changed2018-09-04T10:45:35Z
Abuse contactinfo@navigatorlife.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2009-10-26
StatusAllocated
Delegated rangeAS50009

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

Contacts
RoleNameEmail
registrant MNT-QUARTZ
registrant QUARTZ TELECOM LLC
registrant RIPE-NCC-END-MNT
abuse Quartz abuse handling info@navigatorlife.ru

Source: https://rdap.db.ripe.net/autnum/50009. 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 AS50009 is in PeeringDB as QUARTZ TELECOM.
  • Pass: AS50009 is in PeeringDB as QUARTZ TELECOM.
  • Info: Peering policy: Open.
  • Info: Present at 3 internet exchanges with 3 ports (90G in total).
  • Info: The record was last updated 2024-03-28.
NetworkQUARTZ TELECOM (Quartz)
AS numberAS50009
TypeCable/DSL/ISP, Not Disclosed
Websitehttps://quartztelecom.ru
IRR as-setAS-QUARTZ
Prefixes (IPv4 / IPv6)20 / 1
Traffic20-50Gbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2024-03-28
Contacts
Technicalkeeper@podolsknet.ru
NOCtechsupport@podolsknet.ru

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup