Live / MeridianLink / Incident
MeridianLink: Data Connect – Delayed Table Refreshes
MeridianLink · meridianlink.comMinor incidentResolved2026-10-23 19:42 UTC
Public — what happened
Summary
MeridianLink said some Data Connect tables were not refreshing as expected, which began on 2026-10-19 and could leave downstream reports showing older data. The company said the problem grew from 3 tables to 37, and that it traced the delay to a table used to capture data changes not being refreshed often enough; it also reported a separate issue affecting DEMO/BETA pipelines. On 2026-10-22 it said the issues were fixed and under monitoring, but later that day it said it had found duplicate records in the 10/21-10/22 refresh of the 37 tables. MeridianLink said it is investigating and working on a fix, and the incident is not resolved.
Affected
Data Connect Refresh Status
Timeline
- Started — 2026-10-19 13:03 UTC
- Investigating — 2026-10-19 13:03 UTC (2 updates)
- Monitoring — 2026-10-19 20:51 UTC (2 updates)
- Identified — 2026-10-21 16:56 UTC
- Monitoring — 2026-10-22 00:46 UTC
- Identified — 2026-10-22 15:40 UTC
- Monitoring — 2026-10-22 20:30 UTC
- Investigating — 2026-10-23 13:52 UTC
- Resolved — 2026-10-23 19:42 UTC · 4 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach MeridianLink against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for MeridianLink: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the MeridianLink report →
More from MeridianLink
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.