Network · data from 2026-11-12
AS26218 AS26218 - EMP. DE TEC. E INF. DA PREVIDENCIA - DATAPREV
Registry name: AS26218 - EMP. DE TEC. E INF. DA PREVIDENCIA - DATAPREV, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26218, 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.
| 200.152.32.0/22 | Valid | Nonecovered by 200.152.32.0/21 | 669 99% |
| 200.152.36.0/23 | Valid | Nonecovered by 200.152.32.0/21 | 669 99% |
| 2804:23c0::/40 | Valid | Nonecovered by 2804:23c0::/31 | 635 100% |
| 2804:23c0:2000::/40 | Valid | Nonecovered by 2804:23c0::/31 | 635 100% |
| 2804:23c0::/32 | Valid | Nonecovered by 2804:23c0::/31 | 632 99% |
| 2804:23c0:400::/40 | Valid | Nonecovered by 2804:23c0::/31 | 626 98% |
| 2804:23c0:2400::/40 | Valid | Nonecovered by 2804:23c0::/31 | 626 98% |
| 200.152.38.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 200.152.40.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 200.152.32.0/20 | Valid | Other IRR onlyRADB | 667 99% |
| 200.152.44.0/22 | Valid | Other IRR onlyRADB | 665 99% |
| 2804:23c0:200::/40 | Valid | Other IRR onlyRADB | 636 100% |
| 2804:23c0:2200::/40 | Valid | Other IRR onlyRADB | 636 100% |
AS-SET
AS26218 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 21 are in fix.csv.
- Route object: none7
- Route object: RIR6
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.152.32.0/22 | No route object for it. A route object for 200.152.32.0/21 with origin AS26218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26218 in the RIR database for the space. |
| Route object: none | 200.152.36.0/23 | No route object for it. A route object for 200.152.32.0/21 with origin AS26218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26218 in the RIR database for the space. |
| Route object: none | 2804:23c0::/40 | No route object for it. A route object for 2804:23c0::/31 with origin AS26218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26218 in the RIR database for the space. |
| Route object: none | 2804:23c0:2000::/40 | No route object for it. A route object for 2804:23c0::/31 with origin AS26218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26218 in the RIR database for the space. |
| Route object: none | 2804:23c0::/32 | No route object for it. A route object for 2804:23c0::/31 with origin AS26218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26218 in the RIR database for the space. |
| Route object: none | 2804:23c0:400::/40 | No route object for it. A route object for 2804:23c0::/31 with origin AS26218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26218 in the RIR database for the space. |
| Route object: none | 2804:23c0:2400::/40 | No route object for it. A route object for 2804:23c0::/31 with origin AS26218 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26218 in the RIR database for the space. |
| Route object: RIR | 200.152.38.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.152.40.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.152.32.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.152.44.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:23c0:200::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:23c0:2200::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26218 whose prefix no peer sees AS26218 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.152.32.0/21 | RADB | Valid |
| 200.152.38.0/24 | RADB | Valid |
| 200.152.39.0/24 | RADB | Valid |
| 200.152.40.0/24 | RADB | Valid |
| 200.152.41.0/24 | RADB | Valid |
| 200.152.42.0/24 | RADB | Valid |
| 200.152.43.0/24 | RADB | Valid |
| 2804:23c0::/31 | 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.