Short.cm had 15 outages in the last 2 years totaling 36h 34m of downtime — averaging 0.6 incidents per month.
There were 15 Short.cm outages since October 8, 2025 totaling 36h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
This incident has been resolved. Investigating - We are currently investigating this issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
This incident has been resolved.
This incident has been resolved.
We are currently monitoring this issue.
We are currently investigating this issue.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
AWS Global Accelerator rerouted all redirects to EU and Australia regions. All links work, but a bit slower (extra 500ms latency)
Our hosting provider AWS had a major incident with DynamoDB in their primary region, which affected other their services (almost every AWS service was affected). What was affected: * Short links are stored in DynamoDB, so our service had full downtime * We use Intercom for customer support, which is hosted by AWS and it had full downtime, so our support engineers weren’t able to help you * We use Atlassian Statuspage for this status page, they had full downtime, so we could not update status page to mention this incident * We were locked out of our AWS account and were not able to make any changes Within 24 hours we will release our plan how we can prevent such widespread incident from happening
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.