AS138230 Padum Computers

India PADUMC-AS-IN APNIC 3 IPv4 prefixes 0 IPv6 prefixes

IPv4 addresses

512

IPv6 /48 networks

RPKI

3 valid0 no ROA

Peers and downstreams

Holder

AS name: PADUMC-AS-IN
Description: Padum Computers
Organisation: Padum Computers
Abuse contact: Not published
Assigned: 2018-09-18
Registered: 2020-09-03
Record last changed: 2025-09-27 10:35 UTC

103.155.74.0/23 103.155.74.0/24 103.155.75.0/24

Upstream graph

Upstreams and their upstreams, from BGP paths

Network health

Grade C · 70/100

pass	Prefixes covered by valid ROAs 3 of 3 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 PADUM.COMPUTERS@GMAIL.COM 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 2025-09-27.	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/138230"><img src="https://ip-fd.net/badge/asn/138230/health.svg" alt="AS138230 network health on IP-FD.net"></a>

Markdown

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

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

Routing changes

Last 30 days

2026-10-05 06:42 UTC

Neighbour gone

AS137085

upstream

WHOIS

aut-num:        AS138230
as-name:        PADUMC-AS-IN
handle:         AS138230
remarks:        Padum Computers
technical,administrative:NR246-AP (Naresh Rsthore) <PADUM.COMPUTERS@GMAIL.COM>
abuse:          IRT-PADUMC-IN (IRT-PADUMC-IN) <PADUM.COMPUTERS@GMAIL.COM>
registration:   2020-09-03T11:52:53Z
last changed:   2025-09-27T10:35:01Z
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/138230

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