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

AS198590 ·

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

Warning: AS198590 (BEN-KLINKE Ben Klinke) announces 1 IPv4 and 10 IPv6 prefixes. 1 warning

AS pageAS198590
HolderBEN-KLINKE Ben Klinke
AllocationRIPE NCC, Germany (DE), allocated 2026-04-22
Prefixes (IPv4 / IPv6)1 / 10
RPKI valid100% (11 / 11)
Upstreams and peers1

What to fix

  1. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI AS198590 announces 1 IPv4 and 10 IPv6 prefixes.
  • Pass: AS198590 announces 1 IPv4 and 10 IPv6 prefixes.
  • Pass: All 11 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS207252): an outage there takes the whole network off the internet.
HolderBEN-KLINKE Ben Klinke
IPv4 prefixes1
IPv6 prefixes10
RPKI11 valid
Downstream networks3

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.
NameBEN-KLINKE
HandleAS198590
RangeAS198590
Statusactive
Registered2026-04-22T07:06:44Z
Last changed2026-09-29T06:56:00Z
Abuse contactabuse@benklinke.de
Allocation
Registry (RIR)RIPE NCC
CountryGermany (DE)
Delegated on2026-04-22
StatusAllocated
Delegated rangeAS198590

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

Contacts
RoleNameEmail
registrant BEN-KLINKE-MNT
registrant LAGRANGE-AUTO-MNT
registrant Ben Klinke
registrant RIPE-NCC-END-MNT
abuse Abuse contact role object abuse@benklinke.de

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