bgpreport

Network · data from 2026-11-12

AS20825 UNITYMEDIA Vodafone West GmbH

Registry name: UNITYMEDIA Vodafone West GmbH, DE · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 0.0% with a route object
7IPv6 routes 0.0% RPKI valid · 0.0% with a route object
9RPKI invalid 9 origin · 0 maxLength
0No ROA 9 with no route object for this origin
9Low visibility seen by under 10% of full-table peers
61Route objects not announced registered with origin AS20825, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20825, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

62.143.108.0/24 Invalid: origin Nonecovered by 62.143.0.0/17 2 0%low visibility 2
78.43.224.0/23 Invalid: origin None 2 0%low visibility 2
2a02:908:2b0::/44 Invalid: origin Nonecovered by 2a02:908::/33 2 0%low visibility 2
2a02:8071:5320::/44 Invalid: origin None 2 0%low visibility 2
2a02:8071:5820::/44 Invalid: origin None 2 0%low visibility 2
2a02:8071:5830::/44 Invalid: origin None 2 0%low visibility 2
2a02:8071:7350::/44 Invalid: origin None 2 0%low visibility 2
2a02:8071:7480::/44 Invalid: origin None 2 0%low visibility 2
2a02:8071:7a80::/44 Invalid: origin None 2 0%low visibility 2

AS-SET

AS20825 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 79 are in fix.csv.

  • ROA: origin9
  • Route object: none9
  • Route object: not announced61
ChangePrefix or setDetailFull-table peers
ROA: origin62.143.108.0/24ROAs covering it name AS3209, not AS20825. If AS20825 should announce it, add a ROA for AS20825.2 of 673
Route object: none62.143.108.0/24No route object for it. A route object for 62.143.0.0/17 with origin AS20825 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20825 in the RIR database for the space.2 of 673
ROA: origin78.43.224.0/23ROAs covering it name AS3209, not AS20825. If AS20825 should announce it, add a ROA for AS20825.2 of 673
Route object: none78.43.224.0/23No route object for it. Add a route object with origin AS20825 in the RIR database for the space.2 of 673
ROA: origin2a02:908:2b0::/44ROAs covering it name AS3209, not AS20825. If AS20825 should announce it, add a ROA for AS20825.2 of 636
Route object: none2a02:908:2b0::/44No route object for it. A route object for 2a02:908::/33 with origin AS20825 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20825 in the RIR database for the space.2 of 636
ROA: origin2a02:8071:5320::/44ROAs covering it name AS3209, not AS20825. If AS20825 should announce it, add a ROA for AS20825.2 of 636
Route object: none2a02:8071:5320::/44No route object for it. Add a route object with origin AS20825 in the RIR database for the space.2 of 636
ROA: origin2a02:8071:5820::/44ROAs covering it name AS3209, not AS20825. If AS20825 should announce it, add a ROA for AS20825.2 of 636
Route object: none2a02:8071:5820::/44No route object for it. Add a route object with origin AS20825 in the RIR database for the space.2 of 636
ROA: origin2a02:8071:5830::/44ROAs covering it name AS3209, not AS20825. If AS20825 should announce it, add a ROA for AS20825.2 of 636
Route object: none2a02:8071:5830::/44No route object for it. Add a route object with origin AS20825 in the RIR database for the space.2 of 636
ROA: origin2a02:8071:7350::/44ROAs covering it name AS3209, not AS20825. If AS20825 should announce it, add a ROA for AS20825.2 of 636
Route object: none2a02:8071:7350::/44No route object for it. Add a route object with origin AS20825 in the RIR database for the space.2 of 636
ROA: origin2a02:8071:7480::/44ROAs covering it name AS3209, not AS20825. If AS20825 should announce it, add a ROA for AS20825.2 of 636
Route object: none2a02:8071:7480::/44No route object for it. Add a route object with origin AS20825 in the RIR database for the space.2 of 636
ROA: origin2a02:8071:7a80::/44ROAs covering it name AS3209, not AS20825. If AS20825 should announce it, add a ROA for AS20825.2 of 636
Route object: none2a02:8071:7a80::/44No route object for it. Add a route object with origin AS20825 in the RIR database for the space.2 of 636

Route objects not announced

Route objects with origin AS20825 whose prefix no peer sees AS20825 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.10.160.0/19RIPEInvalid: origin
5.10.160.0/20RIPEInvalid: origin
5.10.176.0/20RIPEInvalid: origin
5.146.0.0/15RIPEInvalid: origin
5.146.0.0/16RIPEInvalid: origin
5.147.0.0/16RIPEInvalid: origin
37.24.0.0/16RIPEInvalid: origin
37.24.0.0/17RIPEInvalid: origin
37.24.128.0/17RIPEInvalid: origin
37.201.0.0/16RIPEInvalid: origin
37.201.0.0/17RIPEInvalid: origin
37.201.128.0/17RIPEInvalid: origin
46.252.128.0/20RIPEInvalid: origin
46.252.128.0/21RIPEInvalid: origin
46.252.136.0/21RIPEInvalid: origin
62.143.0.0/16RIPEInvalid: origin
62.143.0.0/17RIPEInvalid: origin
62.143.128.0/17RIPEInvalid: origin
78.94.0.0/16RIPEInvalid: origin
78.94.0.0/17RIPEInvalid: origin
78.94.128.0/17RIPEInvalid: origin
80.69.96.0/20RIPEInvalid: origin
80.69.96.0/21RIPEInvalid: origin
80.69.104.0/21RIPEInvalid: origin
81.210.128.0/17RIPEInvalid: origin
81.210.128.0/18RIPEInvalid: origin
81.210.192.0/18RIPEInvalid: origin
84.118.0.0/15RIPEInvalid: origin
84.118.0.0/16RIPEInvalid: origin
84.119.0.0/16RIPEInvalid: origin
88.152.0.0/15RIPEInvalid: origin
88.152.0.0/16RIPEInvalid: origin
88.153.0.0/16RIPEInvalid: origin
92.50.64.0/18RIPEInvalid: origin
92.50.64.0/19RIPEInvalid: origin
92.50.96.0/19RIPEInvalid: origin
94.79.128.0/18RIPEInvalid: origin
94.79.128.0/19RIPEInvalid: origin
94.79.160.0/19RIPEInvalid: origin
94.114.0.0/16RIPEInvalid: origin
95.222.0.0/15RIPEInvalid: origin
95.222.0.0/16RIPEInvalid: origin
95.223.0.0/16RIPEInvalid: origin
109.90.0.0/15RIPEInvalid: origin
109.90.0.0/16RIPEInvalid: origin
109.91.0.0/16RIPEInvalid: origin
130.180.0.0/17RIPEInvalid: origin
130.180.0.0/18RIPEInvalid: origin
130.180.64.0/18RIPEInvalid: origin
176.198.0.0/15RIPEInvalid: origin
176.198.0.0/16RIPEInvalid: origin
176.199.0.0/16RIPEInvalid: origin
178.200.0.0/14RIPEInvalid: origin
178.200.0.0/15RIPEInvalid: origin
178.202.0.0/15RIPEInvalid: origin
192.109.89.0/24RIPENo ROA
192.109.211.0/24RIPEValid
192.109.212.0/24RIPEValid
2a02:908::/32RIPEInvalid: origin
2a02:908::/33RIPEInvalid: origin
2a02:908:8000::/33RIPEInvalid: origin

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.