AS213043 ATMCOM Asyncronous Transfer Mode Communication AS
🇳🇴Org handle: ORG-ATMC2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)4,096
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
🇳🇴 NORIR
RIPE NCCStatus
allocated
Allocated
2025-02-19
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 194.35.228.0/22 | 🇳🇴 NO | RIPENCC | allocated |
| 194.35.228.0/23 | 🇳🇴 NO | RIPE | assigned |
| 194.35.230.0/23 | 🇳🇴 NO | RIPE | assigned |
| 194.99.40.0/22 | 🇳🇴 NO | RIPENCC | allocated |
| 194.99.40.0/23 | 🇳🇴 NO | RIPE | assigned |
| 194.99.42.0/23 | 🇳🇴 NO | RIPE | assigned |
All 2 announced prefixes of AS213043 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS213043 hands its own prefixes to: transit providers, or peers at an exchange.
- AS50304BLIX Solutions2
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 AS213043 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/213043Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/213043" | jq