Network · data from 2026-11-12
AS49808 Energie AG Oberösterreich Services und Digital Solutions GmbH
Registry name: POWERSPEED-AS Energie AG Oberoesterreich Services und Digital Solutions GmbH, AT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49808, 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.
| 109.68.104.18/32 | Invalid: maxLength | Nonecovered by 109.68.104.0/21 | 2 0%low visibility |
| 91.233.7.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.233.12.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.75.8.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.148.236.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 193.27.244.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 193.228.232.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.228.233.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a05:4e40::/32 | No ROA | RIR databaseRIPE | 633 100% |
| 5.159.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 31.193.160.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 45.150.96.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 63.247.208.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 85.118.184.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 85.193.160.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 86.109.24.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.249.184.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 91.213.6.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.119.92.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 109.68.104.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 139.178.96.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 145.40.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 162.211.104.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 162.213.162.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.11.84.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.16.112.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.21.98.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.44.210.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.41.207.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.107.144.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.78.46.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 198.89.232.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 2a03:c100::/32 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS49808: AS-POWERSPEED. 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 (AS49808 isn't in the set, or no route object for AS49808 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 | AS49808 in it | Not covered |
|---|---|---|---|---|---|
| AS-POWERSPEED | RIPE | 37 | 8 | Yes | 1 |
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 19 are in fix.csv.
- ROA: maxLength1
- ROA: none8
- Route object: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 109.68.104.18/32 | ROA 109.68.104.0/21 AS49808 has maxLength 21; the route is a /32. Raise the maxLength, or add a ROA for 109.68.104.18/32. |
| Route object: none | 109.68.104.18/32 | No route object for it. A route object for 109.68.104.0/21 with origin AS49808 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49808 in the RIR database for the space. |
| ROA: none | 91.233.7.0/24 | No ROA covers it. Add a ROA for AS49808, maxLength 24. |
| ROA: none | 91.233.12.0/23 | No ROA covers it. Add a ROA for AS49808, maxLength 23. |
| ROA: none | 185.75.8.0/24 | No ROA covers it. Add a ROA for AS49808, maxLength 24. |
| ROA: none | 185.148.236.0/22 | No ROA covers it. Add a ROA for AS49808, maxLength 22. |
| ROA: none | 193.27.244.0/23 | No ROA covers it. Add a ROA for AS49808, maxLength 23. |
| ROA: none | 193.228.232.0/24 | No ROA covers it. Add a ROA for AS49808, maxLength 24. |
| ROA: none | 193.228.233.0/24 | No ROA covers it. Add a ROA for AS49808, maxLength 24. |
| ROA: none | 2a05:4e40::/32 | No ROA covers it. Add a ROA for AS49808, maxLength 32. |
Route objects not announced
Route objects with origin AS49808 whose prefix no peer sees AS49808 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.159.4.0/22 | RIPE | Valid |
| 91.196.20.0/22 | RIPE | No ROA |
| 162.213.160.0/22 | RIPE | Valid |
| 162.213.160.0/23 | RIPE | Valid |
| 162.213.160.0/24 | RIPE | Valid |
| 162.213.161.0/24 | RIPE | Valid |
| 162.213.162.0/24 | RIPE | Valid |
| 162.213.163.0/24 | RIPE | Valid |
| 185.21.96.0/23 | RIPE | Valid |
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.