AS8445 SALZBURG-AG-AS SALZBURG AG fur Energie, Verkehr und Telekommunikation
π¦πΉOrg handle: ORG-SA1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
39total
36 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)267,008
Announced (BGP)250,368
IPv6 Addresses
Allocated (RIR)6.3Γ10Β²βΉ
Announced (BGP)7.1Γ10Β²βΉ
Prefix Limit (IPv4)
500
Prefix Limit (IPv6)
10
Country
π¦πΉ ATRIR
RIPE NCCStatus
allocated
Allocated
1997-08-26
Announced Prefixes
(BGP)39|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | ARINOther IRR | 2026-10-11 | |
| 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 | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 39
1 / 4
Allocated Prefixes
(RIR)37Prefix | Country | RIR | Status |
|---|---|---|---|
| 13.140.96.0/19 | π¦πΉ AT | RIPENCC | allocated |
| 46.247.192.0/19 | π¦πΉ AT | RIPENCC | allocated |
| 82.194.128.0/19 | π¦πΉ AT | RIPENCC | allocated |
| 83.215.0.0/16 | π¦πΉ AT | RIPENCC | allocated |
| 89.26.0.0/17 | π¦πΉ AT | RIPENCC | allocated |
| 91.133.64.0/18 | π¦πΉ AT | RIPENCC | allocated |
| 95.81.32.0/19 | π¦πΉ AT | RIPENCC | allocated |
| 158.220.0.0/18 | π¦πΉ AT | RIPE | assigned |
| 158.220.0.0/19 | π¦πΉ AT | RIPENCC | allocated |
| 158.220.32.0/19 | π¦πΉ AT | RIPENCC | allocated |
1-10 of 37
1 / 4
All 39 announced prefixes of AS8445 β
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS8445 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS8445 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS8445 in the transit part of AS paths: peers, providers or customers.
- AS5404Conova Communications3
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 AS8445 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/8445Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/8445" | jq