Network · data from 2026-11-12
AS553 BelWü
Registry name: BELWUE Universitaet Stuttgart, DE · PeeringDB
108IPv4 routes
88.9% RPKI valid · 88.9% with a route object
4IPv6 routes
100.0% RPKI valid · 100.0% with a route object
11RPKI invalid
11 origin · 0 maxLength
1No ROA
12 with no route object for this origin
12Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS553, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS553, 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.
| 45.82.144.26/32 | Invalid: origin | None | 1 0%low visibility |
| 89.58.56.77/32 | Invalid: origin | None | 1 0%low visibility |
| 110.52.202.232/32 | Invalid: origin | None | 1 0%low visibility |
| 114.37.208.129/32 | Invalid: origin | None | 1 0%low visibility |
| 192.54.49.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 192.54.60.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 192.55.188.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 192.108.23.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 192.108.24.0/23 | Invalid: origin | Other origin only | 1 0%low visibility |
| 192.108.26.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 195.178.110.155/32 | Invalid: origin | None | 1 0%low visibility |
| 192.54.41.0/24 | No ROA | Other origin only | 1 0%low visibility |
| 45.90.132.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 129.69.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 129.143.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 129.206.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 132.230.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 134.2.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 134.60.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 134.108.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 134.155.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 141.7.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 141.10.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 141.31.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 141.37.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 141.47.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 141.62.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 141.70.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 141.70.128.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 141.72.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 141.79.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 141.87.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 144.41.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 147.142.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 153.96.83.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 161.42.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 178.251.231.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.134.84.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 192.42.143.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.52.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 192.52.32.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 192.52.48.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 192.52.50.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.67.208.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.108.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.108.36.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 192.108.40.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 192.108.44.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.0.0/15 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.0.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.13.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.129.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.130.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.152.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.154.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.156.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.160.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.160.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.165.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.166.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.176.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 193.196.192.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.8.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.64.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.70.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.85.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.130.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.149.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.157.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.160.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.168.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 193.197.224.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 134.34.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 134.103.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 141.28.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 141.58.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 141.59.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 141.62.0.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 141.72.0.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 141.72.128.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 193.196.9.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.196.64.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 193.196.132.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.196.136.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 193.196.144.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 193.196.168.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.0.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.4.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.20.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.68.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.80.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.86.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.94.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.112.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.120.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.132.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.136.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.180.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.200.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 193.197.212.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 141.18.0.0/16 | Valid | RIR databaseRIPE | 671 100% |
| 141.19.0.0/16 | Valid | RIR databaseRIPE | 671 100% |
| 141.68.0.0/16 | Valid | RIR databaseRIPE | 671 100% |
| 141.69.0.0/16 | Valid | RIR databaseRIPE | 671 100% |
| 2001:7c0::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2001:7c0::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:ec00::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a0e:3c0::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS553: RIPE::AS-BELWUE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS553 isn't in the set, or no route object for AS553 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS553 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-BELWUE | RIPElists itself further down | 32 | 13 | Yes | 12 |
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 24 are in fix.csv.
- ROA: origin11
- ROA: none1
- Route object: none12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 45.82.144.26/32 | ROAs covering it name AS198401, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 45.82.144.26/32 | No route object for it. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: origin | 89.58.56.77/32 | ROAs covering it name AS197540, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 89.58.56.77/32 | No route object for it. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: origin | 110.52.202.232/32 | ROAs covering it name AS4837, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 110.52.202.232/32 | No route object for it. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: origin | 114.37.208.129/32 | ROAs covering it name AS3462, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 114.37.208.129/32 | No route object for it. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: origin | 192.54.49.0/24 | ROAs covering it name AS680, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 192.54.49.0/24 | Route objects for it name AS680. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: origin | 192.54.60.0/24 | ROAs covering it name AS680, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 192.54.60.0/24 | Route objects for it name AS680. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: origin | 192.55.188.0/24 | ROAs covering it name AS680, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 192.55.188.0/24 | Route objects for it name AS680. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: origin | 192.108.23.0/24 | ROAs covering it name AS680, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 192.108.23.0/24 | Route objects for it name AS680. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: origin | 192.108.24.0/23 | ROAs covering it name AS680, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 192.108.24.0/23 | Route objects for it name AS680. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: origin | 192.108.26.0/24 | ROAs covering it name AS680, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 192.108.26.0/24 | Route objects for it name AS680. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: origin | 195.178.110.155/32 | ROAs covering it name AS48090, not AS553. If AS553 should announce it, add a ROA for AS553. |
| Route object: none | 195.178.110.155/32 | No route object for it. Add a route object with origin AS553 in the RIR database for the space. |
| ROA: none | 192.54.41.0/24 | No ROA covers it. Add a ROA for AS553, maxLength 24. |
| Route object: none | 192.54.41.0/24 | Route objects for it name AS680. Add a route object with origin AS553 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS553 is announced.
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.