Amplience logo

Is Amplience Down?

SaaSLive status, outages, and incident history

No. Amplience is up right now.

Every monitored Amplience system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 9m agoLive · every 60s

Know the moment Amplience breaks

Amplience is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Amplience status page
How we know: the official Amplience status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Amplience Status Summary

As of 16:42 UTC on 14 November 2026, Amplience is operational. PulsAPI checked Amplience's official status page and found 6 of 6 components operational, with no active incidents. The latest incident, "Delays sending and receiving emails to support", was on Nov 12, 2026 and lasted 37h 53m.

Cite as: PulsAPI, “Amplience status”, checked 14 November 2026, 16:42 UTC. https://www.pulsapi.com/services/amplience

Amplience Component Status

The main Amplience systems on this page. All 6 are operational right now.

6operational
Content Operations Platform » CMS
Operational
Content Operations Platform » DAM
Operational
Content Operations Platform » Dynamic Media
Operational

3 more components tracked

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

Also tracking Content Operations Platform » Workforce, Documentation hub, Support.

See all of them free

Component statuses may change independently during partial outages.

Recent Amplience Outages & Incidents

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

Delays sending and receiving emails to supportResolved Nov 12, 2026 · 37h 53mResolved

Microsoft has confirmed that the issue affecting email delivery has been resolved. We are now working through the backlog of emails, and some delays may continue while normal service is restored. Thank you for your patience --- [2026-11-13T08:37:44.775+00:00] (investigating) Microsoft continues to investigate their global outage. Amplience Support can still be reached through our portal at https://support.amplience.com. --- [2026-11-12T18:13:52.552+00:00] (investigating) We are currently experiencing issues with our email provider, which may result in delays to email delivery. Our Support Portal remains fully operational, and you can continue to log new tickets and view or update existing tickets directly at https://support.amplience.com.

SVGs failing to render in DAMResolved Nov 11, 2026 · 3h 0mResolved

This incident has been resolved. --- [2026-11-11T13:45:49.767+00:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-11-11T13:33:17.145+00:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-11-11T11:54:30.622+00:00] (investigating) We are currently investigating this issue.

Broccoli2Shell vulnerability (CVE-2026-111497)Resolved Oct 26, 2026 · 41h 52mResolved

Our engineering and security teams have completed their assessment of the Broccoli2Shell vulnerability (CVE-2026-111497). Appropriate mitigations have been implemented to address the identified risks. We consider this matter resolved and will continue to monitor for any further developments. --- [2026-10-28T11:49:03.855+00:00] (investigating) We are continuing to investigate this issue. --- [2026-10-26T17:57:07.564+00:00] (investigating) We are aware of the recently disclosed Broccoli2Shell vulnerability (CVE-2026-111497). Our engineering and security teams are actively investigating the potential impact on Amplience services and assessing whether any additional protective measures are required. We are treating this assessment as a priority and will provide further updates as appropriate.

Amplience Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Amplience incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% average · 3 days with incidentsNov 14

Live Amplience Outage Reports

Problems reported by engineers using Amplience. 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 Amplience problems reported yet.

Something wrong with Amplience on your end?

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

About Amplience

Amplience's status page at status.amplience.com lists 6 components, such as CMS, DAM and Dynamic Media. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Amplience's side or yours.

Amplience Status FAQ

Is Amplience down right now?

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

What should I do if Amplience 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 Amplience recovers.

How do I check Amplience uptime history?

PulsAPI tracks Amplience uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Amplience changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Amplience outages?

PulsAPI reads the official Amplience status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Amplience components?

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

Can I get alerts when Amplience goes down?

Yes. Create a free account and subscribe to Amplience: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Amplience 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 Amplience problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Amplience?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Amplience plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Amplience with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services