CallRail incident

Google Ads disruption of service

Minor Resolved View vendor source →

CallRail experienced a minor incident on June 12, 2025 affecting Google Ads, lasting 3h 10m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2025, 06:12 PM UTC
Resolved
Jun 12, 2025, 09:23 PM UTC
Duration
3h 10m
Detected by Pingoru
Jun 12, 2025, 06:12 PM UTC

Affected components

Google Ads

Update timeline

  1. identified Jun 12, 2025, 06:12 PM UTC

    Google Ads is reporting disruptions to its Ads Manager service, which includes the APIs used by our integration. Customers using CallRail's Google Ads Integration may experience degraded service or intermittent failures due to issues with the upstream provider, including delayed conversion reporting data and missing or incorrect CPL, keyword, and campaign data. Customers may also experience issues configuring or authorizing the Google Ads Integration on CallRail's platform. We are closely monitoring the fix and will report when service is restored for all customers.

  2. identified Jun 12, 2025, 06:16 PM UTC

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

  3. identified Jun 12, 2025, 06:17 PM UTC

    Google Ads is reporting disruptions to its Ads Manager service, which includes the APIs used by our integration. Customers using CallRail's Google Ads Integration may experience degraded service or intermittent failures due to issues with the upstream provider, including delayed conversion reporting data and missing or incorrect CPL, keyword, and campaign data. Customers may also experience issues configuring or authorizing the Google Ads Integration on CallRail's platform. We are closely monitoring the fix and will report when service is restored for all customers.

  4. monitoring Jun 12, 2025, 08:55 PM UTC

    Google appears to have fixed the issue; we are continuing to monitor for any impacts.

  5. monitoring Jun 12, 2025, 09:01 PM UTC

    Google appears to have fixed the issue; we are continuing to monitor for any impacts.

  6. resolved Jun 12, 2025, 09:23 PM UTC

    This incident has been resolved.