AS4818 DIGIIX-AP - DiGi Telecommunications Sdn. Bhd.
🇲🇾Org handle: ORG-DTSB1-AP
DiGi Telecommunications Sdn. Bhd.
APNICallocated
Announced Prefixes (BGP)
19total
13 IPv46 IPv6
IPv4 Addresses
Allocated (RIR)331,776
Announced (BGP)599,040
IPv6 Addresses
Allocated (RIR)2.3×10²⁹
Announced (BGP)3.1×10²⁹
Routing hygiene
Score 5/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
4
diversity 54/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 19 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Listed on the threat map (2026-10-24)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)19|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | APNICOther IRR | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 | |
| Valid | APNIC | 2026-10-26 | |
| Valid | APNICOther IRR | 2026-10-26 | |
| Valid | APNICOther IRR | 2026-10-26 | |
| Valid | APNICOther IRR | 2026-10-26 | |
| Valid | APNICOther IRR | 2026-10-26 | |
| Valid | APNICOther IRR | 2026-10-26 | |
| Valid | APNICOther IRR | 2026-10-26 | |
| Valid | APNICOther IRR | 2026-10-26 |
1-10 of 19
1 / 2
Allocated Prefixes
(RIR)7Prefix | Country | RIR | Status |
|---|---|---|---|
| 49.124.0.0/15 | 🇲🇾 MY | APNIC | allocated |
| 115.164.0.0/16 | 🇲🇾 MY | APNIC | allocated |
| 182.62.0.0/15 | 🇲🇾 MY | APNIC | allocated |
| 210.48.192.0/20 | 🇲🇾 MY | APNIC | allocated |
| 2001:4458::/32 | 🇲🇾 MY | APNIC | allocated |
| 2401:a120::/32 | 🇲🇾 MY | APNIC | allocated |
| 2402:1980::/32 | 🇲🇾 MY | APNIC | allocated |
All 19 announced prefixes of AS4818 →
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS4818 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS4818 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/4818Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/4818" | jq