AS43180 TRUNKNETWORKS-AS Trunk Networks LTD
πΈπ¨Org handle: ORG-TNL61-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
38total
35 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)8,192
Announced (BGP)12,288
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)2.3Γ10Β²βΉ
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
10
Country
πΈπ¨ SCRIR
RIPE NCCStatus
allocated
Allocated
2007-06-20
Announced Prefixes
(BGP)39|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
45.14.164.0/24MOAS | Invalid | - | 2026-10-10 |
| Valid | Other IRRRIPE | 2026-10-10 | |
| Valid | Other IRRRIPE | 2026-10-10 | |
| Valid | Other IRRRIPE | 2026-10-10 | |
| Valid | Other IRRRIPE | 2026-10-10 | |
| Valid | Other IRRRIPE | 2026-10-10 | |
| Valid | Other IRRRIPE | 2026-10-10 | |
| Valid | Other IRRRIPE | 2026-10-10 |
1-10 of 39
1 / 4
Allocated Prefixes
(RIR)26Prefix | Country | RIR | Status |
|---|---|---|---|
| 2.57.241.0/24 | πΈπ¬ SG | RIPE | assigned |
| 31.207.4.0/24 | πΊπΈ US | RIPE | assigned |
| 82.23.16.0/24 | πΈπ¬ SG | RIPE | assigned |
| 82.23.25.0/24 | πΈπ¬ SG | RIPE | assigned |
| 82.23.28.0/24 | πΈπ¬ SG | RIPE | assigned |
| 82.23.30.0/24 | πΈπ¬ SG | RIPE | assigned |
| 82.23.31.0/24 | πΈπ¬ SG | RIPE | assigned |
| 82.23.34.0/24 | πΈπ¬ SG | RIPE | assigned |
| 82.23.39.0/24 | πΈπ¬ SG | RIPE | assigned |
| 82.23.41.0/24 | πΈπ¬ SG | RIPE | assigned |
1-10 of 26
1 / 3
All 39 announced prefixes of AS43180 β
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS43180 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS43180 passes on: usually its customers.
- AS211019Servers Guru Moula World1
Transfer History
Registry transfers of AS43180 between organisations.
- AS43180Transfer Β·
- AS43180Transfer Β·
- AS43180Transfer Β·
ASPA
No ASPA
Abuse Contact
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 AS43180 should publish an ASPA object
- IPv4 transfers in the RIPE NCC 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/43180Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/43180" | jq