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

AS63174 · 

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

Warning: AS63174 (LAS-COLO2) announces 3 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS63174
HolderLAS-COLO2 - Blue Shield of California
AllocationARIN, United States (US), assigned 2014-08-28
Prefixes (IPv4 / IPv6)3 / 0
RPKI valid0% (0 / 3)
Upstreams and peers5

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

    3 of 3 announced prefixes have no ROA (RPKI not found): 165.253.43.0/24, 165.253.64.0/23, 165.253.144.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 AS63174 and a max length equal to the prefix length:

    165.253.43.0/24 AS63174 max-length /24
165.253.64.0/23 AS63174 max-length /23
165.253.144.0/24 AS63174 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

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

    route: 165.253.43.0/24
origin: AS63174

    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: AS63174 announces 3 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 3 of 3 announced prefixes have no ROA (RPKI not found): 165.253.43.0/24, 165.253.64.0/23, 165.253.144.0/24.
  • Warning: 1 of 3 announced prefixes have no IRR route object: 165.253.43.0/24.
  • Info: 5 upstreams and peers, 0 downstream networks seen.
HolderLAS-COLO2 - Blue Shield of California
IPv4 prefixes3
IPv6 prefixes0
RPKI3 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
165.253.43.0/24 No ROA
165.253.64.0/23 No ROA
165.253.144.0/24 No ROA

Upstreams and peers seen to the left 5

AS701 Verizon AS174 Cogent Communications, Inc. AS3356 Lumen AS3356 AS22911 SINAP-TIX AS23005 Switch, Ltd.

Announced prefixes 3

165.253.43.0/24 165.253.64.0/23 165.253.144.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.
NameLAS-COLO2
HandleAS63174
RangeAS63174
Statusactive
Registered2014-08-28T15:34:46-04:00
Last changed2014-08-28T15:34:46-04:00
Abuse contactabuse@blueshieldca.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2014-08-28
StatusAssigned
Delegated rangeAS63174

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

Contacts
RoleNameEmail
registrant Blue Shield of California

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