rewindex

ChangesModeDiscovery Database Stale Data

Mode: Critical incident: Discovery Database Stale Data

Major incidentdegradation (model (Jev), 92%)Changed Detected status.modeanalytics.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Mode removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Discovery Database Stale Data
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-02-23 22:12 UTC
AddedResolved time#5
Before: not present
After: 2025-02-23 22:12 UTC
AddedAffected components#6
Before: not present
After: Discovery Database
AddedUpdateinvestigating#7
Before: not present
After: We are aware of and investigating an issue that is intermittently blocking scheduled updates to the Discovery Database's data feed at the table level resulting in incomplete, stale, or incorrect data.
AddedUpdateidentified#8
Before: not present
After: We have identified that the issue previously reported as causing degraded performance has escalated and is now significantly impacting the functionality of the Discovery Database. Our team is actively investigating the root cause and working to resolve the problem as quickly as possible.
AddedUpdateidentified#9
Before: not present
After: Our Engineers have deployed a mitigation to address the degraded performance in the Discovery Database. The changes may not take effect before the next scheduled daily run. We expect to perform additional work next week during normal business hours to rectify the situation.
AddedUpdateresolved#10
Before: not present
After: We believe this issue to now be resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

History of this incident

Sunday, February 23, 2025

1 incident change

Cite this

Critical incident: Discovery Database Stale Data on Mode’s status page, changed 2025-02-23 22:12 UTC (change 1 of 1).

Title
Critical incident: Discovery Database Stale Data
Vendor
Mode
Date
URL
https://rewindex.com/change/i9807025c741a00

All Mode changesMode profileMarkdownJSON