Affected components
Update timeline
- monitoring Apr 22, 2026, 07:05 PM UTC
We experienced a minor outage with app.amplience.com logging into Dynamic Content. The spike to performance has since subsided and we a now monitoring the situation. We can confirm that Dynamic Content is now accessible.
- resolved Apr 22, 2026, 07:24 PM UTC
The issue is resolved. app.amplience.net logins are working as expected
- postmortem Apr 29, 2026, 09:19 AM UTC
**Incident Start Date** 19:40 BST **Incident End Date** 19:54 BST **Issue Summary** On Wednesday evening, users were unable to log into [app.amplience.net](http://app.amplience.net) for a period of 14 minutes. **Root Cause** Our third-party authentication provider, Auth0, experienced a DNS outage caused by a misconfiguration on their side. This incident also impacted some of our alerting capabilities, which we are currently reviewing with our partners. **Resolution** Auth0 resolved their DNS issue, restoring normal authentication services. **Corrective Actions** * Review and strengthen alerting to ensure visibility is maintained during third-party DNS-related incidents * Work with Auth0 to understand the full scope of the misconfiguration and their preventative measures
Looking to track Amplience downtime and outages?
Pingoru polls Amplience's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Amplience reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Amplience alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required