Routing security
AS50920 KABEL-BRAUNAU
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS50920 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a04:f680::/29 | RPKI valid | IRR | 34 |
| 81.16.24.0/22 | RPKI valid | IRR | 53 |
| 92.39.160.0/20 | RPKI valid | IRR | 53 |
| 92.243.83.0/24 | RPKI valid | IRR | 53 |
| 149.62.33.0/24 | RPKI valid | IRR | 53 |
| 176.61.160.0/21 | RPKI valid | IRR | 53 |
| 185.64.60.0/22 | RPKI valid | IRR | 53 |
| 188.213.232.0/24 | RPKI valid | IRR | 53 |
| 193.28.91.0/24 | RPKI valid | IRR | 53 |
| 193.28.229.0/24 | RPKI valid | IRR | 53 |
| 193.151.60.0/22 | RPKI valid | IRR | 53 |
| 194.103.64.0/20 | RPKI valid | IRR | 53 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS50920 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 81.16.24.0/22 | /24 | RIPENCC |
| 92.39.160.0/20 | /24 | RIPENCC |
| 92.243.83.0/24 | /24 | RIPENCC |
| 149.62.33.0/24 | /24 | RIPENCC |
| 176.61.160.0/21 | /24 | RIPENCC |
| 185.64.60.0/22 | /24 | RIPENCC |
| 188.213.232.0/24 | /24 | RIPENCC |
| 193.28.91.0/24 | /24 | RIPENCC |
| 193.28.229.0/24 | /24 | RIPENCC |
| 193.151.60.0/22 | /24 | RIPENCC |
| 194.103.64.0/20 | /24 | RIPENCC |
| 2a04:f680::/29 | /64 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS28760 | Infotech EDV-Systeme GmbH | Declared | Observed |
| AS39878 | Peter Rauter GmbH | Declared | Observed |
An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.
IRR
Registered route objects
Route objects naming AS50920 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 81.16.24.0/22 | RIPE | — | MNT-KAB-BRAUNAU | 2024-03-12 | Announced |
| 92.39.160.0/20 | RIPE | Kabel-Braunau-GmbH, Provider Local Registry Block | MNT-KAB-BRAUNAU | 2025-02-26 | Announced |
| 92.243.83.0/24 | RIPE | — | MNT-KAB-BRAUNAU | 2026-04-14 | Announced |
| 149.62.33.0/24 | RIPE | — | MNT-KAB-BRAUNAU | 2026-04-14 | Announced |
| 176.61.160.0/21 | RIPE | AT-Kabel-Braunau-Customer | MNT-KAB-BRAUNAU | 2025-10-21 | Announced |
| 185.64.60.0/22 | RIPE | AT-KBR-MUNDERFING-PON-Dynamic | MNT-KAB-BRAUNAU | 2026-04-14 | Announced |
| 188.213.232.0/24 | RIPE | — | MNT-KAB-BRAUNAU | 2026-04-14 | Announced |
| 193.28.91.0/24 | RIPE | Kabel-Braunau-GmbH, Provider Local Registry Block | MNT-KAB-BRAUNAU | 2026-04-14 | Announced |
| 193.28.229.0/24 | RIPE | Kabel-Braunau-GmbH, Provider Local Registry Block | MNT-KAB-BRAUNAU | 2014-09-02 | Announced |
| 193.151.60.0/22 | RIPE | Kabel-Braunau-GmbH, Customer-Subnet | MNT-KAB-BRAUNAU | 2026-04-14 | Announced |
| 194.103.64.0/20 | RIPE | — | MNT-KAB-BRAUNAU | 2025-03-04 | Announced |
| 2a04:f680::/29 | RIPE | — | MNT-KAB-BRAUNAU | 2025-02-06 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS50920 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-HURRICANEV6 | RADB | Lists AS50920 as a direct member |
AS-INFOTECH | RIPE | Lists AS50920 as a direct member |
AS-KABEL-BRAUNAU | RIPE | Lists AS50920 as a direct member |
AS-RAUTER | RIPE | Lists AS50920 as a direct member |
AS-WEISSBLAU-DE_SIM | RIPE | Lists AS50920 as a direct member |
AS50920:AS-KABELBRAUNAU | RIPE | Lists AS50920 as a direct member |
RPKI from rpki-client, validated 2026-10-14 18:17 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-14. Cross-check on bgp.he.net.