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

AS34757 ·

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

Warning: AS34757 (SIBSET-NSK-AS) announces 11 IPv4 and 1 IPv6 prefixes. 2 warnings

AS pageAS34757
HolderSIBSET-NSK-AS Sibirskie Seti Ltd.
AllocationRIPE NCC, Russia (RU), allocated 2005-03-30
Prefixes (IPv4 / IPv6)11 / 1
RPKI valid42% (5 / 12)
Upstreams and peers14
Peering policyOpen

What to fix

  1. Warning

    7 of 12 announced prefixes have no ROA (RPKI not found): 80.64.168.0/21, 80.89.192.0/20, 85.118.224.0/21, 89.31.112.0/21, 89.189.176.0/20 (+2).

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

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

    80.64.168.0/21 AS34757 max-length /21
    80.89.192.0/20 AS34757 max-length /20
    85.118.224.0/21 AS34757 max-length /21
    89.31.112.0/21 AS34757 max-length /21
    89.189.176.0/20 AS34757 max-length /20
    93.92.216.0/21 AS34757 max-length /21
    2a00:bfc0::/35 AS34757 max-length /35

    Open in RPKI / ROA validator Guide

  2. 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 7 of 12 announced prefixes have no ROA (RPKI not found): 80.64.168.0/21, 80.89.192.0/20, 85.118.224.0/21, 89.31.112.0/21, 89.189.176.0/20 (+2).
  • Pass: AS34757 announces 11 IPv4 and 1 IPv6 prefixes.
  • Warning: 7 of 12 announced prefixes have no ROA (RPKI not found): 80.64.168.0/21, 80.89.192.0/20, 85.118.224.0/21, 89.31.112.0/21, 89.189.176.0/20 (+2).
  • Info: 5 of 12 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 14 upstreams and peers, 7 downstream networks seen.
HolderSIBSET-NSK-AS Sibirskie Seti Ltd.
IPv4 prefixes11
IPv6 prefixes1
RPKI5 valid · 7 not found
Downstream networks7
Routes to fix
PrefixRPKI
80.64.168.0/21 No ROA
80.89.192.0/20 No ROA
85.118.224.0/21 No ROA
89.31.112.0/21 No ROA
89.189.176.0/20 No ROA
93.92.216.0/21 No ROA
2a00:bfc0::/35 No ROA

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.
NameSIBSET-NSK-AS
HandleAS34757
RangeAS34757
Statusactive
Registered2005-03-30T11:11:43Z
Last changed2026-10-14T01:53:41Z
Abuse contactabuse@sibset-team.ru
Allocation
Registry (RIR)RIPE NCC
CountryRussia (RU)
Delegated on2005-03-30
StatusAllocated
Delegated rangeAS34757

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

Contacts
RoleNameEmail
registrant Sibirskie Seti Ltd.
registrant RIPE-NCC-END-MNT
registrant SIBSET-MNT
abuse Siberian Networks Abuse team abuse@sibset-team.ru

Source: https://rdap.db.ripe.net/autnum/34757. 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 public NOC, policy or technical contact.
  • Pass: AS34757 is in PeeringDB as Sibirskie Seti AS34757.
  • Info: Peering policy: Open.
  • Info: Present at 1 internet exchanges with 1 ports (20G in total).
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkSibirskie Seti AS34757
AS numberAS34757
TypeCable/DSL/ISP, Regional
Websitehttp://sibset.ru
IRR as-setAS-SIBSET
Prefixes (IPv4 / IPv6)20 / 0
Traffic50-100Gbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup