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

AS11589 · 

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

Warning: AS11589 (STOWE-COMMUNICATIONS) announces 7 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS11589
HolderSTOWE-COMMUNICATIONS - Stowe Communications LLC
AllocationARIN, United States (US), assigned 2011-07-27
Prefixes (IPv4 / IPv6)7 / 0
RPKI valid0% (0 / 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

    7 of 7 announced prefixes have no ROA (RPKI not found): 52.124.4.0/22, 64.94.148.0/24, 160.223.200.0/23, 161.38.22.0/23, 195.85.78.0/23 (+2).

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

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

    52.124.4.0/22 AS11589 max-length /22
64.94.148.0/24 AS11589 max-length /24
160.223.200.0/23 AS11589 max-length /23
161.38.22.0/23 AS11589 max-length /23
195.85.78.0/23 AS11589 max-length /23
198.212.196.0/23 AS11589 max-length /23
199.188.176.0/21 AS11589 max-length /21

    Open in RPKI / ROA validator Guide

  3. 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: AS11589 announces 7 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 7 of 7 announced prefixes have no ROA (RPKI not found): 52.124.4.0/22, 64.94.148.0/24, 160.223.200.0/23, 161.38.22.0/23, 195.85.78.0/23 (+2).
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 2 downstream networks seen.
HolderSTOWE-COMMUNICATIONS - Stowe Communications LLC
IPv4 prefixes7
IPv6 prefixes0
RPKI7 not found
Downstream networks2
Routes to fix
PrefixRPKI
52.124.4.0/22 No ROA
64.94.148.0/24 No ROA
160.223.200.0/23 No ROA
161.38.22.0/23 No ROA
195.85.78.0/23 No ROA
198.212.196.0/23 No ROA
199.188.176.0/21 No ROA

Upstreams and peers seen to the left 2

AS3356 Lumen AS3356 AS12282 GMA

Announced prefixes 7

52.124.4.0/22 64.94.148.0/24 160.223.200.0/23 161.38.22.0/23 195.85.78.0/23 198.212.196.0/23 199.188.176.0/21

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameSTOWE-COMMUNICATIONS
HandleAS11589
RangeAS11589
Statusactive
Registered2011-07-27T14:50:26-04:00
Last changed2020-02-05T16:38:27-05:00
Abuse contactrickr@stowecable.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2011-07-27
StatusAssigned
Delegated rangeAS11589

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

Contacts
RoleNameEmail
registrant Stowe Communications LLC

Source: https://rdap.arin.net/registry/autnum/11589. Registration data from rdap.arin.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