Is Amplience down?
Last checked 3m agoNo incidents right now.
Amplience is operational right now. Last checked 3m ago; the most recent incident resolved 71d ago.
Real-time Amplience status, recent outages, and incident history — pulled directly from Amplience's official status page at https://status.amplience.com every 5 minutes. Pingoru tracks 6 Amplience services and has captured 2 incidents in the last 90 days (99.63% uptime). Get email, Slack, Discord, or webhook alerts the moment Amplience reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Dynamic Content
Timeline · 3 updates
- investigating · Jul 06, 2026, 04:08 PM UTC
We're currently experiencing an elevated level of API errors and are actively investigating the issue. During this time, customers may experience slower response times or intermittent API errors. We apologise for the disruption and will provide further updates as soon as we have more information.
- monitoring · Jul 06, 2026, 04:17 PM UTC
Service has been restored, and we are continuing to monitor the platform closely to ensure stability.
- resolved · Jul 06, 2026, 04:58 PM UTC
This incident is now resolved.
Latest: This incident is now resolved.
-
- Content Hub
Timeline · 3 updates
- identified · Jun 30, 2026, 02:02 PM UTC
We are aware that a subset of legacy processing jobs are experiencing intermittent issues. We have identified the cause and are working to restore normal service. We will provide further updates as progress continues.
- resolved · Jun 30, 2026, 04:34 PM UTC
We have successfully implemented a fix.
- postmortem · Jul 02, 2026, 12:47 PM UTC
**Incident Start Time** 9 June 2026, 00:00 UTC **Incident End Time** 30 June 2026, 17:37 UTC **Issue Summary** A small number of legacy Processing Jobs intermittently failed to run at their scheduled times. As a result, some automated asset processing tasks, such as set creation and metadata updates, were not completed as expected. **Root Cause** The issue was caused by a planned authentication change introduced by Bitbucket as part of the retirement of its app password authentication method. During scheduled transition periods, authentication requests using the deprecated method were temporarily rejected, preventing some Processing Jobs from downloading the scripts required to execute. **Corrective Actions** We have implemented a permanent fix to remove the dependency on the deprecated authentication method. As a result, these Processing Jobs are no longer affected by Bitbucket's scheduled transition periods. We have identified all Processing Jobs impacted during the incident and are replaying them where appropriate to ensure the expected processing is completed. If you have any questions or believe your workflows require additional review, please contact our Support team at [support.amplience.com](http://support.amplience.com).
Latest: **Incident Start Time** 9 June 2026, 00:00 UTC **Incident End Time** 30 June 2026, 17:37 UTC **Issue Summary** A small number of legacy Processing Jobs intermittently failed to r…
-
- Degraded performance with DC-API ResolvedStarted Jul 06, 2026, 04:08 PM UTC · Resolved Jul 06, 2026, 04:58 PM UTC · 50m
- Started Jun 30, 2026, 02:02 PM UTC · Resolved Jun 30, 2026, 04:34 PM UTC · 2h 31m