AS213518 Next Kraftwerke GmbH

Germany next RIPE 4 IPv4 prefixes 0 IPv6 prefixes

IPv4 addresses

1,024

IPv6 /48 networks

RPKI

4 valid0 no ROA

Peers and downstreams

Holder

AS name: next
Description: Next Kraftwerke GmbH
Organisation: Next Kraftwerke GmbH
Registered in: Köln, Germany
Abuse contact: abuse@next-kraftwerke.de
Assigned: 2025-01-26
Registered: 2025-01-27
Record last changed: 2026-04-23 14:22 UTC

79.170.96.0/24 79.170.97.0/24 79.170.99.0/24 91.220.16.0/24

Upstream graph

Upstreams and their upstreams, from BGP paths

Network health

Grade B · 80/100

pass	Prefixes covered by valid ROAs 4 of 4 announced prefixes are RPKI valid.	25/25
pass	No RPKI invalid announcements None of the announcements is RPKI invalid.	10/10
fail	Announces IPv6 No IPv6 prefixes are announced.	0/15
partly	More than one upstream 1 upstream seen in BGP.	5/10
pass	Working abuse contact abuse@next-kraftwerke.de is published.	15/15
pass	Publishes a geofeed A geofeed (RFC 8805) tells where the address space is used.	10/10
pass	No prefixes smaller than /24 or /48 All prefixes are /24 (IPv4) or /48 (IPv6) or larger.	10/10
pass	Registry record maintained Last changed 2026-04-23.	5/5

Built from the announced prefixes, RPKI, the registry record and geofeeds. Checks without data are not counted. Also in the API.

Show this on your website

HTML

<a href="https://ip-fd.net/asn/213518"><img src="https://ip-fd.net/badge/asn/213518/health.svg" alt="AS213518 network health on IP-FD.net"></a>

Markdown

[![AS213518 network health](https://ip-fd.net/badge/asn/213518/health.svg)](https://ip-fd.net/asn/213518)

Use rpki.svg instead of health.svg for the RPKI badge.

Routing changes

Last 30 days

2026-10-05 12:50 UTC	New neighbour	AS3320	peer
2026-10-05 12:50 UTC	New prefix	91.220.16.0/24

WHOIS

aut-num:        AS213518
as-name:        next
org:            ORG-NKG5-RIPE
admin-c:        NA9130-RIPE
tech-c:         NT4891-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         NXK-MNT
created:        2025-01-27T12:59:26Z
last-modified:  2026-04-23T14:22:06Z
source:         RIPE
% 4 routing policy lines (import/export) not shown

Routing data

Updated just now

Registry record

Fetched just now from RIPE

Prefixes and neighbours come from the RIPE RIS route collectors. Data older than 5 minutes is refreshed when this page is opened.

API

curl -H "X-API-Key: YOUR_KEY" https://ip-fd.net/api/v1/asn/213518

const res = await fetch('https://ip-fd.net/api/v1/asn/213518', {
  headers: { 'X-API-Key': 'YOUR_KEY' }
});
const data = await res.json();
console.log(data);

import requests

r = requests.get('https://ip-fd.net/api/v1/asn/213518', headers={'X-API-Key': 'YOUR_KEY'}, timeout=10)
r.raise_for_status()
print(r.json())

<?php
$ch = curl_init('https://ip-fd.net/api/v1/asn/213518');
curl_setopt($ch, CURLOPT_HTTPHEADER, ['X-API-Key: YOUR_KEY']);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$data = json_decode(curl_exec($ch), true);
print_r($data);

req, _ := http.NewRequest("GET", "https://ip-fd.net/api/v1/asn/213518", nil)
req.Header.Set("X-API-Key", "YOUR_KEY")
res, err := http.DefaultClient.Do(req)
if err != nil {
    log.Fatal(err)
}
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Works without a key at a lower rate. Get a free key.