CallRail incident

CallRail and Lead Center Intermittent Access Delays

Minor Resolved View vendor source →

CallRail experienced a minor incident on September 26, 2024 affecting CallRail Web Application and Lead Center Web Application and 1 more component, lasting 3h 19m. The incident has been resolved; the full update timeline is below.

Started
Sep 26, 2024, 04:13 PM UTC
Resolved
Sep 26, 2024, 07:32 PM UTC
Duration
3h 19m
Detected by Pingoru
Sep 26, 2024, 04:13 PM UTC

Affected components

CallRail Web ApplicationLead Center Web ApplicationLead Center Mobile App

Update timeline

  1. investigating Sep 26, 2024, 04:13 PM UTC

    Some customers are continuing to experience issues accessing the CallRail web app and mobile app. Using the web app incurs several requests each time you navigate, we are seeing a small percentage of these failing. We are aware of these issues and are taking rapid action to resolve the situation. Calls and Dynamic Number Insertion are working normally, though Lead Center may not be accessible for some.

  2. identified Sep 26, 2024, 05:32 PM UTC

    We've identified an issue at our infrastructure provider that appears related to this incident. We're watching that incident, and working to expedite a full resolution for our affected systems.

  3. monitoring Sep 26, 2024, 05:43 PM UTC

    We identified an incident at our infrastructure provider that caused some traffic to fail to route properly through our load balancers. We took steps to reinitialize our load balancers there and our monitoring tools are indicating performance has been restored. We'll continue to watch performance closely to ensure no further action is necessary.

  4. monitoring Sep 26, 2024, 05:56 PM UTC

    We are seeing additional reports of errors when accessing the application. We are investigating and will continue to provide updates.

  5. monitoring Sep 26, 2024, 06:17 PM UTC

    We are seeing systems begin to recover and performance has been restored. We will continue to watch performance closely to ensure no further action is necessary.

  6. resolved Sep 26, 2024, 07:32 PM UTC

    This incident has been resolved.