Autonomous system
AS12360 KTK KEVAG Telekom GmbH
Residential RIPE Cable/DSL/ISP
Summary
KEVAG Telekom
isp eyeball business legacy
The telecoms arm of the Koblenz municipal utility, selling access and colocation in the middle Rhine region.
What it's used for
- Residential, business and hosted connectivity. 58,880 addresses across 27 prefixes, five IPv6 announcements, and 116 observed BGP neighbours.
Notable
- The largest block,
5.231.128.0/18, is registered asKTK-DYNIP-NET— the dynamic address pool, named as such in the registry rather than only in reverse DNS. - Reverse names for subscriber space are positional under
ktk-ip.de. One sampled address breaks out into a different domain entirely:way2-gw01-colo-ko.nr-city.net, a colocation gateway withkofor Koblenz. - Twelve dated netnames run from
DE-KTK-990409toDE-KTK-20121004, thirteen years of separate applications. - Two IPv6
/32s,2a01:5580::/32and2a02:1628::/32, plus three/48s.
Interesting
- Two
/32s is one more than a provider is normally issued. RIPE gives a member a single allocation and expands it on request, so a second one usually arrives attached to a company that was bought rather than to an application that was filed. - KEVAG is the Koblenz electricity and transport utility, and its telecoms subsidiary is the same municipal pattern seen across German networks: the organisation that already owned the ducts, the poles and a billing relationship with every household in town turned out to be well placed to sell them internet access as well.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 3 exchanges in 2 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| DE-CIX Frankfurt | Frankfurt, Germany | 80.81.194.18 |
| Neutral Internet Exchange | Amsterdam, Netherlands | 193.239.117.98 |
| KleyReX Internet Exchange | Frankfurt, Germany | 193.189.82.55 |
Transit providers
16 upstream, 8 downstream and 38 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 27 prefixes · 58.88K addresses IPv6 5 prefixes
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 32 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS12360- Registry name
- KTK
- Registrant
- KEVAG Telekom GmbH
- Abuse contact
- abuse@noc.ktk.de
- Registered
- 2002-08-21
- Last changed
- 2026-02-09
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- KEVAG Telekom GmbH
- Also known as
- RZ Online
- Network type
- Cable/DSL/ISP
- Scope
- Europe
- Traffic ratio
- Mostly Inbound
- Peering policy
- Selective
- IRR as-set
AS12360:AS-KTK- Present at
- 3 exchanges
- Facilities
- 5 facilities
- Website
- http://kevag-telekom.de/
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 86% valid · 24 valid, 4 with no ROA
- ROAs
- 28 authorising AS12360
- ASPA
- no ASPA record
- IRR
- 96% registered · 27 of 28 announcements 1 other origin
- Route objects
- 31 naming AS12360
Reputation
Classification and threat
Residential Fixed-line consumer ISP. Addresses here are homes.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 432 networks and 1,768 prefixes, as published 2026-10-12. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere