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

AS34928 ·

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

Warning: AS34928 (regioitaachen regio iT gesellschaft fur…) announces 4 IPv4 and 1 IPv6 prefixes. 2 warnings

AS pageAS34928
Holderregioitaachen regio iT gesellschaft fur informationstechnologie mbh
AllocationRIPE NCC, Germany (DE), allocated 2006-12-07
Prefixes (IPv4 / IPv6)4 / 1
RPKI valid0% (0 / 5)
Upstreams and peers1
Peering policyOpen

What to fix

  1. Warning

    5 of 5 announced prefixes have no ROA (RPKI not found): 91.102.136.0/21, 91.102.141.0/24, 185.98.92.0/22, 194.99.73.0/24, 2a02:16f0::/32.

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

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

    91.102.136.0/21 AS34928 max-length /21
    91.102.141.0/24 AS34928 max-length /24
    185.98.92.0/22 AS34928 max-length /22
    194.99.73.0/24 AS34928 max-length /24
    2a02:16f0::/32 AS34928 max-length /32

    Open in RPKI / ROA validator Guide

  2. 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 5 of 5 announced prefixes have no ROA (RPKI not found): 91.102.136.0/21, 91.102.141.0/24, 185.98.92.0/22, 194.99.73.0/24, 2a02:16f0::/32.
  • Pass: AS34928 announces 4 IPv4 and 1 IPv6 prefixes.
  • Warning: 5 of 5 announced prefixes have no ROA (RPKI not found): 91.102.136.0/21, 91.102.141.0/24, 185.98.92.0/22, 194.99.73.0/24, 2a02:16f0::/32.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS34309): an outage there takes the whole network off the internet.
Holderregioitaachen regio iT gesellschaft fur informationstechnologie mbh
IPv4 prefixes4
IPv6 prefixes1
RPKI5 not found
Downstream networks0
Routes to fix
PrefixRPKI
91.102.136.0/21 No ROA
91.102.141.0/24 No ROA
185.98.92.0/22 No ROA
194.99.73.0/24 No ROA
2a02:16f0::/32 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.
Nameregioitaachen
HandleAS34928
RangeAS34928
Statusactive
Registered2006-12-07T10:18:11Z
Last changed2021-07-06T08:21:06Z
Abuse contactripe@regioit-aachen.de
Allocation
Registry (RIR)RIPE NCC
CountryGermany (DE)
Delegated on2006-12-07
StatusAllocated
Delegated rangeAS34928

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

Contacts
RoleNameEmail
registrant regio iT gesellschaft fur informationstechnologie mbh
registrant REGIOITAACHEN-MNT
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role ripe@regioit-aachen.de

Source: https://rdap.db.ripe.net/autnum/34928. 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 public NOC, policy or technical contact.
  • Pass: AS34928 is in PeeringDB as regio iT aachen.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
Networkregio iT aachen
AS numberAS34928
TypeContent, Regional
Websitehttp://www.regioit-aachen.de
IRR as-setAS-REGIOITAACHEN
Prefixes (IPv4 / IPv6)1 / 0
Traffic20-100Mbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup