AS39519 MYLOC-ENTERPRISE WIIT AG
🇩🇪Org handle: ORG-MMIA3-RIPE
myLoc managed IT AG - Enterprise and Dialup
RIPE NCCallocated
Announced Prefixes (BGP)
6total
5 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 86.105.223.0/24 | 🇩🇪 DE | RIPE | assigned |
| 152.89.92.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 194.107.165.0/24 | 🇩🇪 DE | RIPE | assigned |
| 195.93.242.0/23 | 🇩🇪 DE | RIPENCC | assigned |
| 195.191.98.0/24 | 🇩🇪 DE | RIPENCC | allocated |
| 2001:4ba2::/32 | 🇩🇪 DE | RIPE | assigned |
All 6 announced prefixes of AS39519 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS39519 hands its own prefixes to: transit providers, or peers at an exchange.
- AS24961MYLOC WIIT6
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 AS39519 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/39519Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39519" | jq