What’s new in Relay

7 releases shown

1. 04Nov 2026v4.12

   Replay by time window

   When a customer’s server is down for 40 minutes, you no longer replay deliveries one by one. Pick the window, see how many events it holds, and send them again — in their original order.

   1. Replay a time window from the dashboardFeature

      Endpoint › Deliveries › Replay window. A preview shows the event count before anything is sent.

   2. POST /v4/replaysFeature

      The same thing from the API, with a dry_run flag that returns the count only.

   3. Replays kept the original signature timestampFix

      Replayed deliveries are now signed at send time, so strict receivers no longer reject them as stale.

   Read the v4.12 notes
2. 21Oct 2026v4.11

   Static egress IPs in Singapore

   Scale projects in ap-southeast-1 now deliver from two fixed addresses that your customers can put on an allow-list.

   1. Two static IPs per regionFeature

      Listed under Settings › Network, and at GET /v4/egress for automation.

   2. Faster TLS handshakes to APAC endpointsImprovement

      Session resumption cut median connect time from 212 ms to 74 ms.

   Read the v4.11 notes
3. 07Oct 2026v4.10

   Portal logs load four times faster

   The embedded portal now streams the first 50 deliveries instead of waiting for the whole page.

   1. Streaming delivery logImprovement

      Time to first row fell from 1.9 s to 0.45 s for endpoints with more than 100k deliveries.

   2. Search by delivery IDImprovement

      Paste dlv_… into the portal search to jump straight to it.

   3. Dark theme contrast in the portalFix

      Status chips now meet 4.5:1 on dark backgrounds.

   Read the v4.10 notes
4. 23Sep 2026v4.9

   Failure alerts by webhook

   Get told about failing endpoints the way your customers get told about everything else: with a signed event.

   1. endpoint.failing and endpoint.recovered eventsFeature

      Sent to an operator endpoint of your choice after 5 consecutive failures, and again on the first success.

   2. Duplicate alert emailsFix

      Endpoints that flapped within a minute sent two emails; now one.

   Read the v4.9 notes
5. 09Sep 2026v4.8

   Idempotency keys on every write

   Retrying your own send call after a timeout no longer risks sending the event twice.

   1. Idempotency-Key headerFeature

      Keys are kept for 24 hours; a repeat returns the first response with relay-idempotent-replay: true.

   2. SDKs set keys for youImprovement

      Node, Python, Go and Ruby SDKs generate a key per call and reuse it on their own retries.

   Read the v4.8 notes
6. 26Aug 2026v4.7

   Per-endpoint rate limits

   A slow customer no longer slows down everyone else: each endpoint gets its own limit and its own queue.

   1. rate_limit on endpointsFeature

      Requests per second, 1 to 500. Over the limit, deliveries wait in the endpoint’s queue instead of failing.

   2. Retry-After was ignored on 429Fix

      We now honour Retry-After up to 10 minutes.

   3. Wrong timezone in CSV exportsFix

      Timestamps are UTC with a Z suffix, as documented.

   Read the v4.7 notes
7. 12Aug 2026v4.6

   Event catalog, public

   Publish your event types and their JSON schemas as a page your customers can browse before they subscribe.

   1. Catalog page per projectFeature

      Hosted at your-project.relay-catalog.example.com or embedded in your docs.

   2. Schema diff on publishImprovement

      Publishing a new schema version shows which fields were added, removed or retyped.

   Read the v4.6 notes

Older releases: v1.0 (2023-03-14) to v4.5 are in the archive.