Extended Service Outage – What Happened
Over the past 24 hours, absentify was unfortunately unavailable for about 20 hours. This is the longest downtime we have ever experienced, and we want to sincerely apologize for the inconvenience this caused.
Our team worked through the entire night to bring the service back online as quickly as possible. Below, we want to be transparent about what happened and how we will ensure that something like this does not happen again.
What happened?
Last night, we made a (seemingly) small update to our Azure infrastructure configuration — an update we had, of course, thoroughly tested in our staging environment beforehand. However, after rolling it out to production, unexpected issues occurred: our service was no longer able to start correctly, and reverting the original settings was no longer possible.
At the same time, the Azure region North Europe did not have enough available resources to redeploy our services. We were forced to switch to other regions, which introduced new technical challenges and delays.
In the end, we had to rebuild large parts of our network infrastructure and architecture from scratch. This process took a significant amount of time and included several unexpected difficulties along the way.
During the day, Microsoft Azure was additionally dealing with DDoS-related issues, which temporarily prevented us from deploying new resources. Once that situation was resolved, we encountered another obstacle: our build process relies on certain assets that are retrieved via Cloudflare — and Cloudflare itself experienced outages today, which disrupted our builds even further.
In short: several external factors came together at the same time, creating a chain reaction that none of our regular procedures could have anticipated.
Why this situation was entirely new for us
- We are ISO-certified and perform quarterly restore tests to ensure we can reliably recover our systems.
- However, we have never before experienced a scenario where we could neither access Azure resources nor provision new ones.
- Throughout the entire incident, we worked closely with Microsoft. Their support was excellent, but the combination of Azure resource shortages, DDoS activity, and Cloudflare outages still resulted in a long recovery time.
Current status
- absentify is fully online again and all core functionality should be working as expected.
- If you continue to experience any issues, please notify us at support@absentify.com.
- We are closely monitoring all systems to ensure stability.
How we will prevent this in the future
A downtime of this length is unacceptable to us. In the coming days, we will:
- review and redesign our infrastructure and deployment strategy,
- introduce additional redundancies for critical components,
- expand our disaster recovery planning to include rare scenarios such as Azure region shortages or Cloudflare outages,
- and put safeguards in place to ensure a single configuration update cannot trigger a cascading failure.
Our goal is clear: learn everything we can from this incident and significantly increase our resilience so that an outage of this scale does not happen again.
We are truly sorry for the inconvenience caused and greatly appreciate your patience and trust.
Your absentify Team

