When the iXp UI is launched using the load-balanced URL, the session is initially established with one of the iXp servers (for example, the iXp PROD Primary). Subsequently, when users navigate to Instances/Site, the request may be routed based on load-balancer behaviour to either of the iXp servers. If the request is handled by the same iXp server, the site name remains unchanged. If it is served by the other iXp server, the site name reflects that server instead. While the site name is dynamically updated within the frame, the iXp UI title remains static and does not change accordingly.
This is expected behavior with iXP at this time.
Since both iXp servers operate in a high-availability, load-balanced configuration, this behavior has no functional impact unless the AutoSys-configured instances are not visible.