Serper incident

Degraded API Performance

Minor Resolved View vendor source →

Serper experienced a minor incident on April 27, 2025 affecting Current status by service (API), lasting 48m. The incident has been resolved; the full update timeline is below.

Started
Apr 27, 2025, 06:02 AM UTC
Resolved
Apr 27, 2025, 06:50 AM UTC
Duration
48m
Detected by Pingoru
Apr 27, 2025, 06:02 AM UTC

Affected components

Current status by service (API)

Update timeline

  1. investigating Apr 27, 2025, 06:02 AM UTC

    Some parts of our service are currently experiencing higher than normal latency and an increased number of 429 (rate limit) errors. We're actively looking into it. We're actively investigating the issue and working to restore normal performance as quickly as possible.

  2. resolved Apr 27, 2025, 06:50 AM UTC

    Service performance has returned to normal. We encountered unexpected scaling issues with our cloud provider, which led to increased latency and a higher number of 429 (rate limit) errors. We've provisioned additional resources to mitigate the impact and are continuing to monitor closely. Thank you for your patience.