AS38488 TELECARD-PAKISTAN-AS-AP Telecard Limited

🇵🇰

Org handle: ORG-TL27-AP

Telecard Limited

APNICallocated

Announced Prefixes (BGP)

9total

8 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)0

Announced (BGP)2,048

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)1.2×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2007-03-20

Announced Prefixes

(BGP)9

Prefix	RPKI	IRR	Last Seen
116.0.42.0/24	Valid	APNICOther IRR	2026-10-11
202.123.240.0/24	Valid	APNICOther IRR	2026-10-11
202.123.242.0/24	Valid	APNICOther IRR	2026-10-11
202.123.244.0/24	Valid	APNIC	2026-10-11
202.123.246.0/24	Valid	APNICOther IRR	2026-10-11
202.123.248.0/24	No ROA	APNICOther IRR	2026-10-11
202.123.249.0/24	No ROA	APNICOther IRR	2026-10-11
202.123.250.0/24	No ROA	APNICOther IRR	2026-10-11
2400:a960::/48	Valid	APNIC	2026-10-11

(seen in AS paths)

Networks AS38488 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

External Links

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS38488 should publish an ASPA object
IPv4 transfers in the APNIC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/38488" | jq