AS48200 OPTEAMAX-AS Opteamax GmbH
🇩🇪Org handle: ORG-OG38-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
4 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)2,816
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)6|
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 | - | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 193.36.46.0/24 | 🇩🇪 DE | RIPENCC | assigned |
| 194.62.23.0/24 | 🇩🇪 DE | RIPENCC | allocated |
| 2a01:b1c0:10::/48 | 🇩🇪 DE | RIPE | assigned |
All 6 announced prefixes of AS48200 →
BGP Neighbours
(seen in AS paths)Upstreams (6)
Networks AS48200 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (5)
Networks whose own prefixes AS48200 passes on: usually its customers.
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 AS48200 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/48200Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/48200" | jq