Heysender Outage History

Type: Incident Duration: 4 hours and 42 minutes Affected Components: Outgoing SMTP, API Aug 10, 10:13:00 GMT+0 - Investigating - We're currently experiencing issues sending e-mails from our system. We're investigating the cause. Aug 10, 14:55:12 GMT+0 - Resolved - Due to an issue with our hosting provider Heysender could not send email for a few hours this afternoon. The issue has been solved and we're monitoring the state of the service for the rest of the day.

Type: Incident Duration: 11 minutes Affected Components: Incoming SMTP, Outgoing SMTP, App, API Dec 11, 11:54:20 GMT+0 - Investigating - All systems are down. We are currently investigating this incident. Dec 11, 12:05:39 GMT+0 - Resolved - We're back online and all systems are operational. Many apologies for the issues - we're working closely with our service provider to avoid similar incidents going forward.

Type: Incident Duration: 9 hours and 46 minutes Affected Components: Incoming SMTP, Outgoing SMTP, API, App Dec 4, 13:09:17 GMT+0 - Resolved - This incident has been resolved. Dec 4, 06:11:19 GMT+0 - Resolved - All systems seem to be online again. We're keeping an eye on things but from here it seems to be a network issue at our hosting supplier resulting in about 10 minutes of downtime. We will update when we know more. Dec 4, 13:11:11 GMT+0 - Postmortem - The issue was caused by a firewall issue at our hosting provider. It was solved with 10 minutes of total downtime to the system. Dec 4, 06:01:33 GMT+0 - Investigating - We're currently investigating what seems to be an issue connecting to smtp.heysender.com. New status within 30 minutes. Dec 4, 06:05:04 GMT+0 - Investigating - The issue also affects the app, API and outgoing SMTP. We're still investigating.

Type: Incident Duration: 21 hours and 6 minutes Affected Components: API, App Oct 2, 12:14:00 GMT+0 - Identified - Once again our hosting provider has issues with S3 hosting. We are making changes in order to handle the issue but mail queues should be up and running again soon. New update in 20 minutes. Oct 2, 12:40:00 GMT+0 - Monitoring - We're sending emails again but we're not storing HTML and text content or attachments. We'll update when this changes. Oct 3, 09:20:00 GMT+0 - Resolved - All services are back to normal. We are in touch with our provider about how to solve this issue for good.

Type: Maintenance Duration: 2 hours Affected Components: API, Incoming SMTP, App, Outgoing SMTP Jan 15, 19:45:00 GMT+0 - Identified - We will be updating a central piece of SMTP software in Heysender. This will result in a downtime on the incoming SMTP service lasting a few minutes where the SMTP service will not respond to connection requests. Afterwards, the incoming SMTP service will be running but all outgoing e-mail will be caught and saved for later delivery while we update the software. The date and time of the update is: **Tuesday 21st of January 2025 from 20:45 CET to 22:45 CET** We expect the entire process to take 1-2 hours from start to end. For the first few minutes no incoming SMTP requests will succeed and afterwards there will be a delay of up to 2 hours on outgoing e-mail. If you have any questions regarding the update please do not hesitate to get in touch with support. Jan 15, 21:45:00 GMT+0 - Completed - Maintenance has completed successfully.

Type: Incident Duration: 12 minutes Affected Components: API, Incoming SMTP, App, Outgoing SMTP Jan 7, 13:51:00 GMT+0 - Monitoring - We are currently experiencing e-mails with logging in Heysender. Our hosting partner is updating a key part of their infrastructure which we use to store log files making us unable to handle the logs. We have made a change to the system so we bypass logging of text and HTML versions which solves the issue for now. We will update when all is back to normal. Jan 7, 14:03:00 GMT+0 - Resolved - This incident has been resolved.

Type: Incident Duration: 15 days, 21 hours and 25 minutes Dec 19, 12:28:00 GMT+0 - Resolved - This incident has been resolved. Dec 19, 12:03:00 GMT+0 - Monitoring - Due to a change in the service some webhooks changed format. This has resulted in issues with integrations parsing the webhooks. The change has been rolled back and we're working on fixing the format before we retry the webhooks with the right format. If your service responds with 200 OK when a webhook is received we will not retry the webhook. Get in touch with support if you need assistance receiving the webhooks again.