Major incident

Rebrandly: Elevated error rate on link creation API

Affected: Rebrandly API (Classic Workspaces), Rebrandly API (Extended Workspaces)

Current status of Rebrandly: Operational — live Rebrandly status

Timeline

1. May 12, 2026, 17:45 UTC
   investigating
   We are investigating elevated error rates (403s & 500s)on the Rebrandly link creation API. Some customers may receive "permission denied" responses when creating links via the API, and bulk creation requests may complete with fewer links than requested. Authentication and link redirection are not affected, and existing links continue to work normally. We will provide an update within 1 hour
2. May 12, 2026, 18:46 UTC
   investigating
   We have addressed one contributing factor (database write throttling) and are continuing to investigate a separate factor that is keeping customer-facing error rates elevated. Authentication and link redirection remain unaffected. We will provide another update within 1 hour.
3. May 12, 2026, 19:44 UTC
   identified
   We have identified the cause as a cache configuration issue in our link creation path. A fix is now being deployed across our infrastructure, and we expect customer-facing error rates to begin returning to normal as the deployment completes. Authentication and link redirection remain unaffected. We will provide another update within 1 hour.
4. May 12, 2026, 19:53 UTC
   monitoring
   A fix has been deployed and customer-facing error rates have returned to normal levels. We are monitoring for stability before declaring the incident fully resolved. Authentication and link redirection remain unaffected. We will provide another update within 1 hour.
5. May 12, 2026, 20:28 UTC
   resolved
   This incident has been fully resolved. The link creation API is operating normally and the underlying cause has been addressed. Authentication and link redirection were not affected throughout the incident. We apologize for the disruption and thank you for your patience. A post-incident review will be conducted and shared with our customers, as part of our standard process.

Updates as published by Rebrandly (original).