Platform: All Regions - Unable to launch PRA session when using hostname

Incident overview 

On January 09, 2026, A subset of Platform customers were unable to launch new PRA sessions when the target machine hostname used a single-label format (e.g., webserver1).

Sessions with machine names using FQDN (webserver1.example.com) and IP address as formats, functioned as expected.  

• Impact Start Time: January 9, 2026, 1:00 AM UTC 

• Impact End Time: January 9, 2026, 3:35 AM UTC 

Root Cause 

On January 9, 2026, at 12:00 AM UTC, a new version of the PRA service was deployed. This release introduced a regression in the hostname validation logic, causing single‑label hostnames (e.g., webserver1) to be incorrectly flagged as invalid and preventing session launches for customers using this format. 

After correlating the deployment with the customer reports, we initiated an immediate rollback to the previous stable version. Post‑rollback validation, including a review of backend traces and logs, confirmed that the issue was fully resolved and that affected customers were once again able to launch sessions using single‑label hostnames. 

Prevention and Follow-up Actions

• Review deployment process to identify why this regression was not caught in pre-production testing.

• Expand test automation coverage to include single-label hostname validation scenarios.

• Enhance observability by adding telemetry and alerts for hostname‑related validation failures.