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

AS393775 ·

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

Warning: AS393775 (IPP-AS) announces 48 IPv4 and 2 IPv6 prefixes. 3 warnings

AS pageAS393775
HolderIPP-AS - IP Pathways, LLC
AllocationARIN, United States (US), assigned 2015-01-20
Prefixes (IPv4 / IPv6)48 / 2
RPKI valid94% (47 / 50)
Upstreams and peers2
Peering policyOpen

What to fix

  1. Warning

    3 of 50 announced prefixes have no ROA (RPKI not found): 63.76.52.0/22, 198.135.140.0/24, 199.45.254.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 AS393775 and a max length equal to the prefix length:

    63.76.52.0/22 AS393775 max-length /22
    198.135.140.0/24 AS393775 max-length /24
    199.45.254.0/24 AS393775 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    5 of 50 announced prefixes have no IRR route object: 209.127.255.0/24, 199.116.141.0/24, 199.116.143.0/24, 199.116.140.0/24, 63.76.52.0/22.

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

    route: 209.127.255.0/24
    origin: AS393775
    
    route: 199.116.141.0/24
    origin: AS393775
    
    route: 199.116.143.0/24
    origin: AS393775

    Open in ASN & BGP prefix lookup

  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 3 of 50 announced prefixes have no ROA (RPKI not found): 63.76.52.0/22, 198.135.140.0/24, 199.45.254.0/24.
  • Pass: AS393775 announces 48 IPv4 and 2 IPv6 prefixes.
  • Warning: 3 of 50 announced prefixes have no ROA (RPKI not found): 63.76.52.0/22, 198.135.140.0/24, 199.45.254.0/24.
  • Info: 47 of 50 announced prefixes are RPKI valid.
  • Warning: 5 of 50 announced prefixes have no IRR route object: 209.127.255.0/24, 199.116.141.0/24, 199.116.143.0/24, 199.116.140.0/24, 63.76.52.0/22.
  • Info: 2 upstreams and peers, 1 downstream networks seen.
HolderIPP-AS - IP Pathways, LLC
IPv4 prefixes48
IPv6 prefixes2
RPKI47 valid · 3 not found
Without IRR route object5
Downstream networks1
Routes to fix
PrefixRPKI
63.76.52.0/22 No ROA
198.135.140.0/24 No ROA
199.45.254.0/24 No ROA

Upstreams and peers seen to the left 2

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.
NameIPP-AS
HandleAS393775
RangeAS393775
Statusactive
Registered2015-01-20T13:25:23-05:00
Last changed2023-12-28T12:21:13-05:00
Abuse contactnoc@ippathways.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2015-01-20
StatusAssigned
Delegated rangeAS393775

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

Contacts
RoleNameEmail
registrant IP Pathways, LLC

Source: https://rdap.arin.net/registry/autnum/393775. 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: AS393775 is in PeeringDB as IP Pathways, LLC.
  • Info: Peering policy: Open.
  • Info: Present at 4 internet exchanges with 4 ports (40G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkIP Pathways, LLC
AS numberAS393775
TypeNSP, North America
Websitehttp://www.ippathways.com
IRR as-setAS-IPPATHWAYS
Prefixes (IPv4 / IPv6)200 / 10
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-06-22

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup