Skip to content

Commit 6f07dd0

Browse files
authored
Merge branch 'cloudflare:production' into design-guide-streamlined-waf-deployment-across-zones-apps
2 parents c7e3812 + 28308f0 commit 6f07dd0

File tree

3 files changed

+13
-14
lines changed

3 files changed

+13
-14
lines changed

src/content/docs/hyperdrive/get-started.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ To connect to your database, you will need a database driver which allows you to
175175

176176
To install `postgres`, ensure you are in the `hyperdrive-tutorial` directory. Open your terminal and run the following command:
177177

178-
<PackageManagers pkg="postgres" comment="This should install v3.4.4 or later" />
178+
<PackageManagers pkg="postgres" comment="This should install v3.4.5 or later" />
179179

180180
With the driver installed, you can now create a Worker script that queries your database.
181181

@@ -190,7 +190,7 @@ The `index.ts` file is where you configure your Worker's interactions with Hyper
190190
Populate your `index.ts` file with the following code:
191191

192192
```typescript
193-
// Postgres.js 3.4.4 or later is recommended
193+
// Postgres.js 3.4.5 or later is recommended
194194
import postgres from "postgres";
195195

196196
export interface Env {

src/content/docs/magic-transit/get-started.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ The LOA must be a PDF. Transit providers may reject the LOA if it is a JPG or PN
4343

4444
### Verify IRR entries
4545

46-
Verify your Internet Routing Registry (IRR) entries match corresponding origin autonomous system numbers (ASNs) to ensure Magic Transit routes traffic to the correct autonomous systems (AS). For guidance, refer to [Verify IRR entries](/byoip/concepts/irr-entries/best-practices/#verify-an-irr-entry).
46+
Verify that your Internet Routing Registry (IRR) entries match your corresponding origin autonomous system numbers (ASNs) to ensure Magic Transit routes traffic to the correct autonomous systems (AS). For guidance, refer to [Verify IRR entries](/byoip/concepts/irr-entries/best-practices/#verify-an-irr-entry).
4747

4848
If you are using a Cloudflare IP, you do not need to verify your IRR entries.
4949

src/content/docs/magic-transit/how-to/advertise-prefixes.mdx

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -39,14 +39,17 @@ If you do not have an ASN or do not want to bring your ASN to Cloudflare, you ca
3939
Current customers who are still using Cloudflare's AS209242 can continue using this same ASN. No further change is required.
4040
:::
4141

42-
## Add an IP prefix
42+
## Advertise your prefix
43+
44+
:::note
45+
You can only advertise your prefix [after running pre-flight checks](/magic-transit/get-started/#5-run-pre-flight-checks) with Cloudflare. If your prefix status is greyed out and shows an _Withdrawn_ status, your prefix is locked. Contact your account team to close the pre-flight checks phase with you and unlock your prefixes.
46+
:::
4347

4448
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
4549
2. Go to **Magic Transit** > **Configuration**.
46-
3. From the **IP Prefixes** tab, select **Create**.
47-
4. Fill out the information for your prefix and select **Add IP Prefix**.
48-
49-
After you add the prefix, you can edit its status.
50+
3. From the **IP Prefixes** tab select your prefix > **Edit**.
51+
4. Under **Status**, select _Advertise_ to advertise your prefix.
52+
5. Select **Edit Prefix** to save your changes.
5053

5154
## Edit the status of a prefix
5255

@@ -55,9 +58,9 @@ After you add the prefix, you can edit its status.
5558
3. _(Optional)_ Edit the description for your prefix.
5659
4. Select **Edit IP Prefix** to save your changes.
5760

58-
:::note[Note:]
5961
To avoid latency and potentially dropped routes, enable prefix advertisement from Cloudflare before withdrawing the advertisement from your data center.
60-
:::
62+
63+
You should also be aware that announcing or withdrawing a prefix should propagate across Cloudflare's global network almost instantly, with changes typically taking effect within a few minutes at most. However, Cloudflare has no control over how long ISPs take to refresh their routes. Keep this in mind when announcing or withdrawing a prefix from your account, and plan accordingly.
6164

6265
## Delete a prefix
6366

@@ -66,10 +69,6 @@ You can only delete a prefix with an **Unapproved** status. To delete prefixes w
6669
1. From the **IP Prefixes** tab, locate the prefix you want to modify and select **Delete**.
6770
2. Confirm your choice from the modal by selecting **Delete**.
6871

69-
:::note
70-
Withdrawing a prefix should propagate across Cloudflare's global network almost instantly, with changes typically taking effect within a few minutes at most. However, Cloudflare has no control over how long ISPs take to refresh their routes. Keep this in mind when announcing or withdrawing a prefix from your account, and plan accordingly.
71-
:::
72-
7372
## Border Gateway Protocol (BGP) control for advertisements
7473

7574
Use BGP to control the advertisement status of your prefix - advertised or withdrawn - from Cloudflare's global network for on-demand deployment scenarios. BGP Control works by establishing BGP sessions to Cloudflare's globally distributed Route Reflectors, which will initiate propagation of your prefix advertisement across Cloudflare's global network.

0 commit comments

Comments
 (0)