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

AS134544 · 

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

Warning: AS134544 (CENBONGT-AS-AP) announces 7 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS134544
HolderCENBONGT-AS-AP - Cenbong Int'l Holdings Limited
AllocationAPNIC, Hong Kong SAR China (HK), allocated 2015-08-25
Prefixes (IPv4 / IPv6)7 / 0
RPKI valid57% (4 / 7)
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

    3 of 7 announced prefixes have no ROA (RPKI not found): 45.126.2.0/24, 45.126.3.0/24, 103.35.254.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 AS134544 and a max length equal to the prefix length:

    45.126.2.0/24 AS134544 max-length /24
45.126.3.0/24 AS134544 max-length /24
103.35.254.0/24 AS134544 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    6 of 7 announced prefixes have no IRR route object: 45.126.3.0/24, 45.126.1.0/24, 45.126.0.0/24, 45.126.2.0/24, 103.35.252.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 AS134544 in your RIR’s IRR database (or RADB).

    route: 45.126.3.0/24
origin: AS134544

route: 45.126.1.0/24
origin: AS134544

route: 45.126.0.0/24
origin: AS134544

    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: AS134544 announces 7 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 3 of 7 announced prefixes have no ROA (RPKI not found): 45.126.2.0/24, 45.126.3.0/24, 103.35.254.0/24.
  • Info: 4 of 7 announced prefixes are RPKI valid.
  • Warning: 6 of 7 announced prefixes have no IRR route object: 45.126.3.0/24, 45.126.1.0/24, 45.126.0.0/24, 45.126.2.0/24, 103.35.252.0/24 (+1).
  • Info: 2 upstreams and peers, 1 downstream networks seen.
HolderCENBONGT-AS-AP - Cenbong Int'l Holdings Limited
IPv4 prefixes7
IPv6 prefixes0
RPKI4 valid · 3 not found
Without IRR route object6
Downstream networks1
Routes to fix
PrefixRPKI
45.126.2.0/24 No ROA
45.126.3.0/24 No ROA
103.35.254.0/24 No ROA

Upstreams and peers seen to the left 2

AS4837 China Unicom AS9381 HKBNES

Announced prefixes 7

45.126.0.0/24 45.126.1.0/24 45.126.2.0/24 45.126.3.0/24 103.35.252.0/24 103.35.253.0/24 103.35.254.0/24

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameCENBONGT-AS-AP
HandleAS134544
RangeAS134544
CountryHK
Statusactive
Registered2015-08-25T02:31:59Z
Last changed2021-01-15T03:20:26Z
Abuse contactIRT@cenbong.com
Allocation
Registry (RIR)APNIC
CountryHong Kong SAR China (HK)
Delegated on2015-08-25
StatusAllocated
Delegated rangeAS134544

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

Contacts
RoleNameEmail
registrant Cenbong Int'l Holdings Limited support@cenbong.com
abuse IRT-CENBONGT-HK IRT@cenbong.com
administrative, technical Cenbong Intl Holdings Limited administrator support@cenbong.com

Source: https://rdap.apnic.net/autnum/134544. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

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