Magic Transit customers can now configure AS prepending on their BYOIP prefixes advertised at the Cloudflare edge. This allows for smoother traffic migration and minimizes packet loss when changing providers.
AS prepending makes the Cloudflare route less preferred by increasing the AS path length. You can use this to gradually shift traffic away from Cloudflare before withdrawing a prefix, avoiding abrupt routing changes.
Prepending can be configured via the API or through BGP community values when peering with the Magic Transit routing table. For more information, refer to Advertise prefixes.
Source: Cloudflare
Latest Posts
- AWS Lambda MicroVMs is now available in 5 additional AWS regions
- AWS IAM now supports 20 managed policies per role by default
- Web Search in Amazon Bedrock AgentCore adds domain and published date filtering, expands to Europe and Asia Pacific
- MC1323266: Microsoft 365 Copilot Gets Power BI Data Grounding for Answering User Questions
