Changelog

We’ve completed one of our biggest infrastructure upgrades yet: migrating our analytics to a new datastore with significantly more processing power and optimized materialized views. This allows us to present analytics data much faster and makes it easier to roll out new analytics features in the future.

Got feedback on what you'd like to see in Analytics? We’d love to hear from you—reach out via chat or at support@redirect.pizza.

We’ve completed a migration of our certificate storage from SSD to NVMe-based storage to improve SSL handshake times for domains that aren't cached at a specific edge node location. Since uncached domains need to retrieve certificates from storage, switching to NVMe-based storage enables faster certificate retrieval. This results in better performance, particularly in the 99th percentile of requests where certificates aren’t already cached.

With this migration finished, we continue our mission to provide the fastest redirecting platform out there.

We’ve also added a hot-spare option for our certificate storage. In case of maintenance or outages on our primary storage, we can now seamlessly switch to this hot-spare, allowing faster recovery and increased platform reliability.

We’ve improved the search functionality when filtering by a specific domain combined with a path. Results now only include exact matches for the domain, while the path is partially matched. This helps you find the redirect you're looking for more efficiently.

We fixed several cases where redirect flattening wasn’t applied correctly. These cases have been resolved, and our test suite has been expanded to cover more scenarios, ensuring even more redirects can be flattened—resulting in fewer hops and faster redirects.

Interested in using redirect flattening? You can learn more about it here: https://redirect.pizza/support/redirect-flattening

We’ve added a hit counter for dynamic destinations, making it easy to see how many requests were sent to a specific destination within a redirect.

Additionally, we’ve improved the styling of the hits indicator across the platform to ensure a consistent and polished user experience.

Starting January 2025, wildcard redirects can now be applied instantly without the need to issue a new SSL certificate for each hostname. This is achieved by obtaining a true wildcard SSL certificate for each wildcard redirect.

By adding the _acme-challenge NS record to your domain, your redirect will be automatically converted to a wildcard certificate, ensuring better scalability and higher performance.

We've introduced the {domain.subdomains.*} destination variable, which is especially useful when working with subdomains and only needing specific parts of the source domain.

For example, if you want to use the result of a wildcard in the destination's subdomain:

Source: *.test.example.com
Destination: {domain.subdomains.0}.destination.com

This allows you to dynamically map subdomains from the source to your desired destination.

You can now configure CNAME records, direct IP URLs, and even geolocation directly from your Dedicated IP detail screen. Setup is available immediately after activation—no need to contact support.