AS201101 NATS (En Route) Ltd

United Kingdom NATSEN-NC RIPE 7 IPv4 prefixes 0 IPv6 prefixes

IPv4 addresses

1,280

IPv6 /48 networks

RPKI

0 valid7 no ROA

Peers and downstreams

Holder

AS name: NATSEN-NC
Description: NATS (En Route) Ltd
Organisation: NATS (En Route) Ltd
Abuse contact: soc@nats.co.uk
Assigned: 2018-07-10
Registered: 2018-07-11
Record last changed: 2018-09-04 12:16 UTC

159.197.101.0/24 159.197.28.0/23 159.197.28.0/24 159.197.29.0/24 159.197.32.0/23 159.197.32.0/24 159.197.33.0/24

Upstream graph

Upstreams and their upstreams, from BGP paths

Network health

Grade E · 40/100

fail	Prefixes covered by valid ROAs 0 of 7 announced prefixes are RPKI valid, 7 have no ROA.	0/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 soc@nats.co.uk is published.	15/15
fail	Publishes a geofeed No geofeed found. Without one, location databases have to guess.	0/10
pass	No prefixes smaller than /24 or /48 All prefixes are /24 (IPv4) or /48 (IPv6) or larger.	10/10
fail	Registry record maintained Last changed 2018-09-04.	0/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/201101"><img src="https://ip-fd.net/badge/asn/201101/health.svg" alt="AS201101 network health on IP-FD.net"></a>

Markdown

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

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

Routing changes

Last 30 days

2026-10-05 04:07 UTC

Relationship changed

AS286

upstream to peer

WHOIS

aut-num:        AS201101
as-name:        NATSEN-NC
org:            ORG-NRL5-RIPE
admin-c:        MG21995-RIPE
tech-c:         MG21995-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         uk-natsen-1-mnt
created:        2018-07-11T12:57:41Z
last-modified:  2018-09-04T12:16:23Z
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/201101

const res = await fetch('https://ip-fd.net/api/v1/asn/201101', {
  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/201101', 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/201101');
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/201101", 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.