AS48441 MAGLAN-AS MagLAN LLC
🇷🇺Org handle: ORG-SWLL2-RIPE
ISP MagLAN
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)3,072
Announced (BGP)3,072
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 94.247.56.0/21 | 🇷🇺 RU | RIPENCC | allocated |
| 185.33.236.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 2a00:d0e0::/32 | 🇷🇺 RU | RIPENCC | allocated |
All 2 announced prefixes of AS48441 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS48441 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8359MTS PJSC2
Downstreams (2)
Networks whose own prefixes AS48441 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS48441 in the transit part of AS paths: peers, providers or customers.
- AS12389ROSTELECOM PJSC Rostelecom1
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS48441 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/48441Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/48441" | jq