Network · data from 2026-11-12
AS49576 REE-AS RED ELECTRICA DE ESPANA S.A.U.
Registry name: REE-AS RED ELECTRICA DE ESPANA S.A.U., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49576, 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.
| 193.148.111.0/24 | Valid | Nonecovered by 193.148.104.0/21 | 673 100% |
| 192.112.72.0/21 | Valid | None | 671 100% |
| 193.148.103.0/24 | Valid | Nonecovered by 193.148.96.0/21 | 670 100% |
| 193.148.124.0/24 | Valid | Nonecovered by 193.148.120.0/21 | 668 99% |
| 193.148.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.148.98.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.148.96.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 193.148.104.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 193.148.121.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.148.125.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.148.126.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.148.97.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.148.99.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.148.100.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.148.110.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.148.96.0/20 | Valid | RIR databaseRIPE | 670 100% |
| 192.112.76.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.148.119.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.148.102.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 193.148.120.0/21 | Valid | RIR databaseRIPE | 667 99% |
| 193.148.120.0/24 | Valid | RIR databaseRIPE | 667 99% |
AS-SET
AS49576 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 16 are in fix.csv.
- Route object: none4
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 193.148.111.0/24 | No route object for it. A route object for 193.148.104.0/21 with origin AS49576 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49576 in the RIR database for the space. |
| Route object: none | 192.112.72.0/21 | No route object for it. Add a route object with origin AS49576 in the RIR database for the space. |
| Route object: none | 193.148.103.0/24 | No route object for it. A route object for 193.148.96.0/21 with origin AS49576 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49576 in the RIR database for the space. |
| Route object: none | 193.148.124.0/24 | No route object for it. A route object for 193.148.120.0/21 with origin AS49576 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49576 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49576 whose prefix no peer sees AS49576 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.112.72.0/24 | RIPE | Invalid: maxLength |
| 192.112.73.0/24 | RIPE | Invalid: maxLength |
| 192.112.74.0/24 | RIPE | Invalid: maxLength |
| 192.112.75.0/24 | RIPE | Invalid: maxLength |
| 192.112.77.0/24 | RIPE | Invalid: maxLength |
| 192.112.78.0/24 | RIPE | Invalid: maxLength |
| 192.112.79.0/24 | RIPE | Invalid: maxLength |
| 193.148.112.0/20 | RIPE | Valid |
| 193.148.112.0/24 | RIPE | Valid |
| 193.148.113.0/24 | RIPE | Valid |
| 193.148.114.0/24 | RIPE | Valid |
| 193.148.116.0/24 | 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.