Rebrandly incident

Login and API timeouts following Cloud provider outage

Major Resolved View vendor source →

Rebrandly experienced a major incident on December 7, 2021 affecting Rebrandly Dashboard and Rebrandly API (Classic Workspaces) and 1 more component, lasting 5h 43m. The incident has been resolved; the full update timeline is below.

Started
Dec 07, 2021, 04:03 PM UTC
Resolved
Dec 07, 2021, 09:47 PM UTC
Duration
5h 43m
Detected by Pingoru
Dec 07, 2021, 04:03 PM UTC

Affected components

Rebrandly DashboardRebrandly API (Classic Workspaces)Rebrandly API (Extended Workspaces)Rebrandly Apps

Update timeline

  1. investigating Dec 07, 2021, 04:03 PM UTC

    We are currently investigating an issue affecting login to Dashboard (including Rebrandly desktop and mobile apps and the browser extensions) and the Link Management API. We are in touch with the Cloud provider (Amazon Web Services) to assess the impact of this partial outage. Links redirection and tracking appear to be not affected by this.

  2. identified Dec 07, 2021, 04:08 PM UTC

    Following our previous communication, we have observed there is a broader issue in our Cloud provider affecting the US East region on multiple availability zones.

  3. identified Dec 07, 2021, 04:33 PM UTC

    Our Cloud provider (Amazon Web Services) reported: [08:26 AM PST] We are experiencing API and console issues in the US-EAST-1 Region. We have identified root cause and we are actively working towards recovery.

  4. identified Dec 07, 2021, 06:41 PM UTC

    We have no available ETA to share yet. We are waiting for our Cloud provider to reinstate services, and are in the process of isolating the specific Amazon services affected by this incident, so as to possibly restore critical API functionality.

  5. monitoring Dec 07, 2021, 09:15 PM UTC

    We observed that critical Rebrandly services are back operative with degraded performances, as the Cloud provider managed to execute a recovery plan. No ETA for a full resolution has been provided yet.

  6. resolved Dec 07, 2021, 09:47 PM UTC

    This incident has been resolved.