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

AS206922 · 

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

Warning: AS206922 (Globex-NL-AMS Globex Telecom Group Limi…) announces 3 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS206922
HolderGlobex-NL-AMS Globex Telecom Group Limited
AllocationRIPE NCC, Hong Kong SAR China (HK), allocated 2016-10-07
Prefixes (IPv4 / IPv6)3 / 0
RPKI valid67% (2 / 3)
Upstreams and peers1

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

    1 of 3 announced prefixes have no ROA (RPKI not found): 185.20.4.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 AS206922 and a max length equal to the prefix length:

    185.20.4.0/24 AS206922 max-length /24

    Open in RPKI / ROA validator Guide

  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

  4. 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 No IPv6 prefixes announced.
  • Pass: AS206922 announces 3 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 1 of 3 announced prefixes have no ROA (RPKI not found): 185.20.4.0/24.
  • Info: 2 of 3 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS41095): an outage there takes the whole network off the internet.
HolderGlobex-NL-AMS Globex Telecom Group Limited
IPv4 prefixes3
IPv6 prefixes0
RPKI2 valid · 1 not found
Downstream networks1
Routes to fix
PrefixRPKI
185.20.4.0/24 No ROA

Upstreams and peers seen to the left 1

AS41095 IPTP Networks

Announced prefixes 3

185.20.4.0/24 185.171.246.0/24 185.171.247.0/24

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.
NameGlobex-NL-AMS
HandleAS206922
RangeAS206922
Statusactive
Registered2016-10-07T12:35:10Z
Last changed2023-12-04T11:23:26Z
Abuse contactabuse.globex@v-tell.com
Allocation
Registry (RIR)RIPE NCC
CountryHong Kong SAR China (HK)
Delegated on2016-10-07
StatusAllocated
Delegated rangeAS206922

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

Contacts
RoleNameEmail
registrant lir-hk-globex-telecom-1-MNT
registrant Globex Telecom Group Limited
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse.globex@v-tell.com

Source: https://rdap.db.ripe.net/autnum/206922. 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: AS206922 is in PeeringDB as Global Telecom AS206922.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkGlobal Telecom AS206922
AS numberAS206922
Type, Not Disclosed
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Ratio requiredNo
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup