Network · data from 2026-11-12
AS25893 WATTAGE-01 - Wattage Hosting, LLC
Registry name: WATTAGE-01 - Wattage Hosting, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25893, 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.
| 2602:fa49::/48 | Valid | Nonecovered by 2602:fa49::/36 | 636 100% |
| 2602:fa49:4::/48 | Valid | Nonecovered by 2602:fa49::/36 | 636 100% |
| 2602:fa49:5::/48 | Valid | Nonecovered by 2602:fa49::/36 | 635 100% |
| 50.117.21.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 50.118.153.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 50.118.176.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 50.118.191.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 23.159.68.0/24 | Valid | RIR databaseARIN | 673 100% |
| 23.230.220.0/24 | Valid | RIR databaseARIN | 673 100% |
| 50.117.70.0/24 | Valid | RIR databaseARIN | 673 100% |
| 50.117.71.0/24 | Valid | RIR databaseARIN | 673 100% |
| 50.117.76.0/24 | Valid | RIR databaseARIN | 673 100% |
| 50.117.77.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.164.115.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.164.130.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.164.214.0/24 | Valid | RIR databaseARIN | 673 100% |
| 104.252.35.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.252.227.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.252.231.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.252.236.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.252.239.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.252.241.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.253.17.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.253.38.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.253.51.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.253.67.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.252.16.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.252.24.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.252.29.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.252.32.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.252.35.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.252.36.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.252.37.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.252.38.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.252.39.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 192.177.185.0/24 | Valid | RIR databaseARIN | 673 100% |
| 192.177.188.0/24 | Valid | RIR databaseARIN | 673 100% |
| 192.177.189.0/24 | Valid | RIR databaseARIN | 673 100% |
| 45.38.38.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.38.53.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.38.141.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.38.203.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.38.224.0/24 | Valid | RIR databaseARIN | 672 100% |
| 45.39.109.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.39.173.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.39.176.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.39.211.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.39.217.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.39.218.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.39.243.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.39.249.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 2602:fa49::/36 | Valid | RIR databaseARIN | 636 100% |
AS-SET
AS25893 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 9 are in fix.csv.
- Route object: none3
- Route object: RIR4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2602:fa49::/48 | No route object for it. A route object for 2602:fa49::/36 with origin AS25893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25893 in the RIR database for the space. |
| Route object: none | 2602:fa49:4::/48 | No route object for it. A route object for 2602:fa49::/36 with origin AS25893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25893 in the RIR database for the space. |
| Route object: none | 2602:fa49:5::/48 | No route object for it. A route object for 2602:fa49::/36 with origin AS25893 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25893 in the RIR database for the space. |
| Route object: RIR | 50.117.21.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 50.118.153.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 50.118.176.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 50.118.191.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25893 whose prefix no peer sees AS25893 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 50.117.70.0/23 | ARIN, RADB | Valid |
| 50.117.76.0/23 | ARIN, RADB | 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.