AS202701 MK-MM Michael Kloos
🇩🇪Org handle: ORG-MK127-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
2 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)1.2×10³⁰
Announced (BGP)1.2×10³⁰
Announced Prefixes
(BGP)4|
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 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.156.204.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 194.5.100.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 2a07:a100::/29 | 🇩🇪 DE | RIPENCC | allocated |
| 2a0c:e840::/29 | 🇩🇪 DE | RIPENCC | allocated |
All 4 announced prefixes of AS202701 →
BGP Neighbours
(seen in AS paths)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 AS202701 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/202701Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/202701" | jq