Movable Ink logo

Is Movable Ink Down?

SaaSLive status, outages, and incident history

No. Movable Ink is up right now.

Every monitored Movable Ink system is operational as of August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 24m agoLive, rechecked every 60s
How we know: the official Movable Ink status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Movable Ink Component Status

The main Movable Ink systems on this page. All 20 are operational right now.

20operational
Da Vinci - ESP Integrations » Acoustic Campaign
Operational
Da Vinci - ESP Integrations » Adobe Campaign Classic
Operational
Da Vinci - ESP Integrations » Amazon SES
Operational

17 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Da Vinci - ESP Integrations » Braze, Da Vinci - ESP Integrations » Cheetah Messaging, Da Vinci - ESP Integrations » Cordial, Da Vinci - ESP Integrations » Oracle Responsys, Da Vinci - ESP Integrations » SalesForce Marketing Cloud, Da Vinci - ESP Integrations » Zeta, Da Vinci » Analytics, Da Vinci » Data Processing, Da Vinci » Link Redirect, Da Vinci » Signal, Da Vinci » Web App, Studio - Integrations » Exchange Integrations, and 5 more.

Create a free account

Component statuses may change independently during partial outages.

Recent Movable Ink Outages & Incidents

Incident history from the official Movable Ink status page, including resolution updates.

Uptime history4 days observed
Aug 8100.00% averageAug 11
Da Vinci - Click-Through Links Experiencing Certificate ErrorsResolved Jul 30, 2026 · 1h 13mResolved

## Incident Summary On July 30, 2026, between 20:13 UTC and 21:54 UTC \(4:13 PM–5:54 PM ET\), Da Vinci experienced an interruption affecting HTTPS traffic on the `coherentpath.link` tracking domain. During this period, recipients clicking links in proof or production emails could encounter a browser security warning indicating that the site's security certificate had expired. Users generating or proofing campaigns that relied on the affected tracking domain could also experience the same error. Click and open events initiated during the incident were unable to reach Da Vinci's tracking service and therefore were not recorded. The issue was caused by the expiration of the TLS certificate serving `coherentpath.link` before a replacement certificate could be successfully provisioned. The renewal process was blocked because the certificate configuration still included domains associated with previously off-boarded clients. Since those domains no longer resolved to the production infrastructure, Google's managed certificate service was unable to issue the replacement certificate before the existing certificate expired. The issue was limited to HTTPS traffic. The underlying application and HTTP endpoint remained available throughout the incident. ## Resolution Engineering restored service by removing obsolete client domains from the certificate configuration and updating the production infrastructure to use a valid certificate while a replacement managed certificate was provisioned. Once the updated certificate was deployed, the team validated HTTPS connectivity across the affected environments and re-synchronized impacted creatives to regenerate valid tracking links.Service was fully restored by 21:54 UTC, after which the incident was declared resolved. ## Corrective Actions To reduce the likelihood of a similar issue recurring, we are implementing several improvements to certificate and infrastructure management.We are adding proactive monitoring to alert on upcoming certificate expirations at least 14 days in advance, as well as alerts for managed certificate provisioning failures so renewal issues can be identified before they impact production. We are also strengthening the client off-boarding process to ensure retired domains are removed from both ingress configuration and certificate definitions as part of the standard workflow. In addition, production load-balancing resources will be brought under infrastructure-as-code management to reduce configuration drift and simplify future incident response. Monitoring around domain health, certificate status, and production routing will also be expanded to improve detection and diagnosis of similar issues. --- [2026-07-30T18:49:27.106-04:00] (resolved) The updated security certificate has been deployed, and Da Vinci click-through links are now functioning as expected. Please reach out to the Technical Support team if you continue to experience issues or have additional questions. A post-mortem will be shared within 7 business days. --- [2026-07-30T17:36:17.026-04:00] (investigating) We are investigating an issue impacting Da Vinci click-through links due to an expired security certificate. Our Engineering team is actively working to resolve the issue and will provide an update as soon as more information is available.

Studio - Login/Access Issues for Multiple Clients & UsersResolved Jul 23, 2026 · 1h 4mResolved

This incident has been resolved by our engineering team. All services have been restored and users are able to access Studio again. --- [2026-07-23T09:33:03.647-04:00] (identified) The issue has been identified by our Engineering team and a fix will be implemented shortly --- [2026-07-23T08:50:53.451-04:00] (investigating) Users may be experiencing trouble with logging into/accessing the Studio platform. Our Engineering team is currently investigating. We will post an update in 1 hour.

Studio - Content Serving Disruption (US-East)Resolved Jun 29, 2026 · -695 minResolved

Between 11:11 PM ET on June 28, 2026 and 12:04 AM ET on June 29, 2026, Studio experienced a content serving disruption affecting requests routed through our US-East region. Requests routed through our EU or US-West regions were unaffected and completed normally. Our Engineering team has confirmed that content serving has fully recovered and the platform is operating normally. Please reach out to the Technical Support team if you continue to see this issue or have additional questions. A post-mortem will be posted within 7 business days.

Live Movable Ink Outage Reports

Problems reported by engineers using Movable Ink. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Movable Ink problems reported yet.

Something wrong with Movable Ink on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Movable Ink

Movable Ink exposes 29 monitored components on its status page at status.movableink.com — Studio, Web App and Acoustic Campaign among them. Follow Movable Ink downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured Movable Ink uptime at 100.00%. Response times, incident history, and SLA tracking for Movable Ink are available on the PulsAPI dashboard.

Movable Ink Status FAQ

Is Movable Ink down right now?

PulsAPI checks Movable Ink every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Movable Ink status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Movable Ink is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Movable Ink recovers.

How do I check Movable Ink uptime history?

PulsAPI tracks Movable Ink uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Movable Ink.

How fast does PulsAPI detect Movable Ink outages?

PulsAPI polls the official Movable Ink status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Movable Ink components?

Yes. PulsAPI monitors 20 individual Movable Ink components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Movable Ink goes down?

Yes. Create a PulsAPI account and subscribe to Movable Ink. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Movable Ink status changes.

How do I report an issue with Movable Ink to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Movable Ink problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Movable Ink?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Movable Ink alongside up to 9 other services at pulsapi.com/signup.

Track Movable Ink with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Movable Ink status changes.

Start free trial