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

AS24744 ·

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

Warning: AS24744 (SiNET-SK-AS SiNET Telecom s.r.o.) announces 6 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS24744
HolderSiNET-SK-AS SiNET Telecom s.r.o.
AllocationRIPE NCC, Slovakia (SK), allocated 2002-03-11
Prefixes (IPv4 / IPv6)6 / 0
RPKI valid0% (0 / 6)
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

    6 of 6 announced prefixes have no ROA (RPKI not found): 62.169.160.0/23, 62.169.162.0/23, 62.169.164.0/22, 62.169.168.0/21, 62.169.182.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 AS24744 and a max length equal to the prefix length:

    62.169.160.0/23 AS24744 max-length /23
    62.169.162.0/23 AS24744 max-length /23
    62.169.164.0/22 AS24744 max-length /22
    62.169.168.0/21 AS24744 max-length /21
    62.169.182.0/24 AS24744 max-length /24
    62.169.183.0/24 AS24744 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    6 of 6 announced prefixes have no IRR route object: 62.169.168.0/21, 62.169.183.0/24, 62.169.164.0/22, 62.169.160.0/23, 62.169.182.0/24 (+1).

    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 AS24744 in your RIR’s IRR database (or RADB).

    route: 62.169.168.0/21
    origin: AS24744
    
    route: 62.169.183.0/24
    origin: AS24744
    
    route: 62.169.164.0/22
    origin: AS24744

    Open in ASN & BGP prefix lookup

  4. 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: AS24744 announces 6 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 6 of 6 announced prefixes have no ROA (RPKI not found): 62.169.160.0/23, 62.169.162.0/23, 62.169.164.0/22, 62.169.168.0/21, 62.169.182.0/24 (+1).
  • Warning: 6 of 6 announced prefixes have no IRR route object: 62.169.168.0/21, 62.169.183.0/24, 62.169.164.0/22, 62.169.160.0/23, 62.169.182.0/24 (+1).
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderSiNET-SK-AS SiNET Telecom s.r.o.
IPv4 prefixes6
IPv6 prefixes0
RPKI6 not found
Without IRR route object6
Downstream networks0
Routes to fix
PrefixRPKI
62.169.160.0/23 No ROA
62.169.162.0/23 No ROA
62.169.164.0/22 No ROA
62.169.168.0/21 No ROA
62.169.182.0/24 No ROA
62.169.183.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.
NameSiNET-SK-AS
HandleAS24744
RangeAS24744
Statusactive
Registered2002-03-11T16:52:41Z
Last changed2017-11-15T09:19:15Z
Abuse contactsinet@sinet.sk
Allocation
Registry (RIR)RIPE NCC
CountrySlovakia (SK)
Delegated on2002-03-11
StatusAllocated
Delegated rangeAS24744

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

Contacts
RoleNameEmail
registrant SiNET Telecom s.r.o.
registrant RIPE-NCC-END-MNT
registrant SiNET-SK-MNT
abuse Abuse Contact sinet@sinet.sk

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