Network · data from 2026-11-12
AS54053 REALOGY-DDC - Realogy Group LLC
Registry name: REALOGY-DDC - Realogy Group LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54053, 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.
| 167.182.1.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 167.182.2.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 167.182.3.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 167.182.6.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 167.182.7.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 167.182.67.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 167.182.71.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 167.182.73.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 167.182.75.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 167.182.80.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 167.182.85.0/24 | Valid | Nonecovered by 167.182.0.0/17 | 673 100% |
| 198.151.39.0/24 | Valid | Nonecovered by 198.151.38.0/23 | 673 100% |
| 167.182.59.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 167.182.74.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 167.182.76.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 167.182.77.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 167.182.82.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 198.151.42.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 198.175.44.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS54053 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: none12
- Route object: RIR7
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 167.182.1.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 167.182.2.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 167.182.3.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 167.182.6.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 167.182.7.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 167.182.67.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 167.182.71.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 167.182.73.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 167.182.75.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 167.182.80.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 167.182.85.0/24 | No route object for it. A route object for 167.182.0.0/17 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: none | 198.151.39.0/24 | No route object for it. A route object for 198.151.38.0/23 with origin AS54053 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54053 in the RIR database for the space. |
| Route object: RIR | 167.182.59.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.182.74.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.182.76.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.182.77.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.182.82.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.151.42.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.175.44.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54053 whose prefix no peer sees AS54053 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 167.182.0.0/17 | RADB | No ROA |
| 198.151.38.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.