DRMtoday Outage History

DRMtoday is up right now

Pingoru has recorded 50 incidents for DRMtoday: 0 in the last 12 months and 0 in the last 90 days.

Source: status.drmtoday.com

50incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking DRMtoday in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 512 (0%)

Incidents, newest first

Notice October 20, 2025 DRMtoday Production: AWS outage in us-east-1 21h 21m License Delivery

Started Oct 20, 2025, 10:06 AM UTC· resolved Oct 21, 2025, 07:27 AM UTC

  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 2h 27m License Delivery

Started Jun 24, 2025, 07:45 PM UTC· resolved Jun 24, 2025, 10:12 PM UTC

  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 →