Is CloudMailin Down Right Now? Discover if there is an ongoing service outage.

Status page incorrectly noted a component as down whilst all checks were successful. As a result none of our alerts prompted us to take action as there was no actual underlying issue.

This incident has been resolved.

Any affected servers should have been replaced

Some customers are reporting that expired certificates are still in operation. It appears that one of the servers in the clusters is still operating with an old certificate. We're currently attempting to determine which and replace this server.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

At 12:10 UTC we deployed a change which attempted to fix an encoding problem for a small number of customers. This change appears to have resulted in attachments incorrectly being transformed into utf-8 instead of remaining in the binary character set. This change resulted in the corruption of these files as they were persisted to attachment storage. Unfortunately this has resulted in emails received in this time period having corrupt files. We're deeply sorry for this mistake on our part. The change has been rolled back and should no longer be causing an issue and we are continuing to monitor the situation. Steve - Founder, CloudMailin.com

A deployment at 12:10 UTC included code which attempted to resolve a long standing issue with encoding for a small subset of users. This fix unintentionally broke the character encoding of attachments being processed by CloudMailin and has resulted in the corruption of a number of files. We'll continue to investigate. The change has been rolled back

We're currently investigating reports of corrupted files within attachment storage.

This incident has been resolved.

The issue is currently resolved. There should not have been interruption to inbound email however, there may have been a delay to outbound message processing and the management website was un-reachable. We are still awaiting further details from our provider.

We are continuing to work on a fix for this issue.

It looks like there was an issue with the Heroku router preventing access to our 'running' application. We'll continue to investigate this and communicate with Heroku.

We're investigating an issue with our provider causing traffic not to reach out servers correctly.

This incident has been resolved.

Indexing is all caught up and the website should be showing the latest events again.

The issue has been identified and a fix is being implemented.

There is currently a delay in the statuses shown in the dashboard for both inbound and outbound emails. All in and outbound emails continue to process normally but the dashboard is not showing all of the messages at present.

This incident has been resolved.

There is currently an issue with new users authenticating with Google. The issue allows the user to login but then raises an error message once the user has authenticated preventing them taking action within the system. We're currently working on a resolution.

Things appear to be resolved. Unfortunately an issue with our upstream provider (Heroku - https://status.heroku.com/incidents/2402) was the root cause. Although not every customer was affected, unfortunately this incident caused issues with message delivery for some customers. Any messages that were not be received will have been asked to retry later, most will likely have already done so. Our next priority will be investigating our options to mitigate against issues like this in future.

Things appear to be stabilising. We're continuing to monitor and investigate

Things appear to have been resolved. We're continuing to monitor the situation and investigate.

Our upstream provider is having issues resulting in a knock on affect to some parts of our service. More details from the provider can be found: https://status.heroku.com/incidents/2402. In the meantime we're working on mitigating the impact for our customers also.

We are currently investigating this issue.

In December 2021 Several vulnerabilities were disclosed for the the Log4j logging framework for Java. Since reporting the vulnerabilities were widely reported to have been exploited in the wild. CloudMailin is not vulnerable to this attack. None of the components that CloudMailin uses are susceptible to the attack and we have tested several different scenarios to ensure that no component in our stack responds to the reported CVEs. For more information feel free to contact us.

AWS is reporting this mostly resolved. We're going to close this but continue to keep an eye on things.

We're continuing to monitor the situation. Our delivery doesn't appear to be affected but we'll keep monitoring.

We're seeing an increase in errors returned from AWS Services when we interact with the platform. At present our server's and functionality don't appear affected but we're monitoring the situation.

We've received reports that some users were unable to reach the CloudMailin servers or that Messages were delayed. The issue appears to have been resolved but we continue to investigate the causes and why some users reported issues.

We previously had two different views, fixed and fluid, the fluid view is now the default.

Due to an issue with our billing integration a small number of customers were unable to login. When logging in the users were presented with a 500 error code and were not able to view the management dashboard. None of the message delivery or receipt functionality was affected.