AS47569 ERLANG-AS Erlang company Ltd.
🇷🇺Org handle: ORG-EcL10-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
16total
16 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)4,096
Announced (BGP)4,096
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)16|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 16
1 / 2
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 79.110.240.0/20 | 🇷🇺 RU | RIPENCC | assigned |
All 16 announced prefixes of AS47569 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS47569 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS47569 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS47569 in the transit part of AS paths: peers, providers or customers.
- AS9002RETN Limited11
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 AS47569 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/47569Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/47569" | jq