AS9999 AT TOKYO Corporation

Japan ATTOKYO APNIC 10 IPv4 prefixes 1 IPv6 prefix

IPv4 addresses

20,224

IPv6 /48 networks

65,536

RPKI

8 valid3 no ROA

Peers and downstreams

Holder

AS name: ATTOKYO
Description: AT TOKYO Corporation
Organisation: AT TOKYO Corporation
Abuse contact: Not published
Assigned: 2000-04-26
Record last changed: 2014-06-18 22:53 UTC

110.44.20.0/22 119.59.64.0/21 165.100.192.0/20 202.13.124.0/22 202.243.223.0/24 203.223.24.0/21 203.80.6.0/23 203.89.128.0/22 211.132.0.0/20 219.99.128.0/20

Upstream graph

Upstreams and their upstreams, from BGP paths

Network health

Grade D · 58/100

partly	Prefixes covered by valid ROAs 8 of 11 announced prefixes are RPKI valid, 3 have no ROA.	18/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
fail	Working abuse contact No abuse contact is published in the registry.	0/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 2014-06-18.	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/9999"><img src="https://ip-fd.net/badge/asn/9999/health.svg" alt="AS9999 network health on IP-FD.net"></a>

Markdown

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

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:        AS9999
as-name:        ATTOKYO
handle:         AS9999
remarks:        AT TOKYO Corporation
technical,administrative:JNIC1-AP (Japan Network Information Center) <hostmaster@nic.ad.jp>
technical,administrative:JP00010132
last changed:   2014-06-18T22:53:04Z
source:         APNIC (RDAP)

Routing data

Updated just now

Registry record

Fetched just now from APNIC RDAP

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/9999

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