AS45794 NTT Singapore - IP Network (RFC 2270)

Singapore NTT-SG-AP-RFC2270 APNIC 1 IPv4 prefix 0 IPv6 prefixes

IPv4 addresses

256

IPv6 /48 networks

RPKI

1 valid0 no ROA

Peers and downstreams

Holder

AS name: NTT-SG-AP-RFC2270
Description: NTT Singapore - IP Network (RFC 2270)
Organisation: NTT Singapore Pte Ltd
Abuse contact: Not published
Assigned: 2009-06-11
Registered: 2009-06-12
Record last changed: 2021-01-13 13:58 UTC

58.65.13.0/24

Upstream graph

Upstreams and their upstreams, from BGP paths

Network health

Grade C · 65/100

pass	Prefixes covered by valid ROAs 1 of 1 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 ap.eis-netops@global.ntt 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 2021-01-13.	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/45794"><img src="https://ip-fd.net/badge/asn/45794/health.svg" alt="AS45794 network health on IP-FD.net"></a>

Markdown

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

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:        AS45794
as-name:        NTT-SG-AP-RFC2270
handle:         AS45794
remarks:        NTT Singapore - IP Network (RFC 2270)
remarks:        For routing information,
remarks:        Please refer to RADB or
remarks:        NTT Communications Routing Registry (NTTCOM)
remarks:        *****************************************************
remarks:        Contacts per RFC2142
remarks:        *****************************************************
administrative: NAA7-AP (NETWORK ADMIN - AS17645) <ap.eis-netops@global.ntt>
registrant:     ORG-NSPL9-AP (NTT Singapore Pte Ltd) <ap.eis-netops@global.ntt>
technical,administrative:IE11-AP (IP ENGINEERING - AS17645) <ap.eis-netops@global.ntt>
abuse:          IRT-NTT-SG (IRT-NTT-SG) <ap.eis-netops@global.ntt>
registration:   2009-06-12T04:49:25Z
last changed:   2021-01-13T13:58:22Z
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/45794

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