Secure Infrastructure Access (SIA) RDP-Protocol for On-Prem Connection Issue

Recovering
Recovering

We've fixed the core issue, and are waiting for things to recover.

Identified

Our engineering team has identified the root cause. The issue is limited to the following two specific scenarios in SIA-RDP only:

  1. Numeric FQDN components - A user attempts to connect to a machine using a Fully Qualified Domain Name (FQDN) where the subdomain םר the domain contain numeric characters.
  2. IP-only connection with a conflicting cloud-discovered target - A user attempts to connect using an IP address only (without a network name), while a machine that was discovered and onboarded to SIA via Connect cloud environments (through a cloud provider integration) resolves to the same IP address.

Other connection scenarios are unaffected.

Our team is actively working on a fix. We will provide a further update within 90 minutes, or sooner if new information becomes available.

Investigating

We are currently investigating an issue affecting SIA connections for the RDP protocol in a specific use case that is still being investigated. Our engineering team is actively working to restore full functionality.

Impact: Users may be unable to connect to targets in certain specific use cases through SIA using the RDP protocol. All other protocols continue to operate normally.

Next update: In 90 minutes, or sooner if new information becomes available.

Began at:

Affected components
    • US East (N. Virginia)
    • Canada (Central)
    • Brazil (Sao Paulo)
    • Europe (Frankfurt)
    • Europe (London)
    • Europe (Milan)
    • Middle East (UAE)
    • Israel (Tel Aviv)
    • Asia Pacific (Tokyo)
    • Asia Pacific (Mumbai)
    • Asia Pacific (Sydney)
    • Asia Pacific (Singapore)
    • FedRAMP | Government