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

AS34694 ·

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

Warning: AS34694 (STWW-AS) announces 3 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS34694
HolderSTWW-AS Stadtwerke Woergl GmbH
AllocationRIPE NCC, Austria (AT), allocated 2005-03-17
Prefixes (IPv4 / IPv6)3 / 1
RPKI valid0% (0 / 4)
Upstreams and peers3
Peering policyOpen

What to fix

  1. Warning

    4 of 4 announced prefixes have no ROA (RPKI not found): 64.34.16.0/22, 83.219.160.0/19, 185.106.188.0/22, 2a06:3980::/29.

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

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

    64.34.16.0/22 AS34694 max-length /22
    83.219.160.0/19 AS34694 max-length /19
    185.106.188.0/22 AS34694 max-length /22
    2a06:3980::/29 AS34694 max-length /29

    Open in RPKI / ROA validator Guide

  2. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  3. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI 4 of 4 announced prefixes have no ROA (RPKI not found): 64.34.16.0/22, 83.219.160.0/19, 185.106.188.0/22, 2a06:3980::/29.
  • Pass: AS34694 announces 3 IPv4 and 1 IPv6 prefixes.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 64.34.16.0/22, 83.219.160.0/19, 185.106.188.0/22, 2a06:3980::/29.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 3 upstreams and peers, 0 downstream networks seen.
HolderSTWW-AS Stadtwerke Woergl GmbH
IPv4 prefixes3
IPv6 prefixes1
RPKI4 not found
Downstream networks0
Routes to fix
PrefixRPKI
64.34.16.0/22 No ROA
83.219.160.0/19 No ROA
185.106.188.0/22 No ROA
2a06:3980::/29 No ROA

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.
NameSTWW-AS
HandleAS34694
RangeAS34694
Statusactive
Registered2005-03-17T16:25:53Z
Last changed2019-12-04T11:18:37Z
Abuse contactabuse@woergl.at
Allocation
Registry (RIR)RIPE NCC
CountryAustria (AT)
Delegated on2005-03-17
StatusAllocated
Delegated rangeAS34694

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

Contacts
RoleNameEmail
registrant Stadtwerke Woergl GmbH
registrant RIPE-NCC-END-MNT
registrant STWW-MNT
abuse Abuse-Contact Stadtwerke Woergl abuse@woergl.at

Source: https://rdap.db.ripe.net/autnum/34694. 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 No IRR as-set is listed.
  • Pass: AS34694 is in PeeringDB as Stadtwerke Woergl GmbH.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2024-04-10.
NetworkStadtwerke Woergl GmbH
AS numberAS34694
Type, Not Disclosed
Websitehttp://www.stww.at
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2024-04-10
Contacts
Abuseabuse@woergl.at

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup