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

AS219447 ·

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

Problem: AS219447 (FLASHSPEEDLIMITED) announces 34 IPv4 and 0 IPv6 prefixes. 1 problem · 2 warnings

AS pageAS219447
HolderFLASHSPEEDLIMITED HONG KONG FLASH SPEED LIMITED
AllocationRIPE NCC, Hong Kong SAR China (HK), allocated 2026-06-12
Prefixes (IPv4 / IPv6)34 / 0
RPKI valid76% (26 / 34)
Upstreams and peers1

What to fix

  1. Problem

    8 of 34 announced prefixes are RPKI invalid: 5.199.37.0/24, 79.180.147.0/24, 82.47.191.0/24, 152.234.134.0/24, 178.93.169.0/24 (+3).

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. 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

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 8 of 34 announced prefixes are RPKI invalid: 5.199.37.0/24, 79.180.147.0/24, 82.47.191.0/24, 152.234.134.0/24, 178.93.169.0/24 (+3).
  • Pass: AS219447 announces 34 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Problem: 8 of 34 announced prefixes are RPKI invalid: 5.199.37.0/24, 79.180.147.0/24, 82.47.191.0/24, 152.234.134.0/24, 178.93.169.0/24 (+3).
  • Info: 26 of 34 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS62610): an outage there takes the whole network off the internet.
HolderFLASHSPEEDLIMITED HONG KONG FLASH SPEED LIMITED
IPv4 prefixes34
IPv6 prefixes0
RPKI26 valid · 8 invalid
Downstream networks0
Routes to fix
PrefixRPKI
5.199.37.0/24 RPKI invalid
79.180.147.0/24 RPKI invalid
82.47.191.0/24 RPKI invalid
152.234.134.0/24 RPKI invalid
178.93.169.0/24 RPKI invalid
178.94.68.0/24 RPKI invalid
178.94.116.0/24 RPKI invalid
189.12.130.0/24 RPKI invalid

Upstreams and peers seen to the left 1

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.
NameFLASHSPEEDLIMITED
HandleAS219447
RangeAS219447
Statusactive
Registered2026-06-12T10:18:53Z
Last changed2026-11-03T17:59:34Z
Abuse contacthaowang@hkflashspeed.com
Allocation
Registry (RIR)RIPE NCC
CountryHong Kong SAR China (HK)
Delegated on2026-06-12
StatusAllocated
Delegated rangeAS219447

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

Contacts
RoleNameEmail
registrant A2-MNT
registrant NOVA-TOP-MNT
registrant HONG KONG FLASH SPEED LIMITED
registrant RIPE-NCC-END-MNT
abuse Abuse contact role object haowang@hkflashspeed.com

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