You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/byoip/get-started-review.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,6 @@ Overall, the steps can be summarized as follows:
32
32
2. You prepare a [letter of agency (LOA)](/byoip/concepts/loa/) containing both the prefixes you are authorizing Cloudflare to announce and which ASN they will be announced under. Cloudflare will present this to our transit partners as evidence that we are allowed to announce the route.
33
33
3. After receiving the LOA, Cloudflare validates the [requirements](#requirements).
34
34
4. Cloudflare provisions the IPs.
35
-
5.Once the IPs are provisioned, you use [service bindings](/byoip/service-bindings/)and [address maps](/byoip/address-maps/) to control how your IPs are used.
36
-
6.(Optional) You can use [Prefix delegations](/byoip/concepts/prefix-delegations/)to share all or part of your prefix with another Cloudflare account.
35
+
5.(Optional) You can use [Prefix delegations](/byoip/concepts/prefix-delegations/)to share all or part of your prefix with another Cloudflare account.
36
+
6. You use [service bindings](/byoip/service-bindings/)and [address maps](/byoip/address-maps/) to control how your IPs are used.
37
37
7. Finally, you configure the [Border Gateway Protocol advertisement](/byoip/concepts/dynamic-advertisement/) for your IPs at the Cloudflare network.
0 commit comments