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

AS3319 ·

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

Warning: AS3319 (URAN) announces 41 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS3319
HolderURAN User Association of Ukrainian Research and Academic Network URAN
AllocationRIPE NCC, Ukraine (UA), allocated 1995-02-22
Prefixes (IPv4 / IPv6)41 / 0
RPKI valid98% (40 / 41)
Upstreams and peers1

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    1 of 41 announced prefixes have no ROA (RPKI not found): 195.178.152.0/22.

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

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

    195.178.152.0/22 AS3319 max-length /22

    Open in RPKI / ROA validator Guide

  3. Warning

    2 of 41 announced prefixes have no IRR route object: 77.47.154.0/24, 77.47.155.0/24.

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

    route: 77.47.154.0/24
    origin: AS3319
    
    route: 77.47.155.0/24
    origin: AS3319

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS3319 announces 41 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 1 of 41 announced prefixes have no ROA (RPKI not found): 195.178.152.0/22.
  • Info: 40 of 41 announced prefixes are RPKI valid.
  • Warning: 2 of 41 announced prefixes have no IRR route object: 77.47.154.0/24, 77.47.155.0/24.
  • Info: One upstream or peer seen (AS12687): an outage there takes the whole network off the internet.
HolderURAN User Association of Ukrainian Research and Academic Network URAN
IPv4 prefixes41
IPv6 prefixes0
RPKI40 valid · 1 not found
Without IRR route object2
Downstream networks0
Routes to fix
PrefixRPKI
195.178.152.0/22 No ROA

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.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameURAN
HandleAS3319
RangeAS3319
Statusactive
Registered2002-05-10T12:48:13Z
Last changed2020-06-04T09:31:04Z
Abuse contactabuse@uran.ua
Allocation
Registry (RIR)RIPE NCC
CountryUkraine (UA)
Delegated on1995-02-22
StatusAllocated
Delegated rangeAS3319

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

Contacts
RoleNameEmail
registrant User Association of Ukrainian Research and Academic Network URAN
registrant RIPE-NCC-END-MNT
registrant URAN-MNT
abuse URAN Operations abuse@uran.ua

Source: https://rdap.db.ripe.net/autnum/3319. 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