Live / MeridianLink / Incident
MeridianLink: Potential Data Connect Refresh Delay
MeridianLink · meridianlink.comMinor incidentResolved2026-10-30 15:15 UTC
Public — what happened
Summary
MeridianLink said a possible delay in refreshing Data Connect information began on 2026-10-30 at 04:10 UTC, after its team was alerted to a failure in the process that updates the day's data. The company said this was linked to the Consumer server being down for maintenance, and that clients who normally get data around 12 AM PST / 3 AM EST could be affected. By 13:10 UTC it said only 9 clients were still waiting for a refresh and estimated about 3 more hours to finish. The incident is marked resolved as of 15:15 on the same day.
Affected
Data Connect Refresh Status
Timeline
- Started — 2026-10-30 04:10 UTC
- Identified — 2026-10-30 04:10 UTC (2 updates)
- Resolved — 2026-10-30 15:15 UTC · 11h 05m 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.