Changelog

Our API documentation has been fully rewritten. It’s cleaner, easier to navigate, and includes clearer examples and better endpoint descriptions, all in a fresh new style. See the updated documentation here: redirect.pizza API

Team owners can now reset two-factor authentication for any team member. If someone loses access to their authentication device, you can help them regain access—no need to contact support.

You can now export all your source hostnames as a CSV file from the dashboard. Useful for quick audits, backups, or sharing, with details like HSTS status and embedding protection included.

We’ve enhanced our internal abuse handling processes, enabling us to detect and block bad actors more quickly. These improvements help us maintain a secure, stable, and zero-tolerance platform.

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