Edge network migration

The legacy network was taken offline in January 2025, after a two-year migration period. If a redirect stopped working because its hostname still pointed at the legacy network, follow the steps under "What you need to do" to reactivate it.

Background

In May 2022 we launched our current global edge network. Its servers are located close to your visitors, which makes it the fastest network we've run. We own the IP space of this network, so future changes on our side won't require a DNS change from you.

What it means for you

Hostnames that still point at the legacy IP addresses or hostname need a one-time DNS change. This overview lists every hostname in your account that still needs it.

What you need to do

  • A records: replace 89.41.169.49 with 89.106.200.1
  • AAAA records: replace 2a01:7c8:e001:1a:0:0:0:6ab2 with 2a12:5240::1
  • CNAME records: replace a.redirect.pizza with edge.redirect.pizza

Once the change has propagated, redirect.pizza detects it automatically and the redirect resumes.

Questions?

Email support@redirect.pizza. We're happy to help.

More articles

Setup & Configuration
What are these DNS changes?
What DNS types can I use?
How long does the DNS change take?
Troubleshooting new redirects
Redirecting non-www to www
Redirect settings
Matching
Regex matching
Wildcard subdomains
Destination variables
Dynamic destinations
Redirect flattening
SSL profiles
robots.txt
Monitoring redirect.pizza itself
Features
Automatic HTTPS
Automatic DNS
Nameservers
Analytics
Broken destination monitoring
Email forwarding
Pause and resume
Dedicated IP
API
MCP
Zapier
Terraform provider
Security & Account
Team management
Two-factor authentication
SAML SSO
SSO via Okta
Summary email
HSTS (HTTP Strict Transport Security)
Prevent foreign embedding
Web Application Firewall (WAF)
Security & compliance
Subprocessors
Service level agreement (SLA)
Walkthroughs
GoDaddy: Forwarding with HTTPS support
Namecheap: Forwarding with HTTPS support
Cloudflare: Forwarding with HTTPS support
Network Solutions: Forwarding with HTTPS support
Hover: Forwarding with HTTPS support
Amazon Route 53: Forwarding with HTTPS support
Google Cloud DNS: Forwarding with HTTPS support
Azure DNS: Forwarding with HTTPS support
DigitalOcean: Forwarding with HTTPS support
NS1: Forwarding with HTTPS support
DNS Made Easy: Forwarding with HTTPS support
TransIP: Forwarding with HTTPS support
EuroDNS: Forwarding with HTTPS support
Mijndomein: Forwarding with HTTPS support
Freenom: Forwarding with HTTPS support