pingoru pingoru Aptoma had 13 outages in the last 2 years totaling 17h 0m of downtime, averaging 0.5 incidents per month.
There were 13 Aptoma outages since December 4, 2024 totaling 17h 0m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We are investigating an issue login in to DrEdition via SSO providers.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are monitoring reports of intermittent errors on DrPublish.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The incident was caused by an old version of DrPublish unintentionally being released at 13:39. At 13:44 normal operations were restored on the most recent DrPublish version. We have since removed the cause of the incident to avoid incidents from the same cause in the future.
On 29 April at 12:59 CEST, a DrPublish deployment introduced a regression that disrupted article propagation to downstream print workflows. The issue was identified and the deployment was rolled back at 13:47 CEST. Normal service was restored within minutes. Total duration: approximately 48 minutes. We apologise for the disruption this caused, particularly for customers with tight print deadlines during this window. We are reviewing our deployment and monitoring procedures to reduce both the likelihood and detection time of similar issues in the future.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Problems occurred between 13:46 and 13:59 today. We have implemented a fix. Everything should now work as expected. Please report to us per [email protected] if it is not.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
There is currently a significant outage at AWS in the region us-east-1. This is not currently affecting our services, but we are actively monitoring the situation. Should the nature of this outage change for the worse, or start to disrupt our services, we will provide updates here.
This incident has been resolved.
AWS had internal DNS issues in their Virginia-location \(us-east-1\). This region is the hub for the majority of AWS’s global services, such as the ones that handle CDNs, authentication, permissions, etc. Local services in Virginia were impacted severely, and global services were degraded by this outage. Aptoma services were not directly impacted by this outage. We had minor disruptions to internal workflows and some telemetry, but nothing that ended up being noticeable by users. We actively monitor the health of our service providers and are ready to triage our own services if upstream issues affect us. We have redundancy plans in place for outages affecting our own primary location.
We are currently investigating this issue.
We're seeing intermittent failures across multiple Google services, as well as the CloudFlare network.
The following components are affected by the ongoing outages on Google services: - Login in DrEdition and DrPublish wherever Google SSO is used. - The preview of Front Pages in DrEdition. Publishing Front Pages is unaffected.
Google services appear to be stabilizing. Some integrations still have longer request times than normal. We are continuing to monitor.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue with front pages on Firefox. For now we recommend using Chrome instead.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are monitoring an issue with saving in DrPublish. We believe the underlying issue to be solved.
An update to encoding of article data in DrPublish was deployed at 13:30CET, which blocked saving and publishing of articles. We were became aware of this issue at 13:38, and the problematic update had been rolled back by 13:44. This affected saving and publishing articles from the DrPublish editor. Article imports, including pushes from external CMS and automatic feed imports were unaffected by this issue. Availability of article data in DrPublish APIs was also not affected.
We are currently investigating an issue. We are not yet certain of the specific implications of this issue, and consequently you may recieve this report without being affected. We will return with more specific information as soon as we know more. Please contact [email protected] if you have any questions.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We believe the issue is corrected. Monitoring.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The problem was due to an intermittent network issue between the Front Pages realtime service and a cache service. We have redundancies, but we will be looking into whether adding additional redundancies can mitigate issues of a similar nature in the future. Our internal postmortem process will conclude this. We are sorry for the problems caused.
At 12:30 PM we had a brief outage on the Asset API, lasting for approx. 5 minutes. This incident has since been resolved and we continue to monitor the service.