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

AS1339 ·

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

Warning: AS1339 (ANSBB-ASNNET-1) announces 12 IPv4 and 2 IPv6 prefixes. 3 warnings

AS pageAS1339
HolderANSBB-ASNNET-1 - Verizon Business
AllocationARIN, United States (US), assigned 1994-11-23
Prefixes (IPv4 / IPv6)12 / 2
RPKI valid0% (0 / 14)
Upstreams and peers1

What to fix

  1. Warning

    10 of 14 announced prefixes have no ROA (RPKI not found): 63.64.54.0/24, 152.196.0.0/22, 152.196.0.0/24, 152.196.110.0/23, 152.196.112.0/23 (+5).

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

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

    63.64.54.0/24 AS1339 max-length /24
    152.196.0.0/22 AS1339 max-length /22
    152.196.0.0/24 AS1339 max-length /24
    152.196.110.0/23 AS1339 max-length /23
    152.196.112.0/23 AS1339 max-length /23
    152.196.112.0/24 AS1339 max-length /24
    152.196.114.0/23 AS1339 max-length /23
    152.196.116.0/23 AS1339 max-length /23
    152.196.123.0/24 AS1339 max-length /24
    152.196.124.0/24 AS1339 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    14 of 14 announced prefixes have no IRR route object: 152.196.0.0/24, 152.196.0.0/22, 152.196.124.0/24, 152.196.110.0/23, 63.64.54.0/24 (+9).

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

    route: 152.196.0.0/24
    origin: AS1339
    
    route: 152.196.0.0/22
    origin: AS1339
    
    route: 152.196.124.0/24
    origin: AS1339

    Open in ASN & BGP prefix lookup

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 10 of 14 announced prefixes have no ROA (RPKI not found): 63.64.54.0/24, 152.196.0.0/22, 152.196.0.0/24, 152.196.110.0/23, 152.196.112.0/23 (+5).
  • Pass: AS1339 announces 12 IPv4 and 2 IPv6 prefixes.
  • Warning: 10 of 14 announced prefixes have no ROA (RPKI not found): 63.64.54.0/24, 152.196.0.0/22, 152.196.0.0/24, 152.196.110.0/23, 152.196.112.0/23 (+5).
  • Info: The RPKI state of 4 prefixes was not looked up (no ROA of AS1339 covers them; only the first 10 are checked).
  • Warning: 14 of 14 announced prefixes have no IRR route object: 152.196.0.0/24, 152.196.0.0/22, 152.196.124.0/24, 152.196.110.0/23, 63.64.54.0/24 (+9).
  • Info: One upstream or peer seen (AS701): an outage there takes the whole network off the internet.
HolderANSBB-ASNNET-1 - Verizon Business
IPv4 prefixes12
IPv6 prefixes2
RPKI10 not found · 4 not looked up
Without IRR route object14
Downstream networks2
Routes to fix

Upstreams and peers seen to the left 1

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.
NameANSBB-ASNNET-1
HandleAS1321
RangeAS1321 – AS1340
Statusactive
Registered1994-11-23T00:00:00-05:00
Last changed2024-03-04T11:28:24-05:00
Abuse contactabuse@verizon.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on1994-11-23
StatusAssigned
Delegated rangeAS1321 – AS1340

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

Contacts
RoleNameEmail
registrant Verizon Business

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