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

AS18186 ·

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

Warning: AS18186 (NEBULA-GLOBAL) announces 704 IPv4 and 23 IPv6 prefixes. 2 warnings

AS pageAS18186
HolderNEBULA-GLOBAL - Nebula Global LLC
AllocationARIN, United States (US), assigned 2024-09-25
Prefixes (IPv4 / IPv6)704 / 23
RPKI valid4% (29 / 727)
Upstreams and peers35
Peering policyOpen

What to fix

  1. Warning

    10 of 727 announced prefixes have no ROA (RPKI not found): 38.162.120.0/24, 38.162.121.0/24, 38.162.122.0/24, 38.162.123.0/24, 38.162.124.0/24 (+5).

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

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

    38.162.120.0/24 AS18186 max-length /24
    38.162.121.0/24 AS18186 max-length /24
    38.162.122.0/24 AS18186 max-length /24
    38.162.123.0/24 AS18186 max-length /24
    38.162.124.0/24 AS18186 max-length /24
    38.162.125.0/24 AS18186 max-length /24
    38.162.126.0/24 AS18186 max-length /24
    38.162.127.0/24 AS18186 max-length /24
    38.182.128.0/24 AS18186 max-length /24
    38.182.129.0/24 AS18186 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    77 of 727 announced prefixes have no IRR route object: 207.56.248.0/24, 2a10:ce40:231::/48, 149.104.176.0/20, 2602:f7f0:d73::/48, 2602:f7f0:f53::/48 (+72).

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

    route: 207.56.248.0/24
    origin: AS18186
    
    route6: 2a10:ce40:231::/48
    origin: AS18186
    
    route: 149.104.176.0/20
    origin: AS18186

    Open in ASN & BGP prefix lookup

Checks

Routing and RPKI 10 of 727 announced prefixes have no ROA (RPKI not found): 38.162.120.0/24, 38.162.121.0/24, 38.162.122.0/24, 38.162.123.0/24, 38.162.124.0/24 (+5).
  • Pass: AS18186 announces 704 IPv4 and 23 IPv6 prefixes.
  • Warning: 10 of 727 announced prefixes have no ROA (RPKI not found): 38.162.120.0/24, 38.162.121.0/24, 38.162.122.0/24, 38.162.123.0/24, 38.162.124.0/24 (+5).
  • Info: 29 of 727 announced prefixes are RPKI valid.
  • Info: The RPKI state of 688 prefixes was not looked up (no ROA of AS18186 covers them; only the first 10 are checked).
  • Warning: 77 of 727 announced prefixes have no IRR route object: 207.56.248.0/24, 2a10:ce40:231::/48, 149.104.176.0/20, 2602:f7f0:d73::/48, 2602:f7f0:f53::/48 (+72).
  • Info: 35 upstreams and peers, 13 downstream networks seen.
HolderNEBULA-GLOBAL - Nebula Global LLC
IPv4 prefixes704
IPv6 prefixes23
RPKI29 valid · 10 not found · 688 not looked up
Without IRR route object77
Downstream networks13
Routes to fix

Announced prefixes 727

38.162.120.0/24 38.162.121.0/24 38.162.122.0/24 38.162.123.0/24 38.162.124.0/24 38.162.125.0/24 38.162.126.0/24 38.162.127.0/24 38.182.128.0/24 38.182.129.0/24 38.182.130.0/24 38.182.131.0/24 38.182.132.0/24 38.182.133.0/24 38.182.134.0/24 38.182.135.0/24 38.182.136.0/24 38.182.137.0/24 38.182.138.0/23 38.182.138.0/24 38.182.139.0/24 38.182.140.0/23 38.182.140.0/24 38.182.141.0/24 38.182.142.0/24 38.182.143.0/24 38.182.144.0/23 38.182.144.0/24 38.182.145.0/24 38.182.147.0/24 38.182.148.0/22 38.182.148.0/24 38.182.149.0/24 38.182.150.0/24 38.182.151.0/24 38.182.158.0/24 38.182.159.0/24 38.182.160.0/22 38.182.164.0/22 38.182.180.0/22 38.182.192.0/20 38.182.208.0/24 38.182.209.0/24 38.182.212.0/24 38.182.213.0/24 38.182.217.0/24 38.182.218.0/24 38.182.219.0/24 38.182.220.0/24 38.182.221.0/24 38.182.222.0/24 38.182.223.0/24 38.182.224.0/22 38.182.224.0/24 38.182.225.0/24 38.182.226.0/24 38.182.227.0/24 38.182.228.0/24 38.182.229.0/24 38.182.230.0/24 38.182.231.0/24 38.182.232.0/24 38.182.233.0/24 38.182.234.0/24 38.182.235.0/24 38.182.236.0/24 38.182.237.0/24 38.182.238.0/24 38.182.239.0/24 38.182.240.0/20 38.182.246.0/24 39.109.2.0/24 39.109.4.0/24 39.109.8.0/21 39.109.16.0/24 39.109.17.0/24 39.109.18.0/24 39.109.19.0/24 39.109.20.0/24 39.109.21.0/24 39.109.22.0/24 39.109.23.0/24 39.109.24.0/24 39.109.25.0/24 39.109.32.0/24 39.109.33.0/24 39.109.34.0/24 39.109.35.0/24 39.109.36.0/24 39.109.37.0/24 39.109.38.0/24 39.109.39.0/24 39.109.40.0/24 39.109.41.0/24 39.109.42.0/24 39.109.43.0/24 39.109.44.0/24 39.109.53.0/24 39.109.54.0/24 45.196.244.0/24

Showing the first 100.

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.
NameNEBULA-GLOBAL
HandleAS18186
RangeAS18186
Statusactive
Registered2024-09-25T14:28:12-04:00
Last changed2026-06-11T10:10:08-04:00
Abuse contactabuse@nebulaglobal.net
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2024-09-25
StatusAssigned
Delegated rangeAS18186

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

Contacts
RoleNameEmail
registrant Nebula Global LLC

Source: https://rdap.apnic.net/autnum/18186. 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 AS18186 is in PeeringDB as Nebula Global LLC.
  • Pass: AS18186 is in PeeringDB as Nebula Global LLC.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
NetworkNebula Global LLC
AS numberAS18186
TypeNetwork Services, Not Disclosed
Websitehttps://as18186.nebulaglobal.com/
IRR as-setAS-18186
Prefixes (IPv4 / IPv6)2000 / 100
Traffic1-5Tbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-01-21
Contacts
Abuseabuse@nebulaglobal.net
Technicalnoc@nebulaglobal.net
NOCnoc@nebulaglobal.net

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup