AS138493 Yes Net

Bangladesh YESNET-AS-AP APNIC 2 IPv4 prefixes 0 IPv6 prefixes

IPv4 addresses

512

IPv6 /48 networks

RPKI

2 valid0 no ROA

Peers and downstreams

Holder

AS name: YESNET-AS-AP
Description: Yes Net
Organisation: Yes Net
Abuse contact: Not published
Assigned: 2023-04-26
Registered: 2023-04-27
Record last changed: 2023-07-05 15:49 UTC

103.69.58.0/24 103.69.59.0/24

Upstream graph

Upstreams and their upstreams, from BGP paths

Network health

Grade C · 65/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
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 sahin@yesnet.info 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 2023-07-05.	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/138493"><img src="https://ip-fd.net/badge/asn/138493/health.svg" alt="AS138493 network health on IP-FD.net"></a>

Markdown

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

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

Routing changes

Last 30 days

2026-10-05 03:30 UTC

New neighbour

AS10075

peer

WHOIS

aut-num:        AS138493
as-name:        YESNET-AS-AP
handle:         AS138493
remarks:        Yes Net
technical,administrative:YNA9-AP (Yes Net administrator) <sahin@yesnet.info>
abuse:          IRT-YESNET-BD (IRT-YESNET-BD) <sahin@yesnet.info>
registrant:     ORG-YN4-AP (Yes Net) <sahin@yesnet.info>
registration:   2023-04-27T01:30:39Z
last changed:   2023-07-05T15:49:08Z
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/138493

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