Claravine Outage History

Claravine is up right now

Claravine had 3 outages in the last 2 years totaling 109h 34m of downtime — averaging 0.1 incidents per month.

There were 3 Claravine outages since September 5, 2025 totaling 109h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.claravine.com

Notice March 18, 2026

Intermittent Submission Errors Detected

Detected by Pingoru
Mar 18, 2026, 07:30 PM UTC
Resolved
Mar 13, 2026, 05:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 18, 2026, 07:30 PM UTC

    Intermittent submission errors detected at 1:20pm ET. Resolved at 3:20pm ET. No data loss occurred during that timeframe

Read the full incident report →

Notice September 26, 2025

Unable to view certain Claravine application pages

Detected by Pingoru
Sep 26, 2025, 09:35 PM UTC
Resolved
Sep 26, 2025, 04:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 26, 2025, 09:35 PM UTC

    Service restored at 9:34am ET - The Claravine platform response times were restored to allow customers to view their application pages. Claravine isolated the issue to a specific infrastructure pod and took actions to restore it. Incident reported at 9:13am ET - The Claravine platform was reported to have degraded response times and customers may have been temporarily unable to view certain application pages.

Read the full incident report →

Notice September 5, 2025

Reports of processing issues on Adobe Analytics

Detected by Pingoru
Sep 05, 2025, 01:40 AM UTC
Resolved
Sep 09, 2025, 03:15 PM UTC
Duration
4d 13h
Timeline · 2 updates
  1. monitoring Sep 05, 2025, 01:40 AM UTC

    Adobe confirmed reports of processing issues on Adobe Analytics that started on Sep 3, 2025, and that Adobe is actively investigating. Claravine will share an update as soon as we receive more information.

  2. resolved Sep 09, 2025, 03:15 PM UTC

    Resolved - Adobe Analytics processing times are observed to be back to normal. Claravine will continue to monitor and stay in close communication with Adobe.

Read the full incident report →