DRMtoday Outage History

DRMtoday is up right now

DRMtoday had 2 outages in the last 2 years totaling 23h 48m of downtime — averaging 0.1 incidents per month.

There were 2 DRMtoday outages since June 24, 2025 totaling 23h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.drmtoday.com

Notice October 20, 2025

DRMtoday Production: AWS outage in us-east-1

Detected by Pingoru
Oct 20, 2025, 10:06 AM UTC
Resolved
Oct 21, 2025, 07:27 AM UTC
Duration
21h 21m
Affected: License Delivery
Timeline · 2 updates
  1. identified Oct 20, 2025, 10:06 AM UTC

    Due to the ongoing outage of AWS in the us-east-1 region we are currently redirecting all license traffic to other regions at 7:40 UTC. While we were not experiencing errors in regards to license delivery, monitoring for the region was affected and we decided to cut off the region as a precaution. We keep monitoring the situation and will take us-east-1 into operation again once AWS resolves all issues. (This message comes delayed as the AWS outage also affected Atlassian Statuspage operations.)

  2. resolved Oct 21, 2025, 07:27 AM UTC

    AWS has reported that the issues have been resolved. We have enabled the us-east-1 region again.

Read the full incident report →

Minor June 24, 2025

DRMtoday Production: Increased error rate on License Delivery in EU regions

Detected by Pingoru
Jun 24, 2025, 07:45 PM UTC
Resolved
Jun 24, 2025, 10:12 PM UTC
Duration
2h 27m
Affected: License Delivery
Timeline · 4 updates
  1. investigating Jun 24, 2025, 07:45 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 24, 2025, 08:26 PM UTC

    Multiple faulty instances were replaced and our services no longer show excessive error rates. We are monitoring the situation.

  3. resolved Jun 24, 2025, 10:12 PM UTC

    This incident has been resolved.

  4. postmortem Jun 26, 2025, 11:23 AM UTC

    A detailed Root Cause Analysis \(RCA\) is available for this incident and can be provided upon request. To obtain a copy, please submit a ticket via our helpdesk. The report includes an overview of the incident timeline, contributing factors, and the corrective measures implemented.

Read the full incident report →