diff --git a/src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx b/src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx
index 6de418bb4d8b615..b63686d0173e319 100644
--- a/src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx
+++ b/src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx
@@ -1,8 +1,9 @@
 ---
 pcx_content_type: reference
 title: Extended DNS error codes
+sidebar:
+  order: 4
 slug: 1.1.1.1/infrastructure/extended-dns-error-codes
-
 ---
 
 
diff --git a/src/content/docs/1.1.1.1/infrastructure/ipv6-networks.mdx b/src/content/docs/1.1.1.1/infrastructure/ipv6-networks.mdx
index 09ddd443d6173cf..1213a091789bf01 100644
--- a/src/content/docs/1.1.1.1/infrastructure/ipv6-networks.mdx
+++ b/src/content/docs/1.1.1.1/infrastructure/ipv6-networks.mdx
@@ -1,8 +1,9 @@
 ---
 pcx_content_type: reference
 title: Support for IPv6-only networks
+sidebar:
+  order: 3
 slug: 1.1.1.1/infrastructure/ipv6-networks
-
 ---
 
 While network infrastructure is shifting towards IPv6-only networks, providers still need to support IPv4 addresses. Dual-stack networks are networks in which all nodes have both IPv4 and IPv6 connectivity capabilities, and can therefore understand both IPv4 and IPv6 packets.
diff --git a/src/content/docs/1.1.1.1/infrastructure/network-operators.mdx b/src/content/docs/1.1.1.1/infrastructure/network-operators.mdx
index 53ae91d8beef608..bfa146c3ba23312 100644
--- a/src/content/docs/1.1.1.1/infrastructure/network-operators.mdx
+++ b/src/content/docs/1.1.1.1/infrastructure/network-operators.mdx
@@ -1,8 +1,9 @@
 ---
 pcx_content_type: reference
 title: Network operators
+sidebar:
+  order: 1
 slug: 1.1.1.1/infrastructure/network-operators
-
 ---
 
 Network operators, including Internet Service Providers (ISPs), device manufacturers, public Wi-Fi networks, municipal broadband providers, and security scanning services can use [1.1.1.1](/1.1.1.1/setup/) in place of operating their own recursive DNS infrastructure.
diff --git a/src/content/docs/1.1.1.1/infrastructure/sla-and-support.mdx b/src/content/docs/1.1.1.1/infrastructure/sla-and-support.mdx
new file mode 100644
index 000000000000000..cf4d92f4b2a92e1
--- /dev/null
+++ b/src/content/docs/1.1.1.1/infrastructure/sla-and-support.mdx
@@ -0,0 +1,16 @@
+---
+pcx_content_type: reference
+title: SLA and technical support
+sidebar:
+  label: SLA and support
+  order: 5
+slug: 1.1.1.1/infrastructure/sla-and-support
+---
+
+As you use 1.1.1.1 in your infrastructure or service, note that dedicated technical support is limited.
+
+You are subject to the [Cloudflare Website and Online Services Terms of Use](https://www.cloudflare.com/website-terms/) and no service level agreements (SLAs) are provided.
+
+If you need SLAs and dedicated support, consider using [Cloudflare Gateway](/cloudflare-one/policies/gateway/) instead.
+
+Gateway includes other advanced options such as domain categories, customized filtering, and scheduling capabilities. For example, if you are a device manufacturer or network operator, you can use a multi-tenant environment to allow your customers to configure their own individual filters.
\ No newline at end of file