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

AS32889 · 

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

Warning: AS32889 (SOUTHWESTERN-WIRELESS) announces 2 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS32889
HolderSOUTHWESTERN-WIRELESS - Southwestern Wireless, Inc.
AllocationARIN, United States (US), assigned 2012-05-04
Prefixes (IPv4 / IPv6)2 / 0
RPKI valid0% (0 / 2)
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

    2 of 2 announced prefixes have no ROA (RPKI not found): 192.243.31.0/24, 199.195.170.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 AS32889 and a max length equal to the prefix length:

    192.243.31.0/24 AS32889 max-length /24
199.195.170.0/24 AS32889 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    1 of 2 announced prefixes have no IRR route object: 192.243.31.0/24.

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

    route: 192.243.31.0/24
origin: AS32889

    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: AS32889 announces 2 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 2 of 2 announced prefixes have no ROA (RPKI not found): 192.243.31.0/24, 199.195.170.0/24.
  • Warning: 1 of 2 announced prefixes have no IRR route object: 192.243.31.0/24.
  • Info: One upstream or peer seen (AS32505): an outage there takes the whole network off the internet.
HolderSOUTHWESTERN-WIRELESS - Southwestern Wireless, Inc.
IPv4 prefixes2
IPv6 prefixes0
RPKI2 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
192.243.31.0/24 No ROA
199.195.170.0/24 No ROA

Upstreams and peers seen to the left 1

AS32505 Conterra

Announced prefixes 2

192.243.31.0/24 199.195.170.0/24

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.
NameSOUTHWESTERN-WIRELESS
HandleAS32889
RangeAS32889
Statusactive
Registered2012-05-04T15:34:41-04:00
Last changed2012-05-04T15:34:41-04:00
Abuse contactjohn@swwmail.net
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2012-05-04
StatusAssigned
Delegated rangeAS32889

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

Contacts
RoleNameEmail
registrant Southwestern Wireless, Inc.

Source: https://rdap.arin.net/registry/autnum/32889. 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