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

AS400798 ·

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

Warning: AS400798 (PITIX-INFRA) announces 1 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS400798
HolderPITIX-INFRA - Pittsburgh Internet Exchange
AllocationARIN, United States (US), assigned 2022-09-22
Prefixes (IPv4 / IPv6)1 / 1
RPKI valid0% (0 / 2)
Upstreams and peers2
Peering policyOpen

What to fix

  1. Warning

    2 of 2 announced prefixes have no ROA (RPKI not found): 23.143.152.0/24, 2602:faaa::/36.

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

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

    23.143.152.0/24 AS400798 max-length /24
    2602:faaa::/36 AS400798 max-length /36

    Open in RPKI / ROA validator Guide

  2. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB 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 2 of 2 announced prefixes have no ROA (RPKI not found): 23.143.152.0/24, 2602:faaa::/36.
  • Pass: AS400798 announces 1 IPv4 and 1 IPv6 prefixes.
  • Warning: 2 of 2 announced prefixes have no ROA (RPKI not found): 23.143.152.0/24, 2602:faaa::/36.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderPITIX-INFRA - Pittsburgh Internet Exchange
IPv4 prefixes1
IPv6 prefixes1
RPKI2 not found
Downstream networks0
Routes to fix
PrefixRPKI
23.143.152.0/24 No ROA
2602:faaa::/36 No ROA

Upstreams and peers seen to the left 2

Announced prefixes 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.
NamePITIX-INFRA
HandleAS400798
RangeAS400798
Statusactive
Registered2022-09-22T13:59:25-04:00
Last changed2022-09-22T13:59:25-04:00
Abuse contactbmannella@pit-ix.net
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2022-09-22
StatusAssigned
Delegated rangeAS400798

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

Contacts
RoleNameEmail
registrant Pittsburgh Internet Exchange

Source: https://rdap.arin.net/registry/autnum/400798. 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 IRR as-set is listed.
  • Pass: AS400798 is in PeeringDB as Pittsburgh Internet Exchange Services.
  • Info: Peering policy: Open.
  • Info: Present at 1 internet exchanges with 2 ports (200G in total).
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2023-06-28.
NetworkPittsburgh Internet Exchange Services (Pittsburgh Internet Exchange Services)
AS numberAS400798
Type, Not Disclosed
Websitehttps://pit-ix.net
Prefixes (IPv4 / IPv6)1 / 1
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2023-06-28

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup