Live / MeridianLink / Incident
MeridianLink: Data Connect – Data Read Failures on 37 Tables
MeridianLink · meridianlink.comMinor incidentResolved2026-10-16 21:06 UTC
Public — what happened
Summary
MeridianLink said that starting at 12:43 UTC on October 16, 2026, attempts to read data from 37 tables in its Data Connect service failed with an invalid-response error, while other tables and schema lookups kept working. The company said no new data could be pulled for those tables, though data loaded on October 15 and earlier was unaffected. By 15:05 UTC it said it had found the cause, which it attributed to a change in how some tables were partitioned, and began rebuilding the affected tables. A later update said the work was taking longer than expected, and the incident was marked resolved at 21:06 UTC.
Affected
Data Connect Operational Status
Timeline
- Started — 2026-10-16 12:43 UTC
- Investigating — 2026-10-16 12:43 UTC
- Identified — 2026-10-16 15:05 UTC (2 updates)
- Resolved — 2026-10-16 21:06 UTC · 8h 23m 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 43, 2026, our weekly internet health report.