AS134663 I-WEB

Pakistan IWEB-AS-AP APNIC 1 IPv4 prefix 1 IPv6 prefix

IPv4 addresses

256

IPv6 /48 networks

RPKI

2 valid0 no ROA

Peers and downstreams

Holder

AS name: IWEB-AS-AP
Description: I-WEB
Organisation: I-WEB
Abuse contact: Not published
Assigned: 2023-01-19
Registered: 2023-01-20
Record last changed: 2024-01-15 21:14 UTC

103.72.138.0/24

Upstream graph

Upstreams and their upstreams, from BGP paths

Network health

Grade B · 85/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 info@iweb.net.pk 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
pass	Registry record maintained Last changed 2024-01-15.	5/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/134663"><img src="https://ip-fd.net/badge/asn/134663/health.svg" alt="AS134663 network health on IP-FD.net"></a>

Markdown

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

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

Routing changes

Last 30 days

2026-10-04 11:19 UTC	Neighbour gone	AS38193	upstream
2026-10-04 11:19 UTC	Prefix gone	103.72.139.0/24

WHOIS

aut-num:        AS134663
as-name:        IWEB-AS-AP
handle:         AS134663
remarks:        I-WEB
registrant:     ORG-IA85-AP (I-WEB) <ceo@iweb.net.pk>
abuse:          IRT-IWEB-PK (IRT-IWEB-PK) <info@iweb.net.pk>
technical,administrative:IPLA36-AP (I-WEB Pvt Ltd administrator) <info@iweb.net.pk>
registration:   2023-01-20T04:30:37Z
last changed:   2024-01-15T21:14:15Z
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/134663

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