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

AS209622 · 

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

Warning: AS209622 (upress-drb uPress Inc) announces 18 IPv4 and 6 IPv6 prefixes. 3 warnings

AS pageAS209622
Holderupress-drb uPress Inc
AllocationRIPE NCC, United States (US), allocated 2019-01-07
Prefixes (IPv4 / IPv6)18 / 6
RPKI valid79% (19 / 24)
Upstreams and peers6

What to fix

  1. Warning

    5 of 24 announced prefixes have no ROA (RPKI not found): 185.108.150.0/24, 185.108.151.0/24, 185.201.148.0/24, 185.201.149.0/24, 185.201.150.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 AS209622 and a max length equal to the prefix length:

    185.108.150.0/24 AS209622 max-length /24
185.108.151.0/24 AS209622 max-length /24
185.201.148.0/24 AS209622 max-length /24
185.201.149.0/24 AS209622 max-length /24
185.201.150.0/24 AS209622 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 24 announced prefixes have no IRR route object: 2a07:4300:61::/48.

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

    route6: 2a07:4300:61::/48
origin: AS209622

    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 5 of 24 announced prefixes have no ROA (RPKI not found): 185.108.150.0/24, 185.108.151.0/24, 185.201.148.0/24, 185.201.149.0/24, 185.201.150.0/24.
  • Pass: AS209622 announces 18 IPv4 and 6 IPv6 prefixes.
  • Warning: 5 of 24 announced prefixes have no ROA (RPKI not found): 185.108.150.0/24, 185.108.151.0/24, 185.201.148.0/24, 185.201.149.0/24, 185.201.150.0/24.
  • Info: 19 of 24 announced prefixes are RPKI valid.
  • Warning: 1 of 24 announced prefixes have no IRR route object: 2a07:4300:61::/48.
  • Info: 6 upstreams and peers, 0 downstream networks seen.
Holderupress-drb uPress Inc
IPv4 prefixes18
IPv6 prefixes6
RPKI19 valid · 5 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
185.108.150.0/24 No ROA
185.108.151.0/24 No ROA
185.201.148.0/24 No ROA
185.201.149.0/24 No ROA
185.201.150.0/24 No ROA

Upstreams and peers seen to the left 6

AS1680 Cellcom Israel AS20473 The Constant Company AS50673 Serverius AS12025 Iron Mountain Data Centers (fka IO Data… AS12400 Partner Communications AS61102 Interhost Networks

Announced prefixes 24

5.154.240.0/24 88.218.116.0/24 88.218.117.0/24 88.218.118.0/24 88.218.119.0/24 155.117.125.0/24 185.108.148.0/23 185.108.148.0/24 185.108.149.0/24 185.108.150.0/24 185.108.151.0/24 185.131.146.0/24 185.131.147.0/24 185.201.148.0/24 185.201.149.0/24 185.201.150.0/24 185.201.151.0/24 194.231.220.0/24 2a07:4300:31::/48 2a07:4300:61::/48 2a07:4300:972::/48 2a07:4300:1609::/48 2a07:4300:1610::/48 2a07:4300:1611::/48

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
Nameupress-drb
HandleAS209622
RangeAS209622
Statusactive
Registered2019-01-07T13:44:53Z
Last changed2020-01-28T16:26:40Z
Abuse contactabuse@upress.io
Allocation
Registry (RIR)RIPE NCC
CountryUnited States (US)
Delegated on2019-01-07
StatusAllocated
Delegated rangeAS209622

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

Contacts
RoleNameEmail
registrant mnt-us-upressinc-1
registrant uPress Inc
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@upress.io

Source: https://rdap.db.ripe.net/autnum/209622. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

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