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

AS11351 ·

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

Warning: AS11351 (TWC-11351-NORTHEAST) announces 130 IPv4 and 13 IPv6 prefixes. 3 warnings

AS pageAS11351
HolderTWC-11351-NORTHEAST - Charter Communications Inc
AllocationARIN, United States (US), assigned 1998-07-14
Prefixes (IPv4 / IPv6)130 / 13
RPKI valid87% (124 / 143)
Upstreams and peers1

What to fix

  1. Warning

    10 of 143 announced prefixes have no ROA (RPKI not found): 64.30.240.0/20, 136.223.36.0/24, 137.124.0.0/16, 137.124.10.0/24, 150.154.0.0/16 (+5).

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

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

    64.30.240.0/20 AS11351 max-length /20
    136.223.36.0/24 AS11351 max-length /24
    137.124.0.0/16 AS11351 max-length /16
    137.124.10.0/24 AS11351 max-length /24
    150.154.0.0/16 AS11351 max-length /16
    167.254.206.0/24 AS11351 max-length /24
    167.254.207.0/24 AS11351 max-length /24
    192.31.156.0/24 AS11351 max-length /24
    192.67.10.0/24 AS11351 max-length /24
    192.149.230.0/24 AS11351 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    18 of 143 announced prefixes have no IRR route object: 2600:6000:5ea::/48, 98.10.0.0/15, 167.254.207.0/24, 2605:ed00:4c63::/48, 2600:6000:fb34::/48 (+13).

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

    route6: 2600:6000:5ea::/48
    origin: AS11351
    
    route: 98.10.0.0/15
    origin: AS11351
    
    route: 167.254.207.0/24
    origin: AS11351

    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 143 announced prefixes have no ROA (RPKI not found): 64.30.240.0/20, 136.223.36.0/24, 137.124.0.0/16, 137.124.10.0/24, 150.154.0.0/16 (+5).
  • Pass: AS11351 announces 130 IPv4 and 13 IPv6 prefixes.
  • Warning: 10 of 143 announced prefixes have no ROA (RPKI not found): 64.30.240.0/20, 136.223.36.0/24, 137.124.0.0/16, 137.124.10.0/24, 150.154.0.0/16 (+5).
  • Info: 124 of 143 announced prefixes are RPKI valid.
  • Info: The RPKI state of 9 prefixes was not looked up (no ROA of AS11351 covers them; only the first 10 are checked).
  • Warning: 18 of 143 announced prefixes have no IRR route object: 2600:6000:5ea::/48, 98.10.0.0/15, 167.254.207.0/24, 2605:ed00:4c63::/48, 2600:6000:fb34::/48 (+13).
  • Info: One upstream or peer seen (AS7843): an outage there takes the whole network off the internet.
HolderTWC-11351-NORTHEAST - Charter Communications Inc
IPv4 prefixes130
IPv6 prefixes13
RPKI124 valid · 10 not found · 9 not looked up
Without IRR route object18
Downstream networks90
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.
NameTWC-11351-NORTHEAST
HandleAS11351
RangeAS11351
Statusactive
Registered1998-07-14T00:00:00-04:00
Last changed2018-11-27T11:37:55-05:00
Abuse contactabuse@charter.net
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on1998-07-14
StatusAssigned
Delegated rangeAS11351

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

Contacts
RoleNameEmail
registrant Charter Communications Inc

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