AS208973 Gemeente Haarlem

Netherlands haarlem RIPE 1 IPv4 prefix 1 IPv6 prefix

IPv4 addresses

1,024

IPv6 /48 networks

RPKI

2 valid0 no ROA

Peers and downstreams

Holder

AS name: haarlem
Description: Gemeente Haarlem
Organisation: Gemeente Haarlem
Registered in: Haarlem, Netherlands
Abuse contact: netwerkbeheer@haarlem.nl
Assigned: 2019-05-01
Registered: 2019-05-02
Record last changed: 2019-06-03 13:48 UTC

45.67.104.0/22

Upstream graph

Upstreams and their upstreams, from BGP paths

Network health

Grade B · 80/100

pass	Prefixes covered by valid ROAs 2 of 2 announced prefixes are RPKI valid.	25/25
pass	No RPKI invalid announcements None of the announcements is RPKI invalid.	10/10
pass	Announces IPv6 1 IPv6 prefix.	15/15
partly	More than one upstream 1 upstream seen in BGP.	5/10
pass	Working abuse contact netwerkbeheer@haarlem.nl 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 2019-06-03.	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/208973"><img src="https://ip-fd.net/badge/asn/208973/health.svg" alt="AS208973 network health on IP-FD.net"></a>

Markdown

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

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

Routing changes

Last 30 days

No changes recorded in the last 30 days. Changes are recorded each time the routing data of this AS is refreshed. Get alerts in real time.

WHOIS

aut-num:        AS208973
as-name:        haarlem
org:            ORG-GH63-RIPE
admin-c:        DD14134-RIPE
tech-c:         DD14134-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         mnt-nl-haarlem-1
created:        2019-05-02T11:22:05Z
last-modified:  2019-06-03T13:48:35Z
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/208973

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