Uberall Outage History

Uberall is up right now

Uberall had 10 outages in the last 2 years totaling 6h 11m of downtime — averaging 0.4 incidents per month.

There were 10 Uberall outages since September 22, 2025 totaling 6h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.uberall.com

Critical September 21, 2026

Store Locator outage

Detected by Pingoru
Sep 21, 2026, 12:45 PM UTC
Resolved
Sep 21, 2026, 12:59 PM UTC
Duration
13m
Timeline · 1 update
  1. investigating Sep 21, 2026, 12:45 PM UTC

    We are investigating an issue affecting not set.

Read the full incident report →

Major September 21, 2026

Store Locator Outage

Detected by Pingoru
Sep 21, 2026, 12:44 PM UTC
Resolved
Sep 21, 2026, 12:57 PM UTC
Duration
13m
Timeline · 4 updates
  1. investigating Sep 21, 2026, 12:44 PM UTC

    We're aware of issues impacting the Store Locator.

  2. identified Sep 21, 2026, 12:51 PM UTC

    We've identified the issue.

  3. monitoring Sep 21, 2026, 12:52 PM UTC

    We're monitoring the fix.

  4. resolved Sep 21, 2026, 12:57 PM UTC

    The issue has been fully resolved.

Read the full incident report →

Major January 27, 2026

API performance degradation

Detected by Pingoru
Jan 27, 2026, 11:07 AM UTC
Resolved
Jan 27, 2026, 04:51 PM UTC
Duration
5h 44m
Timeline · 2 updates
  1. investigating Jan 27, 2026, 11:07 AM UTC

    We're experiencing elevated API latency. We're taking steps to mitigate the situation and we will continue to monitor the situation

  2. resolved Jan 27, 2026, 05:07 PM UTC

    The issue was fully resolved at 13:30 CET.

Read the full incident report →

Critical September 25, 2025

Production API is down

Detected by Pingoru
Sep 25, 2025, 10:06 PM UTC
Resolved
Sep 25, 2025, 09:31 PM UTC
Duration
Timeline · 3 updates
  1. resolved Sep 25, 2025, 10:06 PM UTC

    This incident has been resolved.

  2. investigating Sep 25, 2025, 10:06 PM UTC

    The API is not responding successfully to the healthcheck

  3. investigating Sep 25, 2025, 10:06 PM UTC

    [Comment from Opsgenie]mauro.junior acknowledged alert: "Production API is down"

Read the full incident report →

Critical September 25, 2025

Production Webapp is down

Detected by Pingoru
Sep 25, 2025, 10:06 PM UTC
Resolved
Sep 25, 2025, 09:30 PM UTC
Duration
Timeline · 3 updates
  1. investigating Sep 25, 2025, 10:06 PM UTC

    [Comment from Opsgenie]mauro.junior acknowledged alert: "Production Webapp is down"

  2. resolved Sep 25, 2025, 10:06 PM UTC

    This incident has been resolved.

  3. investigating Sep 25, 2025, 10:06 PM UTC

    Synthetics check for the Webapp failed

Read the full incident report →

Notice September 22, 2025

Database failover

Detected by Pingoru
Sep 22, 2025, 10:43 AM UTC
Resolved
Jun 24, 2021, 08:36 AM UTC
Duration
Timeline · 1 update
  1. resolved Sep 22, 2025, 10:43 AM UTC

    We triggered a failover of our main database, and some API calls timed out for 2 minutes.

Read the full incident report →

Notice September 22, 2025

Production Website is down

Detected by Pingoru
Sep 22, 2025, 10:43 AM UTC
Resolved
Jul 08, 2021, 09:55 AM UTC
Duration
Timeline · 2 updates
  1. investigating Sep 22, 2025, 10:43 AM UTC

    The Website is not responding successfully to the healthcheck

  2. resolved Sep 22, 2025, 10:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 22, 2025

Production StoreFinder is down

Detected by Pingoru
Sep 22, 2025, 10:43 AM UTC
Resolved
Jul 28, 2021, 12:33 AM UTC
Duration
Timeline · 2 updates
  1. resolved Sep 22, 2025, 10:43 AM UTC

    This incident has been resolved.

  2. investigating Sep 22, 2025, 10:43 AM UTC

    Synthetics check for the StoreFinder failed

Read the full incident report →

Critical September 22, 2025

Landing page down

Detected by Pingoru
Sep 22, 2025, 10:43 AM UTC
Resolved
Sep 27, 2021, 07:10 PM UTC
Duration
Timeline · 2 updates
  1. monitoring Sep 22, 2025, 10:43 AM UTC

    The landing powered by a 3rd-party is currently down (returning 503)

  2. resolved Sep 22, 2025, 10:43 AM UTC

    This incident has been resolved.

Read the full incident report →