Skip to content

[1.1.1.1] Dedicated page about sla and support #18346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 27, 2024
Merged

[1.1.1.1] Dedicated page about sla and support #18346

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4c908cf
Add new page for SLA and support
RebeccaTamachiro Nov 22, 2024
9933983
Add slug starting with 1.1.1.1 to frontmatter
RebeccaTamachiro Nov 22, 2024
aa1a3ad
Fix order within Infrastructure folder
RebeccaTamachiro Nov 22, 2024
ab0baaa
Add link to ToS and update intro paragraph as per PM review
RebeccaTamachiro Nov 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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

---


Expand Down
3 changes: 2 additions & 1 deletion src/content/docs/1.1.1.1/infrastructure/ipv6-networks.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Expand Down
3 changes: 2 additions & 1 deletion src/content/docs/1.1.1.1/infrastructure/network-operators.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Expand Down
16 changes: 16 additions & 0 deletions src/content/docs/1.1.1.1/infrastructure/sla-and-support.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.