You can now upsert redirects through both the API and import functionality. Instead of manually fetching the redirect to determine whether it requires creation or updating, existing redirects are updated automatically when a match is found. This makes bulk updates and automated workflows much easier to manage. Set the `upsert` boolean to `true` on the POST /api/v1/redirects call.
We fixed several issues affecting Azure DNS when working with large zones. Record syncing and lookups are now more reliable, improving overall stability for domains with many entries.
We now automatically detect SYN flood attack patterns and temporarily block the offending IPs in real-time via our centralized RTBH. This helps reduce unnecessary load on the platform and keeps your redirects performing reliably, even under malicious traffic.
Our regex parser has been optimized to handle complex redirect rules more efficiently. Matching is now faster and more consistent, especially for teams with large or advanced configurations.
We've made several upgrades to our DDoS protection. This includes adding more infrastructure resources, increasing available L3 bandwidth, and introducing an additional fallback BGP provider. Together, these changes improve resilience and ensure more stable performance during traffic spikes or attacks in L3 scenarios.
You can now download your payment receipts as PDF files directly from the billing section. This makes it easier to store, forward, or submit them for accounting purposes.
We've added Azure DNS to our list of supported providers for Automatic DNS. If your domain is managed in Azure, you can now set up all required DNS records through the automated set-up flow. No need to manually update records in the Azure portal.
The analytics raw API endpoint now includes the redirect_id field. This makes it easier to match analytical events to specific redirects.