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

As listed on MeridianLink’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the MeridianLink status & history page.

Related: MeridianLink status & history. SquidGrid is not affiliated with MeridianLink.