Live / MeridianLink / Incident
MeridianLink: Data Connect – Data Refresh Delay
MeridianLink · meridianlink.comMinor incidentResolved2026-10-28 17:09 UTC
Public — what happened
Summary
MeridianLink said a delay in refreshing data affected most clients of its Data Connect product, and it began investigating at 12:37 UTC on 2026-10-28. By 13:31 UTC the company reported the delayed data was available again and asked clients to re-run their process to pick up missing records. It said it was still looking into the root cause at that point, and the incident was marked resolved at 17:09 UTC. The status text provided does not say what caused the delay.
Affected
Data Connect Refresh Status
Timeline
- Started — 2026-10-28 12:37 UTC
- Investigating — 2026-10-28 12:37 UTC
- Monitoring — 2026-10-28 13:31 UTC
- Resolved — 2026-10-28 17:09 UTC · 4h 32m 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 45, 2026, our weekly internet health report.