Network · data from 2026-11-12
AS46973 REALOGY-WEBSERVICES - Realogy Group LLC
Registry name: REALOGY-WEBSERVICES - Realogy Group LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46973, 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.9.0/24 | Valid | None | 673 100% |
| 167.182.8.0/24 | Valid | None | 672 100% |
| 167.182.60.0/24 | Valid | None | 672 100% |
| 167.182.61.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 167.182.57.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
AS46973 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 7 are in fix.csv.
- Route object: none3
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 167.182.9.0/24 | No route object for it. Add a route object with origin AS46973 in the RIR database for the space. |
| Route object: none | 167.182.8.0/24 | No route object for it. Add a route object with origin AS46973 in the RIR database for the space. |
| Route object: none | 167.182.60.0/24 | No route object for it. Add a route object with origin AS46973 in the RIR database for the space. |
| Route object: RIR | 167.182.61.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.182.57.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46973 whose prefix no peer sees AS46973 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 167.182.10.0/24 | RADB | No ROA |
| 167.182.62.0/24 | 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.