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

AS40068 ·

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

Warning: AS40068 (NEOVERA-AS40068) announces 3 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS40068
HolderNEOVERA-AS40068 - Neovera, Inc.
AllocationARIN, United States (US), assigned 2006-06-19
Prefixes (IPv4 / IPv6)3 / 0
RPKI valid0% (0 / 3)
Upstreams and peers3
Peering policySelective

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): 208.69.168.0/21, 208.77.248.0/21, 208.95.240.0/21.

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

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

    208.69.168.0/21 AS40068 max-length /21
    208.77.248.0/21 AS40068 max-length /21
    208.95.240.0/21 AS40068 max-length /21

    Open in RPKI / ROA validator Guide

  3. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS40068 announces 3 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 3 of 3 announced prefixes have no ROA (RPKI not found): 208.69.168.0/21, 208.77.248.0/21, 208.95.240.0/21.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 3 upstreams and peers, 1 downstream networks seen.
HolderNEOVERA-AS40068 - Neovera, Inc.
IPv4 prefixes3
IPv6 prefixes0
RPKI3 not found
Downstream networks1
Routes to fix
PrefixRPKI
208.69.168.0/21 No ROA
208.77.248.0/21 No ROA
208.95.240.0/21 No ROA

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.
NameNEOVERA-AS40068
HandleAS40068
RangeAS40068
Statusactive
Registered2006-06-19T17:14:18-04:00
Last changed2026-10-27T10:16:12-04:00
Abuse contactaccounting@neovera.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2006-06-19
StatusAssigned
Delegated rangeAS40068

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

Contacts
RoleNameEmail
registrant Neovera, Inc.
technical Wahab Gull wahab.gull@neovera.com
noc Network Operations Center noc@neovera.com
technical Andrew Stueve andrew.stueve@neovera.com
abuse ABUSE accounting@neovera.com

Source: https://rdap.arin.net/registry/autnum/40068. 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 No public NOC, policy or technical contact.
  • Pass: AS40068 is in PeeringDB as Neovera, Inc..
  • Info: Peering policy: Selective.
  • Info: No internet exchange ports are listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkNeovera, Inc.
AS numberAS40068
TypeContent, Regional
Websitehttp://www.neovera.com
IRR as-setAS40068:AS-CUSTOMERS
Prefixes (IPv4 / IPv6)30 / 2
Traffic20-100Mbps, Mostly Outbound
Peering policySelective
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup