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

AS13629 · 

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

Warning: AS13629 (DEEM-INC) announces 4 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS13629
HolderDEEM-INC - Deem, Inc.
AllocationARIN, United States (US), assigned 2016-04-06
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid50% (2 / 4)
Upstreams and peers3

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 4 announced prefixes have no ROA (RPKI not found): 208.94.217.0/24, 208.94.220.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 AS13629 and a max length equal to the prefix length:

    208.94.217.0/24 AS13629 max-length /24
208.94.220.0/24 AS13629 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    1 of 4 announced prefixes have no IRR route object: 208.94.220.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 AS13629 in your RIR’s IRR database (or RADB).

    route: 208.94.220.0/24
origin: AS13629

    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: AS13629 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 2 of 4 announced prefixes have no ROA (RPKI not found): 208.94.217.0/24, 208.94.220.0/24.
  • Info: 2 of 4 announced prefixes are RPKI valid.
  • Warning: 1 of 4 announced prefixes have no IRR route object: 208.94.220.0/24.
  • Info: 3 upstreams and peers, 0 downstream networks seen.
HolderDEEM-INC - Deem, Inc.
IPv4 prefixes4
IPv6 prefixes0
RPKI2 valid · 2 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
208.94.217.0/24 No ROA
208.94.220.0/24 No ROA

Upstreams and peers seen to the left 3

AS174 Cogent Communications, Inc. AS7018 AT&T US AS3356 Lumen AS3356

Announced prefixes 4

208.94.217.0/24 208.94.219.0/24 208.94.220.0/24 208.94.221.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.
NameDEEM-INC
HandleAS13629
RangeAS13629
Statusactive
Registered2016-04-06T19:00:52-04:00
Last changed2016-12-14T13:45:01-05:00
Abuse contactsyseng@deem.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2016-04-06
StatusAssigned
Delegated rangeAS13629

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

Contacts
RoleNameEmail
registrant Deem, Inc.

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