Network · data from 2026-11-12
AS26344 REALPAGE-INC - Real Page, Inc.
Registry name: REALPAGE-INC - Real Page, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26344, 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.
| 8.20.53.0/24 | No ROA | None | 673 100% |
| 8.39.132.0/24 | No ROA | None | 673 100% |
| 8.39.216.0/24 | No ROA | None | 673 100% |
| 8.40.212.0/23 | No ROA | None | 673 100% |
| 63.96.28.0/24 | No ROA | Nonecovered by 63.96.28.0/22 | 673 100% |
| 63.96.29.0/24 | No ROA | Nonecovered by 63.96.28.0/22 | 673 100% |
| 63.96.242.0/23 | No ROA | None | 673 100% |
| 71.154.19.0/24 | No ROA | None | 673 100% |
| 103.104.56.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 120.28.20.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 222.127.19.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS26344 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 19 are in fix.csv.
- ROA: none8
- Route object: none8
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 8.20.53.0/24 | No ROA covers it. Add a ROA for AS26344, maxLength 24. |
| Route object: none | 8.20.53.0/24 | No route object for it. Add a route object with origin AS26344 in the RIR database for the space. |
| ROA: none | 8.39.132.0/24 | No ROA covers it. Add a ROA for AS26344, maxLength 24. |
| Route object: none | 8.39.132.0/24 | No route object for it. Add a route object with origin AS26344 in the RIR database for the space. |
| ROA: none | 8.39.216.0/24 | No ROA covers it. Add a ROA for AS26344, maxLength 24. |
| Route object: none | 8.39.216.0/24 | No route object for it. Add a route object with origin AS26344 in the RIR database for the space. |
| ROA: none | 8.40.212.0/23 | No ROA covers it. Add a ROA for AS26344, maxLength 23. |
| Route object: none | 8.40.212.0/23 | No route object for it. Add a route object with origin AS26344 in the RIR database for the space. |
| ROA: none | 63.96.28.0/24 | No ROA covers it. Add a ROA for AS26344, maxLength 24. |
| Route object: none | 63.96.28.0/24 | No route object for it. A route object for 63.96.28.0/22 with origin AS26344 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26344 in the RIR database for the space. |
| ROA: none | 63.96.29.0/24 | No ROA covers it. Add a ROA for AS26344, maxLength 24. |
| Route object: none | 63.96.29.0/24 | No route object for it. A route object for 63.96.28.0/22 with origin AS26344 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26344 in the RIR database for the space. |
| ROA: none | 63.96.242.0/23 | No ROA covers it. Add a ROA for AS26344, maxLength 23. |
| Route object: none | 63.96.242.0/23 | No route object for it. Add a route object with origin AS26344 in the RIR database for the space. |
| ROA: none | 71.154.19.0/24 | No ROA covers it. Add a ROA for AS26344, maxLength 24. |
| Route object: none | 71.154.19.0/24 | No route object for it. Add a route object with origin AS26344 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26344 whose prefix no peer sees AS26344 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.96.28.0/22 | RADB | No ROA |
| 125.252.78.0/24 | NTTCOM | Valid |
| 209.37.196.0/23 | RADB | No ROA |
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.