AS200683 EP-Puehringer Elektro Puehringer GmbH
🇦🇹Org handle: ORG-EPG7-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 6/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 38/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 4 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.68.4.0/22 | 🇦🇹 AT | RIPENCC | allocated |
| 185.231.67.0/24 | 🇦🇹 AT | RIPENCC | allocated |
| 188.64.212.0/22 | 🇦🇹 AT | RIPENCC | allocated |
| 2a05:1400::/29 | 🇦🇹 AT | RIPENCC | allocated |
All 4 announced prefixes of AS200683 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS200970 | 🇦🇹RIEPERT Riepert Informationstechnologie GmbH |
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/200683Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200683" | jq