Pearch Outage History

Pearch is up right now

Pearch had 6 outages in the last 2 years totaling 16h 20m of downtime, averaging 0.2 incidents per month.

There were 6 Pearch outages since July 28, 2026 totaling 16h 20m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.pearch.ai

Minor October 7, 2026

Degraded API performance

Detected by Pingoru
Oct 07, 2026, 05:43 PM UTC
Resolved
Oct 07, 2026, 05:54 PM UTC
Duration
10m
Timeline · 2 updates
  1. investigating Oct 07, 2026, 05:43 PM UTC

    Status: Investigating We are investigating degraded performance affecting the Pearch API. Some requests may fail or respond slower than usual. We will post an update as soon as we know more. Affected components Api (Partial outage)

  2. resolved Oct 07, 2026, 05:54 PM UTC

    Status: Resolved This incident has been resolved and the Pearch API is operating normally. Thank you for your patience.

Read the full incident report →

Minor September 14, 2026

API partial outages — historical monitoring correction (8–14 September)

Detected by Pingoru
Sep 14, 2026, 04:00 PM UTC
Resolved
Sep 14, 2026, 04:00 PM UTC
Duration
–
Timeline · 1 update
  1. resolved Sep 14, 2026, 04:00 PM UTC

    Status: Resolved Retrospective correction based on scheduled fast end-to-end API checks from 8–14 September 2026. Downtime is counted only for segments with at least two consecutive failed checks, five minutes apart. Each failure within a qualifying segment contributes five minutes; isolated failures and gaps are excluded. This yields seven partial-outage periods totaling 90 minutes. GCP checks are used through 12 September and Azure checks from 13 September. These impact windows supersede the longer alert-lifetime downtime estimates for the same monitoring issues. All affected periods have ended.

Read the full incident report →

Minor September 1, 2026

Problems with Cloud Infrastructure

Detected by Pingoru
Sep 01, 2026, 02:47 PM UTC
Resolved
Sep 01, 2026, 03:55 PM UTC
Duration
1h 8m
Affected: Api
Timeline · 2 updates
  1. monitoring Sep 01, 2026, 02:47 PM UTC

    Status: Monitoring GCP Affected components Api (Partial outage)

  2. resolved Sep 01, 2026, 03:55 PM UTC

    Status: Resolved Cloud issues Affected components Api (Operational)

Read the full incident report →

Minor August 4, 2026

Dependency failures

Detected by Pingoru
Aug 04, 2026, 06:39 AM UTC
Resolved
Aug 04, 2026, 03:57 PM UTC
Duration
9h 17m
Affected: Api
Timeline · 3 updates
  1. investigating Aug 04, 2026, 06:39 AM UTC

    Status: Investigating Search returning empty results from 12pm to 16pm due to dependency failures. Affected components Api (Partial outage)

  2. investigating Aug 04, 2026, 07:40 AM UTC

    Status: Investigating Regression because of dependency failure Affected components Api (Operational)

  3. resolved Aug 04, 2026, 03:57 PM UTC

    Status: Resolved - Affected components Api (Operational)

Read the full incident report →

Minor July 28, 2026

Slow service performance

Detected by Pingoru
Jul 28, 2026, 05:08 PM UTC
Resolved
Jul 28, 2026, 10:24 PM UTC
Duration
5h 16m
Affected: Api
Timeline · 3 updates
  1. investigating Jul 28, 2026, 05:08 PM UTC

    Status: Investigating _ Affected components Api (Partial outage)

  2. monitoring Jul 28, 2026, 05:47 PM UTC

    Status: Monitoring Issues with the third-party provider Affected components Api (Degraded performance)

  3. resolved Jul 28, 2026, 10:24 PM UTC

    Status: Resolved _ Affected components Api (Operational)

Read the full incident report →

Minor July 28, 2026

High load

Detected by Pingoru
Jul 28, 2026, 02:04 PM UTC
Resolved
Jul 28, 2026, 02:31 PM UTC
Duration
27m
Affected: Api
Timeline · 2 updates
  1. monitoring Jul 28, 2026, 02:04 PM UTC

    Status: Monitoring Response time may be longer Affected components Api (Degraded performance)

  2. resolved Jul 28, 2026, 02:31 PM UTC

    Status: Resolved The search backend is separate from the main system Affected components Api (Operational)

Read the full incident report →