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

AS51089 · 

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

Warning: AS51089 (SNAPSTACK-AS) announces 5 IPv4 and 4 IPv6 prefixes. 3 warnings

AS pageAS51089
HolderSNAPSTACK-AS SnapStack Limited
AllocationRIPE NCC, Hong Kong SAR China (HK), allocated 2020-04-30
Prefixes (IPv4 / IPv6)5 / 4
RPKI valid89% (8 / 9)
Upstreams and peers2
Peering policyNo

What to fix

  1. Warning

    1 of 9 announced prefixes have no ROA (RPKI not found): 44.32.68.0/24.

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

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

    44.32.68.0/24 AS51089 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    3 of 9 announced prefixes have no IRR route object: 2a06:9f81:5702::/48, 2a06:9f81:5703::/48, 2a06:9f81:5704::/48.

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

    route6: 2a06:9f81:5702::/48
origin: AS51089

route6: 2a06:9f81:5703::/48
origin: AS51089

route6: 2a06:9f81:5704::/48
origin: AS51089

    Open in ASN & BGP prefix lookup

  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

Checks

Routing and RPKI 1 of 9 announced prefixes have no ROA (RPKI not found): 44.32.68.0/24.
  • Pass: AS51089 announces 5 IPv4 and 4 IPv6 prefixes.
  • Warning: 1 of 9 announced prefixes have no ROA (RPKI not found): 44.32.68.0/24.
  • Info: 8 of 9 announced prefixes are RPKI valid.
  • Warning: 3 of 9 announced prefixes have no IRR route object: 2a06:9f81:5702::/48, 2a06:9f81:5703::/48, 2a06:9f81:5704::/48.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderSNAPSTACK-AS SnapStack Limited
IPv4 prefixes5
IPv6 prefixes4
RPKI8 valid · 1 not found
Without IRR route object3
Downstream networks0
Routes to fix
PrefixRPKI
44.32.68.0/24 No ROA

Upstreams and peers seen to the left 2

AS41378 Kirino AS137409 Global Secure Layer

Announced prefixes 9

44.32.68.0/24 65.75.197.0/24 185.218.6.0/23 185.218.6.0/24 185.218.7.0/24 2a06:9f81:5700::/40 2a06:9f81:5702::/48 2a06:9f81:5703::/48 2a06:9f81:5704::/48

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.
NameSNAPSTACK-AS
HandleAS51089
RangeAS51089
Statusactive
Registered2020-04-30T19:11:25Z
Last changed2026-10-15T09:00:25Z
Abuse contactabuse@snapstack.hk
Allocation
Registry (RIR)RIPE NCC
CountryHong Kong SAR China (HK)
Delegated on2020-04-30
StatusAllocated
Delegated rangeAS51089

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

Contacts
RoleNameEmail
registrant MNT-SALTYFISH
registrant SnapStack Limited
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@snapstack.hk

Source: https://rdap.db.ripe.net/autnum/51089. 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: AS51089 is in PeeringDB as SnapStack-HK.
  • Info: Peering policy: No.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Info: The record was last updated 2023-12-22.
NetworkSnapStack-HK
AS numberAS51089
TypeNSP, Global
Websitehttps://snapstack.hk/
Prefixes (IPv4 / IPv6)5 / 20
Traffic10-20Gbps, Balanced
Peering policyNo
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2023-12-22
Contacts
Abuseabuse@snapstack.hk
NOCnoc@snapstack.hk
Salessales@snapstack.hk

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup