Updates stale information

src/docs/guides/public-networking.md

@@ -89,7 +89,7 @@ Note that changes to DNS settings may take up to 72 hours to propagate worldwide
 - Freenom domains are not allowed and not supported.
 - The Trial Plan is limited to 1 custom domain. It is therefore not possible to use both `yourdomain.com` and `www.yourdomain.com` as these are considered two distinct custom domains.
 - The [Hobby Plan](/reference/pricing#plans) is limited to 2 custom domains per service.
-- The [Pro Plan]() is limited to 10 domains per service by default.  This limit can be increased for Pro users on request, simply reach out to us via a [private thread](/reference/support#private-threads).
+- The [Pro Plan]() is limited to 20 domains per service by default.  This limit can be increased for Pro users on request, simply reach out to us via a [private thread](/reference/support#private-threads).
 
 ## Wildcard Domains
 

src/docs/reference/deployments.md

@@ -129,6 +129,12 @@ If your service requires data to persist between deployments, or needs more than
 
 By default, Railway maintains only one deploy per service.
 
+In practice, this means that if you trigger a new deploy either [manually](/guides/deployment-actions#redeploy) or [automatically](/guides/github-autodeploys), the old version will be stopped and removed with a slight overlap for zero downtime.
+
+Once the new deployment is online, the old deployment is sent a SIGTERM signal and given 3 seconds to gracefully shutdown before being forcefully stopped with a SIGKILL. We do not send any other signals under any circumstances.
+
+The time given to gracefully shutdown can be controlled by setting a [`RAILWAY_DEPLOYMENT_OVERLAP_SECONDS`](/reference/variables#user-provided-configuration-variables) [service variable](/overview/the-basics#service-variables).
+
 ## Support
 
 For information on how to manage your deployments, explore [the guides in this section](/guides/deployments).

src/docs/reference/public-networking.md

@@ -19,7 +19,7 @@ If you have your own Domain already, Railway also supports adding custom domains
 | **DNS/Domain Names** | - Support for domains, subdomains, and wildcard domains.<br/>- Subdomains and wildcards cannot overlap (`foo.hello.com` cannot exist with `*.hello.com` unless owned by the same service).<br/>- Root domains need a DNS provider with ALIAS records or CNAME flattening.<br/>- Unicode domains should be PUNYcode encoded.<br/>- Non-public/internal domain names are not supported. |
 | **Certificate Issuance** | - Railway attempts to issue a certificate for **up to 72 hours** after domain creation before failing.<br/>- Certificates are expected to be issued within an hour. |
 | **TLS** | - Support for TLS 1.2 and TLS 1.3 with specific ciphersets.<br/>- Certificates are valid for 90 days and renewed every 30 days.<br/>- Cloudflare Proxying does impact certificate issuance and support for wildcard domains. |
-| **Edge Traffic** | - Support for HTTP/1.1 and HTTP/2.<br/>- Support for websockets over HTTP/1.1 (may be interrupted after 2-4hrs, clients should handle reconnect).<br/>- Idle timeout of 900 seconds.<br/>- Max 100 request headers.<br /> - Max 100 concurrent streams per HTTP2 connection.<br/>- Max duration of 5 minutes for HTTP requests. |
+| **Edge Traffic** | - Support for HTTP/1.1 and HTTP/2.<br/>- Support for websockets over HTTP/1.1.<br/>- Idle timeout of 900 seconds.<br/>- Max 100 request headers.<br /> - Max 16 KB Combined Header Size<br />- Max 100 concurrent streams per HTTP2 connection.<br/>- Max duration of 5 minutes for HTTP requests. |
 | **Request Headers** | - `X-Real-IP` for identifying client's remote IP.<br/>- `X-Forwarded-Proto` always indicates `https`.<br/>- `X-Railway-Request-Id` for correlating requests against network logs. |
 | **Requests** | - Inbound traffic must be TLS-encrypted<br/>- HTTP GET requests to port 80 are redirected to HTTPS.<br/>- HTTP POST requests to port 80 are redirected to HTTPS as GET requests.<br/>- SNI is required for correct certificate matching. |
 
@@ -39,7 +39,7 @@ If your application requires higher limits, please don't hesitate to reach out t
 
 The [Hobby plan](/reference/pricing#plans) is limited to 2 custom domains per service.
 
-The [Pro Plan](/reference/pricing#plans) is limited to 10 domains per service by default but can be increased for Pro users on request, by reaching out to us at [[email protected]](mailto:[email protected]) or via [private thread](/reference/support#private-threads).
+The [Pro Plan](/reference/pricing#plans) is limited to 20 domains per service by default but can be increased for Pro users on request, by reaching out to us at [[email protected]](mailto:[email protected]) or via [private thread](/reference/support#private-threads).
 
 ## FAQ
 

src/docs/reference/regions.md

@@ -16,6 +16,7 @@ Within the service settings, you can select one of the following regions:
 | US West              | Oregon, USA            | `us-west1`        |
 | US West (Metal Beta) | California, USA        | `us-west2`        |
 | US East              | Virginia, USA          | `us-east4`        |
+| US East (Metal Beta) | Virginia, USA          | `us-east4-eqdc4a` |
 | EU West              | Amsterdam, Netherlands | `europe-west4`    |
 | Southeast Asia       | Singapore              | `asia-southeast1` |
 
@@ -27,34 +28,31 @@ Within the service settings, you can select one of the following regions:
     alt="Volume"
 />
 
+**Notes:**
 
-*Additional regions may be added in the future as Railway continues expanding its infrastructure footprint.*
+- Additional regions may be added in the future as Railway continues expanding its infrastructure footprint.
 
-By default, Railway deploys to `us-west1` located in Portland, Oregon.
+- Metal regions do not support services with volumes attached to them.
 
-All regions provide the same experience, performance, and reliability you expect from Railway.
+- Metal regions are available to all users as opposed to the other regions which are limited to Pro plan users.
 
-## Impact of Region Changes
+- By default, Railway deploys to `us-west1` located in Portland, Oregon.
 
-The region of a service can be changed at any time, without any changes to your domain, private networking, etc.
+- All regions provide the same experience, performance, and reliability you expect from Railway.
 
-There will be no downtime when changing the region of a service, except if it has a volume attached to it (see next section).
+- Impact of Region Changes
 
-### Volumes
+- The region of a service can be changed at any time, without any changes to your domain, private networking, etc.
 
-Volumes are following the region of the service they are attached to. This means if you attach a new volume to a service, it will be deployed in the same region as the service.
+- There will be no downtime when changing the region of a service, except if it has a volume attached to it (see next section).
 
-If you change the region of a service with an existing attached volume, you will get warned about the volume needing to be migrated to the new region.
+### Volumes
 
-<Image
-    quality={100}
-    src="https://res.cloudinary.com/railway/image/upload/v1695660986/docs/volume_migrate_modal.png"
-    alt="Volume"
-    width={669}
-    height={678}
-/>
+Volumes follow the region of the service they are attached to. This means if you attach a new volume to a service, it will be deployed in the same region as the service.
+
+If you change the region of a service with an existing attached volume, that volume will need to be migrated to the new region. You will experience minimal downtime, even for volumes containing large amounts of data.
 
-Note that this migration can take a while depending on the size of the volume, and will cause downtime of your service during that time.
+The same is true if you attach a detached volume to a service in a different region. It will need to be migrated to the new region.
 
 <Image
     quality={100}
@@ -64,9 +62,6 @@ Note that this migration can take a while depending on the size of the volume, a
     height={483}
 />
 
-
-The same is true if you attach a detached volume to a service in a different region. It will need to be migrated to the new region, which can take a while and cause downtime.
-
 ## Support
 
 For information on how to deploy your services to different regions, refer to [this guide](/guides/optimize-performance#configure-a-region).