AS18156 BITNET-ID-AP BITNET ISP AS
🇮🇩Org handle: A9186214
BITNET ISP AS
APNICallocated
Announced Prefixes (BGP)
12total
12 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)8,192
Announced (BGP)12,544
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)12|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 |
1-10 of 12
1 / 2
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 202.147.224.0/19 | 🇮🇩 ID | APNIC | allocated |
All 12 announced prefixes of AS18156 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS18156 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS18156 passes on: usually its customers.
- AS38770TM ID PT. Tangara Mitrakom7
ASPA
No ASPA
External Links
Learn more
- 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 AS18156 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
Open https://api.ipctl.io/v1/asn/18156Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/18156" | jq