Rebrandly incident

Downtime in links redirection

Major Resolved View vendor source →

Rebrandly experienced a major incident on August 24, 2020 affecting Branded Links redirect (Domain Names registered via Rebrandly) and Branded Links redirect (Domain Names managed outside Rebrandly) and 1 more component, lasting 6h 6m. The incident has been resolved; the full update timeline is below.

Started
Aug 24, 2020, 01:03 PM UTC
Resolved
Aug 24, 2020, 07:10 PM UTC
Duration
6h 6m
Detected by Pingoru
Aug 24, 2020, 01:03 PM UTC

Affected components

Branded Links redirect (Domain Names registered via Rebrandly)Branded Links redirect (Domain Names managed outside Rebrandly)Generic short URLs redirect

Update timeline

  1. investigating Aug 24, 2020, 01:03 PM UTC

    We just identified a downtime in links redirection, investigating right now

  2. identified Aug 24, 2020, 01:21 PM UTC

    We are continuing to investigate this issue. Logs indicate that there is an ongoing DDOS attack targeting the Rebrandly redirection system. Link redirection is experiencing a high latency as a consequence of the high traffic producing stress in the system. Expecting 50% of the requests to be served with higher-than-usual latency.

  3. identified Aug 24, 2020, 01:35 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Aug 24, 2020, 01:41 PM UTC

    An architectural solution has been delivered so that all Branded Links are back working as usual, as part of the Rebrandly emergency plan for this scenario. The problem still persists for links created with the rebrand.ly domain name, a patch will be delivered soon.

  5. identified Aug 24, 2020, 03:46 PM UTC

    We are continuing to work on a solution for this issue.

  6. identified Aug 24, 2020, 04:14 PM UTC

    95% of requests for links with rebrand.ly domain name are being served as usual in response to actions taken to mitigate the issue.

  7. monitoring Aug 24, 2020, 04:37 PM UTC

    A fix has been implemented and we are monitoring the results.

  8. resolved Aug 24, 2020, 07:10 PM UTC

    This incident has been resolved.