Correct the format of Regional Endpoints in the list of Regions

[lukeknep]

What does this PR do?

• We have two types of endpoints.
• A long time ago, we moved Regional Endpoints to a new format ending in api.temporal.io, which is already reflected in our UI / API / CLI.
• Some docs pages were left on the old format (ending in tmprl.cloud), including the list of Regions & their regional endpoints. While these still "work" today, they are subject to change without notice and should not be used in Users' code.
• This PR fixes the outdated format of all instances of ...region.tmprl.cloud in the docs.

Notes to Reviewers

• I have validated programmatically that every single Regional Endpoint listed actually connects successfully.
• I have searched and removed all instances of the old format, except under the AWS PrivateLink for High Availability section (which was not actually talking about a Regional Endpoint, but did happen to use the old format). This will need an additional PR along with some internal alignment on Product direction.

┆Attachments: EDU-6342 Correct the format of Regional Endpoints in the list of Regions

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
temporal-documentation	Error		May 17, 2026 6:03pm

[github-actions]

📖 Docs PR preview links

• Cloud
  • Connectivity
    • AWS Private Connect
    • GCP Private Connect
    • IP addresses
  • High Availability
    • Connectivity for High Availability
  • References
    • Regions
      • Awsregions
      • Gcpregions

[daniel-goldstein]

Looks mostly good but I don't think we can actually change the HA sections since we still use the old endpoint in CNAMEs

[lukeknep]

Ok @daniel-goldstein I've resolved all of the issues you pointed out, great catches!

For HA Namespaces, we have GA'd the automatic failover of Namespace Endpoints via DNS + GA'd PrivateLink where we told the customer to take a dependency on this behavior. This is the only place where they can take a dependency on DNS resolution, so I've added this to the docs: