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

AS3354 ·

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

Warning: AS3354 (THENET-AS-3354) announces 14 IPv4 and 2 IPv6 prefixes. 3 warnings

AS pageAS3354
HolderTHENET-AS-3354 - University of Texas System
AllocationARIN, United States (US), assigned 1993-12-10
Prefixes (IPv4 / IPv6)14 / 2
RPKI valid13% (2 / 16)
Upstreams and peers1

What to fix

  1. Warning

    10 of 16 announced prefixes have no ROA (RPKI not found): 192.138.168.0/24, 198.153.169.0/24, 198.213.0.0/16, 198.214.0.0/16, 198.214.2.0/24 (+5).

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

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

    192.138.168.0/24 AS3354 max-length /24
    198.153.169.0/24 AS3354 max-length /24
    198.213.0.0/16 AS3354 max-length /16
    198.214.0.0/16 AS3354 max-length /16
    198.214.2.0/24 AS3354 max-length /24
    198.214.4.0/24 AS3354 max-length /24
    198.214.6.0/24 AS3354 max-length /24
    206.77.0.0/16 AS3354 max-length /16
    206.77.62.0/24 AS3354 max-length /24
    206.77.63.0/24 AS3354 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    8 of 16 announced prefixes have no IRR route object: 206.77.63.0/24, 2605:2800:101::/48, 206.77.62.0/24, 2605:2800:100::/40, 198.214.2.0/24 (+3).

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

    route: 206.77.63.0/24
    origin: AS3354
    
    route6: 2605:2800:101::/48
    origin: AS3354
    
    route: 206.77.62.0/24
    origin: AS3354

    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 16 announced prefixes have no ROA (RPKI not found): 192.138.168.0/24, 198.153.169.0/24, 198.213.0.0/16, 198.214.0.0/16, 198.214.2.0/24 (+5).
  • Pass: AS3354 announces 14 IPv4 and 2 IPv6 prefixes.
  • Warning: 10 of 16 announced prefixes have no ROA (RPKI not found): 192.138.168.0/24, 198.153.169.0/24, 198.213.0.0/16, 198.214.0.0/16, 198.214.2.0/24 (+5).
  • Info: 2 of 16 announced prefixes are RPKI valid.
  • Info: The RPKI state of 4 prefixes was not looked up (no ROA of AS3354 covers them; only the first 10 are checked).
  • Warning: 8 of 16 announced prefixes have no IRR route object: 206.77.63.0/24, 2605:2800:101::/48, 206.77.62.0/24, 2605:2800:100::/40, 198.214.2.0/24 (+3).
  • Info: One upstream or peer seen (AS6922): an outage there takes the whole network off the internet.
HolderTHENET-AS-3354 - University of Texas System
IPv4 prefixes14
IPv6 prefixes2
RPKI2 valid · 10 not found · 4 not looked up
Without IRR route object8
Downstream networks0
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.
NameTHENET-AS-3354
HandleAS3354
RangeAS3354
Statusactive
Registered1993-12-10T00:00:00-05:00
Last changed2012-04-02T10:31:36-04:00
Abuse contactabuse@the.net
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on1993-12-10
StatusAssigned
Delegated rangeAS3354

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

Contacts
RoleNameEmail
registrant University of Texas System
technical Network Operations Center tech-contact@ots.utsystem.edu

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