Incidents reported on status page for ImprovMX https://status.improvmx.com/ https://d1lppblt9t2x15.cloudfront.net/logos/3c44d4675f92e08a1a2a6a200ef64282.svg https://status.improvmx.com/ en https://status.improvmx.com/incident/564179 Wed, 14 May 2025 12:42:00 -0000 https://status.improvmx.com/incident/564179#5a46d66351fed4ea4eb2aab7e16bd30d9c4bee647109d6296f9e46df9078067c Magic-link user based logins have been fixed. https://status.improvmx.com/incident/564179 Wed, 14 May 2025 05:09:00 -0000 https://status.improvmx.com/incident/564179#bd350394244303469b60244297335455a5ceef6e8abcd03b4ff02cce46d42acb At 1AM EST we pushed a bug out that affected users trying to login to their accounts with email magic link (password login was unaffected). The fix has been identified and resolved as of 8AM EST. https://status.improvmx.com/ Fri, 02 May 2025 17:46:11 +0000 https://status.improvmx.com/#5b3ccbc4c2c80ea301941b54c796e2308a4cd335e81b6bbe6c70278fea540484 mx2.improvmx.com recovered https://status.improvmx.com/ Fri, 02 May 2025 17:34:12 +0000 https://status.improvmx.com/#5b3ccbc4c2c80ea301941b54c796e2308a4cd335e81b6bbe6c70278fea540484 mx2.improvmx.com went down https://status.improvmx.com/incident/555535 Fri, 02 May 2025 15:26:00 -0000 https://status.improvmx.com/incident/555535#5de91ca0ca0a4e036bca8d419edc31c7db3652546882bb1c7c3c08e5f0ce0341 The SPF record issue has been resolved. https://status.improvmx.com/incident/555535 Fri, 02 May 2025 15:26:00 -0000 https://status.improvmx.com/incident/555535#5de91ca0ca0a4e036bca8d419edc31c7db3652546882bb1c7c3c08e5f0ce0341 The SPF record issue has been resolved. https://status.improvmx.com/incident/555535 Fri, 02 May 2025 05:00:00 -0000 https://status.improvmx.com/incident/555535#9afcecead26e45a6e7c66592ce1b71feafbb20b0748fae59dc388c0209f94324 We pushed out a bugged SPF record change last evening (05/02/2025) at 11:30PM Eastern US Time. It was designed to improve email deliverability by reducing the number of SPF lookups, but had an issue that temporarily caused SPF lookup failures. We have pushed corrected SPF records as of 05/02/2025 11AM Eastern US Time. This will require a few hours to fully propagate. https://status.improvmx.com/incident/555535 Fri, 02 May 2025 05:00:00 -0000 https://status.improvmx.com/incident/555535#9afcecead26e45a6e7c66592ce1b71feafbb20b0748fae59dc388c0209f94324 We pushed out a bugged SPF record change last evening (05/02/2025) at 11:30PM Eastern US Time. It was designed to improve email deliverability by reducing the number of SPF lookups, but had an issue that temporarily caused SPF lookup failures. We have pushed corrected SPF records as of 05/02/2025 11AM Eastern US Time. This will require a few hours to fully propagate. https://status.improvmx.com/ Sat, 26 Apr 2025 09:04:52 +0000 https://status.improvmx.com/#b08850c848bfac0e6669ac57be6f56b470563b671c373fe145b1066a829d693a smtp.improvmx.com recovered https://status.improvmx.com/ Sat, 26 Apr 2025 08:58:57 +0000 https://status.improvmx.com/#b08850c848bfac0e6669ac57be6f56b470563b671c373fe145b1066a829d693a smtp.improvmx.com went down https://status.improvmx.com/ Sun, 16 Mar 2025 01:33:24 +0000 https://status.improvmx.com/#3e068a2313a315001c71b287e413ca75840ed93a4517efd5ee743c12ef290dc4 mx1.improvmx.com recovered https://status.improvmx.com/ Sun, 16 Mar 2025 01:17:56 +0000 https://status.improvmx.com/#3e068a2313a315001c71b287e413ca75840ed93a4517efd5ee743c12ef290dc4 mx1.improvmx.com went down https://status.improvmx.com/incident/524452 Fri, 07 Mar 2025 23:27:00 -0000 https://status.improvmx.com/incident/524452#ee31be37e882171e0cc23100b1903a4241afb5bd387b0e11bed6cdd746be624f We have moved the affected servers out of rotation, so message deliverability to microsoft & outlook addresses should be returning to normal. https://status.improvmx.com/incident/524452 Fri, 07 Mar 2025 23:27:00 -0000 https://status.improvmx.com/incident/524452#ee31be37e882171e0cc23100b1903a4241afb5bd387b0e11bed6cdd746be624f We have moved the affected servers out of rotation, so message deliverability to microsoft & outlook addresses should be returning to normal. https://status.improvmx.com/incident/524452 Fri, 07 Mar 2025 23:27:00 -0000 https://status.improvmx.com/incident/524452#ee31be37e882171e0cc23100b1903a4241afb5bd387b0e11bed6cdd746be624f We have moved the affected servers out of rotation, so message deliverability to microsoft & outlook addresses should be returning to normal. https://status.improvmx.com/incident/524452 Fri, 07 Mar 2025 17:39:00 -0000 https://status.improvmx.com/incident/524452#45e192688bcfb632d1eac3235e71de190e4092fa0631900263bdb512c7a2838d A subset of our sending servers experiencing degraded deliverability to Microsoft & Outlook mail servers. We are actively working on replacing these servers to restore high deliverability standards. https://status.improvmx.com/incident/524452 Fri, 07 Mar 2025 17:39:00 -0000 https://status.improvmx.com/incident/524452#45e192688bcfb632d1eac3235e71de190e4092fa0631900263bdb512c7a2838d A subset of our sending servers experiencing degraded deliverability to Microsoft & Outlook mail servers. We are actively working on replacing these servers to restore high deliverability standards. https://status.improvmx.com/incident/524452 Fri, 07 Mar 2025 17:39:00 -0000 https://status.improvmx.com/incident/524452#45e192688bcfb632d1eac3235e71de190e4092fa0631900263bdb512c7a2838d A subset of our sending servers experiencing degraded deliverability to Microsoft & Outlook mail servers. We are actively working on replacing these servers to restore high deliverability standards. https://status.improvmx.com/incident/514862 Tue, 18 Feb 2025 13:53:00 -0000 https://status.improvmx.com/incident/514862#cbeff20dca845b95c18d732c93869939e37e8f8d93a4a72125ac84b81289b331 PostMortem: We have identified actors spamming our load balancers with traffic which affected a portion of users. We have banned the bad actors, added enhanced logging and alerts to the affected load balancers, and will act accordingly the next time this happens. https://status.improvmx.com/incident/514862 Tue, 18 Feb 2025 12:07:00 -0000 https://status.improvmx.com/incident/514862#f48b9c69bd6be8f8aaad3417f770bc82635beeaf1e2a89215fc2e5d769bf527a Email deliverability has returned to normal for most users. We are continuing to investigate. https://status.improvmx.com/incident/390824 Fri, 28 Jun 2024 18:09:00 -0000 https://status.improvmx.com/incident/390824#7227a164ed2a8cd0847fe11d665ad25a7e22da85c1ddd3b2b9ab01025f1fd510 The queue has gone back to normal levels and we're seeing delivery times sub 10 seconds again. This is the all clear, and there will be no further updates. https://status.improvmx.com/incident/390824 Fri, 28 Jun 2024 18:09:00 -0000 https://status.improvmx.com/incident/390824#7227a164ed2a8cd0847fe11d665ad25a7e22da85c1ddd3b2b9ab01025f1fd510 The queue has gone back to normal levels and we're seeing delivery times sub 10 seconds again. This is the all clear, and there will be no further updates. https://status.improvmx.com/incident/390824 Fri, 28 Jun 2024 18:09:00 -0000 https://status.improvmx.com/incident/390824#7227a164ed2a8cd0847fe11d665ad25a7e22da85c1ddd3b2b9ab01025f1fd510 The queue has gone back to normal levels and we're seeing delivery times sub 10 seconds again. This is the all clear, and there will be no further updates. https://status.improvmx.com/incident/390824 Fri, 28 Jun 2024 17:40:00 -0000 https://status.improvmx.com/incident/390824#04129269b8b45e0953e2f01a70320d2e8fe5a45b67061cdd61df5c5dc5f39598 We have identified the root cause of the problem. OpenDNS, a DNS provider we used for the delivery part of our infrastructure, has decided to ban all French-based traffic, impacting half of our MX servers. This ban follows a court order mandated by the French sport code to crack down on services illegally streaming Formula 1. OpenDNS has decided to retaliate by completely shutting down all French traffic, as well as some areas in Portugal — without notice. We have pushed all our traffic to our alternate DNS provider for the impacted services, and email delivery is resuming normally. We'll keep this status update open and hopefully provide the all-clear in the next 30 minutes. https://status.improvmx.com/incident/390824 Fri, 28 Jun 2024 17:40:00 -0000 https://status.improvmx.com/incident/390824#04129269b8b45e0953e2f01a70320d2e8fe5a45b67061cdd61df5c5dc5f39598 We have identified the root cause of the problem. OpenDNS, a DNS provider we used for the delivery part of our infrastructure, has decided to ban all French-based traffic, impacting half of our MX servers. This ban follows a court order mandated by the French sport code to crack down on services illegally streaming Formula 1. OpenDNS has decided to retaliate by completely shutting down all French traffic, as well as some areas in Portugal — without notice. We have pushed all our traffic to our alternate DNS provider for the impacted services, and email delivery is resuming normally. We'll keep this status update open and hopefully provide the all-clear in the next 30 minutes. https://status.improvmx.com/incident/390824 Fri, 28 Jun 2024 17:40:00 -0000 https://status.improvmx.com/incident/390824#04129269b8b45e0953e2f01a70320d2e8fe5a45b67061cdd61df5c5dc5f39598 We have identified the root cause of the problem. OpenDNS, a DNS provider we used for the delivery part of our infrastructure, has decided to ban all French-based traffic, impacting half of our MX servers. This ban follows a court order mandated by the French sport code to crack down on services illegally streaming Formula 1. OpenDNS has decided to retaliate by completely shutting down all French traffic, as well as some areas in Portugal — without notice. We have pushed all our traffic to our alternate DNS provider for the impacted services, and email delivery is resuming normally. We'll keep this status update open and hopefully provide the all-clear in the next 30 minutes. https://status.improvmx.com/incident/390824 Fri, 28 Jun 2024 17:08:00 -0000 https://status.improvmx.com/incident/390824#f643a1ad1b55804e9870f845e4d3cd341022947f92c09ce56a6d9a3427490e38 We are currently seeing elevated delivery times and investigating an incident within our infrastructure. We are able to confirm that emails are queued for delivery and saved properly in our system, so no emails are lost at this point. Next update will follow in 30 minutes. https://status.improvmx.com/incident/390824 Fri, 28 Jun 2024 17:08:00 -0000 https://status.improvmx.com/incident/390824#f643a1ad1b55804e9870f845e4d3cd341022947f92c09ce56a6d9a3427490e38 We are currently seeing elevated delivery times and investigating an incident within our infrastructure. We are able to confirm that emails are queued for delivery and saved properly in our system, so no emails are lost at this point. Next update will follow in 30 minutes. https://status.improvmx.com/incident/390824 Fri, 28 Jun 2024 17:08:00 -0000 https://status.improvmx.com/incident/390824#f643a1ad1b55804e9870f845e4d3cd341022947f92c09ce56a6d9a3427490e38 We are currently seeing elevated delivery times and investigating an incident within our infrastructure. We are able to confirm that emails are queued for delivery and saved properly in our system, so no emails are lost at this point. Next update will follow in 30 minutes. https://status.improvmx.com/incident/253811 Tue, 05 Sep 2023 23:00:00 +0000 https://status.improvmx.com/incident/253811#47439a2b1bc365a849c1ce759b41fa2ea3c22dcd7c856a1d0ee0d7fca03ea832 Maintenance completed https://status.improvmx.com/incident/253811 Tue, 05 Sep 2023 21:00:00 -0000 https://status.improvmx.com/incident/253811#18fb7a659b85dc0779e9e516ca5a8c84a6757c6ec196e7a2f8124a7eed412b1e We have scheduled a maintenance window that will specifically affect the testing of email aliases. During this time, test emails won't be sent in real-time but will be dispatched as soon as maintenance concludes. Please be assured that this **will not** impact the main ImprovMX infrastructure or your regular email service. Your understanding and patience are greatly appreciated as we continue to enhance our service. Thank you for your trust in ImprovMX. https://status.improvmx.com/incident/246907 Fri, 18 Aug 2023 12:37:00 -0000 https://status.improvmx.com/incident/246907#deaba345743315ddf3c5a102be76898b3924e94e3a3f140d1e01bcefca8e3a90 #### **Post Mortem** Recently at ImprovMX, we encountered a challenge within our email forwarding service. An unexpected update to a server OS package on AWS disrupted our system's ability to automatically scale instances as demand increased. ##### **Resolution and Recovery:** Our dedicated team responded quickly with a two-step plan: 1. **Quick Fix:** We redeployed our servers with a targeted fix to the issue caused by the unexpected update, enabling us to resume our service quickly. 2. **Final Resolution:** To ensure that such an incident does not recur, we revamped our deployment strategy. Now, instead of deploying new server instances with a fresh OS, we deploy them pre-installed. This approach not only eliminates nearly all deployment issues but also boosts deployment speed, resulting in much faster auto-scaling whenever there is increased demand or usage of our service. ##### **Moving Forward:** We have learned from this incident and made significant improvements to our systems. We are more robust and resilient than ever before, and we remain committed to offering seamless service. ##### **Transparency and Trust:** At ImprovMX, we believe in honest communication and accountability. We understand the importance of trust, and we assure you that we have taken all necessary steps to prevent such an occurrence in the future. Thank you for your continued support and trust in ImprovMX. https://status.improvmx.com/incident/246907 Fri, 18 Aug 2023 12:37:00 -0000 https://status.improvmx.com/incident/246907#deaba345743315ddf3c5a102be76898b3924e94e3a3f140d1e01bcefca8e3a90 #### **Post Mortem** Recently at ImprovMX, we encountered a challenge within our email forwarding service. An unexpected update to a server OS package on AWS disrupted our system's ability to automatically scale instances as demand increased. ##### **Resolution and Recovery:** Our dedicated team responded quickly with a two-step plan: 1. **Quick Fix:** We redeployed our servers with a targeted fix to the issue caused by the unexpected update, enabling us to resume our service quickly. 2. **Final Resolution:** To ensure that such an incident does not recur, we revamped our deployment strategy. Now, instead of deploying new server instances with a fresh OS, we deploy them pre-installed. This approach not only eliminates nearly all deployment issues but also boosts deployment speed, resulting in much faster auto-scaling whenever there is increased demand or usage of our service. ##### **Moving Forward:** We have learned from this incident and made significant improvements to our systems. We are more robust and resilient than ever before, and we remain committed to offering seamless service. ##### **Transparency and Trust:** At ImprovMX, we believe in honest communication and accountability. We understand the importance of trust, and we assure you that we have taken all necessary steps to prevent such an occurrence in the future. Thank you for your continued support and trust in ImprovMX. https://status.improvmx.com/incident/246907 Fri, 18 Aug 2023 12:37:00 -0000 https://status.improvmx.com/incident/246907#deaba345743315ddf3c5a102be76898b3924e94e3a3f140d1e01bcefca8e3a90 #### **Post Mortem** Recently at ImprovMX, we encountered a challenge within our email forwarding service. An unexpected update to a server OS package on AWS disrupted our system's ability to automatically scale instances as demand increased. ##### **Resolution and Recovery:** Our dedicated team responded quickly with a two-step plan: 1. **Quick Fix:** We redeployed our servers with a targeted fix to the issue caused by the unexpected update, enabling us to resume our service quickly. 2. **Final Resolution:** To ensure that such an incident does not recur, we revamped our deployment strategy. Now, instead of deploying new server instances with a fresh OS, we deploy them pre-installed. This approach not only eliminates nearly all deployment issues but also boosts deployment speed, resulting in much faster auto-scaling whenever there is increased demand or usage of our service. ##### **Moving Forward:** We have learned from this incident and made significant improvements to our systems. We are more robust and resilient than ever before, and we remain committed to offering seamless service. ##### **Transparency and Trust:** At ImprovMX, we believe in honest communication and accountability. We understand the importance of trust, and we assure you that we have taken all necessary steps to prevent such an occurrence in the future. Thank you for your continued support and trust in ImprovMX. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 08:56:00 -0000 https://status.improvmx.com/incident/246907#a4e22b76ce4718c49a5fc5ed5314de297d3576eef1912d273d5157799546cb2e Email forwarding is now resuming. Because of the massive amount of servers re-trying sending we are forwarding slower than usual, but we are actively monitoring our system to ensure things get back to normal levels. We'll be sharing the post mortem here when it is ready. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 08:56:00 -0000 https://status.improvmx.com/incident/246907#a4e22b76ce4718c49a5fc5ed5314de297d3576eef1912d273d5157799546cb2e Email forwarding is now resuming. Because of the massive amount of servers re-trying sending we are forwarding slower than usual, but we are actively monitoring our system to ensure things get back to normal levels. We'll be sharing the post mortem here when it is ready. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 08:56:00 -0000 https://status.improvmx.com/incident/246907#a4e22b76ce4718c49a5fc5ed5314de297d3576eef1912d273d5157799546cb2e Email forwarding is now resuming. Because of the massive amount of servers re-trying sending we are forwarding slower than usual, but we are actively monitoring our system to ensure things get back to normal levels. We'll be sharing the post mortem here when it is ready. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 08:25:00 -0000 https://status.improvmx.com/incident/246907#22a02a25f4499e23bfd6215b674e2d9b08530af6157db654ba3930cf9333bd27 A fix has been implemented and we are monitoring the results. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 08:25:00 -0000 https://status.improvmx.com/incident/246907#22a02a25f4499e23bfd6215b674e2d9b08530af6157db654ba3930cf9333bd27 A fix has been implemented and we are monitoring the results. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 08:25:00 -0000 https://status.improvmx.com/incident/246907#22a02a25f4499e23bfd6215b674e2d9b08530af6157db654ba3930cf9333bd27 A fix has been implemented and we are monitoring the results. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 07:20:00 -0000 https://status.improvmx.com/incident/246907#81f88086842df77b774daceb356defd7e98cdeac79737f7e61502b3591afa1c5 The issue has been identified and we are working on fixing it. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 07:20:00 -0000 https://status.improvmx.com/incident/246907#81f88086842df77b774daceb356defd7e98cdeac79737f7e61502b3591afa1c5 The issue has been identified and we are working on fixing it. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 07:20:00 -0000 https://status.improvmx.com/incident/246907#81f88086842df77b774daceb356defd7e98cdeac79737f7e61502b3591afa1c5 The issue has been identified and we are working on fixing it. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 04:09:00 -0000 https://status.improvmx.com/incident/246907#00959f972f8f9536d5a4e2b6cd1c9add6908e19a2b3af61cc51115de10448239 We are experiencing a temporary degradation of email delivery. Our team is currently conducting a detailed investigation to identify and resolve this matter. Please be assured that this situation is being treated with the highest priority, and we're committed to restoring optimal performance as quickly as possible. **UPDATE:** The issue has been resolved, and the post mortem is now available. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 04:09:00 -0000 https://status.improvmx.com/incident/246907#00959f972f8f9536d5a4e2b6cd1c9add6908e19a2b3af61cc51115de10448239 We are experiencing a temporary degradation of email delivery. Our team is currently conducting a detailed investigation to identify and resolve this matter. Please be assured that this situation is being treated with the highest priority, and we're committed to restoring optimal performance as quickly as possible. **UPDATE:** The issue has been resolved, and the post mortem is now available. https://status.improvmx.com/incident/246907 Thu, 17 Aug 2023 04:09:00 -0000 https://status.improvmx.com/incident/246907#00959f972f8f9536d5a4e2b6cd1c9add6908e19a2b3af61cc51115de10448239 We are experiencing a temporary degradation of email delivery. Our team is currently conducting a detailed investigation to identify and resolve this matter. Please be assured that this situation is being treated with the highest priority, and we're committed to restoring optimal performance as quickly as possible. **UPDATE:** The issue has been resolved, and the post mortem is now available. https://status.improvmx.com/incident/229939 Fri, 07 Jul 2023 11:36:00 -0000 https://status.improvmx.com/incident/229939#6f9de8ebb686823f3e8ab75e7f322d0e00fdd60825758fb77b02f4fd46dbaaee We have identified the root cause of the issue and have implemented a fix. We will be monitoring this to ensure that it remains stable. You should start seeing your emails being delivered as the backlogs are gradually cleared from our infrastructure. https://status.improvmx.com/incident/229939 Fri, 07 Jul 2023 11:36:00 -0000 https://status.improvmx.com/incident/229939#6f9de8ebb686823f3e8ab75e7f322d0e00fdd60825758fb77b02f4fd46dbaaee We have identified the root cause of the issue and have implemented a fix. We will be monitoring this to ensure that it remains stable. You should start seeing your emails being delivered as the backlogs are gradually cleared from our infrastructure. https://status.improvmx.com/incident/229939 Fri, 07 Jul 2023 11:36:00 -0000 https://status.improvmx.com/incident/229939#6f9de8ebb686823f3e8ab75e7f322d0e00fdd60825758fb77b02f4fd46dbaaee We have identified the root cause of the issue and have implemented a fix. We will be monitoring this to ensure that it remains stable. You should start seeing your emails being delivered as the backlogs are gradually cleared from our infrastructure. https://status.improvmx.com/incident/229939 Fri, 07 Jul 2023 11:28:00 -0000 https://status.improvmx.com/incident/229939#bec70fde47c68a41fa879c354bdf143f7b60e1cfdf50d35c05e3f973add37fcb We are experiencing a temporary degradation of email delivery. Our team is currently conducting a detailed investigation to identify and resolve this matter. Please be assured that this situation is being treated with the highest priority, and we're committed to restoring optimal performance as quickly as possible. **UPDATE:** This has been resolved. https://status.improvmx.com/incident/229939 Fri, 07 Jul 2023 11:28:00 -0000 https://status.improvmx.com/incident/229939#bec70fde47c68a41fa879c354bdf143f7b60e1cfdf50d35c05e3f973add37fcb We are experiencing a temporary degradation of email delivery. Our team is currently conducting a detailed investigation to identify and resolve this matter. Please be assured that this situation is being treated with the highest priority, and we're committed to restoring optimal performance as quickly as possible. **UPDATE:** This has been resolved. https://status.improvmx.com/incident/229939 Fri, 07 Jul 2023 11:28:00 -0000 https://status.improvmx.com/incident/229939#bec70fde47c68a41fa879c354bdf143f7b60e1cfdf50d35c05e3f973add37fcb We are experiencing a temporary degradation of email delivery. Our team is currently conducting a detailed investigation to identify and resolve this matter. Please be assured that this situation is being treated with the highest priority, and we're committed to restoring optimal performance as quickly as possible. **UPDATE:** This has been resolved. https://status.improvmx.com/incident/138750 Thu, 24 Nov 2022 12:50:00 -0000 https://status.improvmx.com/incident/138750#cacf11538f45d80fc5f977db2f20edcc3fc0fb836997630a62e48acf12244a41 Deliverability and forwarding from Outlook have resumed as usual. We're still actively monitoring the situation to prevent any reignition, but this is the all-clear for now. We'll provide a detailed post-mortem along with action items for this incident in the coming days. https://status.improvmx.com/incident/138750 Thu, 24 Nov 2022 12:50:00 -0000 https://status.improvmx.com/incident/138750#cacf11538f45d80fc5f977db2f20edcc3fc0fb836997630a62e48acf12244a41 Deliverability and forwarding from Outlook have resumed as usual. We're still actively monitoring the situation to prevent any reignition, but this is the all-clear for now. We'll provide a detailed post-mortem along with action items for this incident in the coming days. https://status.improvmx.com/incident/138750 Thu, 24 Nov 2022 09:37:00 -0000 https://status.improvmx.com/incident/138750#1419b01cb0a9e5c86c6a7f66c976c7bd85082aeb3c4ad44c8e477fec808db21b We've been able to manage the issue on the human level, with the abusive customer removing approx 800 DNS entries from their setup to avoid ImprovMX being the destination server of bounce reports. We are already seeing connections dropping and a more manageable environment overall. We will continue monitoring in the next few hours, but emails should gradually get more and more accepted on the first try. https://status.improvmx.com/incident/138750 Thu, 24 Nov 2022 09:37:00 -0000 https://status.improvmx.com/incident/138750#1419b01cb0a9e5c86c6a7f66c976c7bd85082aeb3c4ad44c8e477fec808db21b We've been able to manage the issue on the human level, with the abusive customer removing approx 800 DNS entries from their setup to avoid ImprovMX being the destination server of bounce reports. We are already seeing connections dropping and a more manageable environment overall. We will continue monitoring in the next few hours, but emails should gradually get more and more accepted on the first try. https://status.improvmx.com/incident/138750 Thu, 24 Nov 2022 08:11:00 -0000 https://status.improvmx.com/incident/138750#0a9b5c5024fd3f4aa5b164aaf27626f3dd5efc8b97083f66996f52f3cb2013ca We're currently battling an attack on our infrastructure which is leveraging Microsoft email servers (specifically Outlook) to send up to 100k connections per minute our way. This means that emails originating from Microsoft servers and trying to hit a redirection alias created on ImprovMX are soft-bouncing. Outbound traffic to outlook isn't affected, nor is any other email provider. Unfortunately, there is no quick way for us to block the incoming traffic, but we've identified the cause of the problem and are working on multiple levels to get this resolved as soon as possible. 1) Human - if the ESP block the bad actor, the problem is solved in a minute. We've been very insistent, but if it doesn't work, we'll start legal action to get movement 2) At the Microsoft level. We've lodged complaints through several channels so that they stop sending all the bounce reports back for that specific IP range. Unfortunately, this is usually very slow and doesn't get solved quickly. 3) At our technical level - We've increased AWS instances to the maximum we can afford (we're 10xing costs for this month - erasing all profits basically). It's like increasing the size of a leaky bucket, but it works temporarily. https://status.improvmx.com/incident/138750 Thu, 24 Nov 2022 08:11:00 -0000 https://status.improvmx.com/incident/138750#0a9b5c5024fd3f4aa5b164aaf27626f3dd5efc8b97083f66996f52f3cb2013ca We're currently battling an attack on our infrastructure which is leveraging Microsoft email servers (specifically Outlook) to send up to 100k connections per minute our way. This means that emails originating from Microsoft servers and trying to hit a redirection alias created on ImprovMX are soft-bouncing. Outbound traffic to outlook isn't affected, nor is any other email provider. Unfortunately, there is no quick way for us to block the incoming traffic, but we've identified the cause of the problem and are working on multiple levels to get this resolved as soon as possible. 1) Human - if the ESP block the bad actor, the problem is solved in a minute. We've been very insistent, but if it doesn't work, we'll start legal action to get movement 2) At the Microsoft level. We've lodged complaints through several channels so that they stop sending all the bounce reports back for that specific IP range. Unfortunately, this is usually very slow and doesn't get solved quickly. 3) At our technical level - We've increased AWS instances to the maximum we can afford (we're 10xing costs for this month - erasing all profits basically). It's like increasing the size of a leaky bucket, but it works temporarily. https://status.improvmx.com/incident/90811 Fri, 27 May 2022 09:58:00 -0000 https://status.improvmx.com/incident/90811#a14aa2884f52d8d6033afcc174047627ee2b1da156955722c87688e9e3e0cd8e We've identified the issue and it's been automatically resolved by our redundancy plan. There will be no further updates. https://status.improvmx.com/incident/90811 Fri, 27 May 2022 09:58:00 -0000 https://status.improvmx.com/incident/90811#a14aa2884f52d8d6033afcc174047627ee2b1da156955722c87688e9e3e0cd8e We've identified the issue and it's been automatically resolved by our redundancy plan. There will be no further updates. https://status.improvmx.com/incident/90811 Fri, 27 May 2022 09:51:00 -0000 https://status.improvmx.com/incident/90811#e825c54cb63a125c5b277ee8222727a13bbce2fe7e2fd6d354ee376d4ddfd443 The dashboard is currently unavailable for all users. Email forwarding isn't impacted. We will update in 15 minutes with more information. https://status.improvmx.com/incident/90811 Fri, 27 May 2022 09:51:00 -0000 https://status.improvmx.com/incident/90811#e825c54cb63a125c5b277ee8222727a13bbce2fe7e2fd6d354ee376d4ddfd443 The dashboard is currently unavailable for all users. Email forwarding isn't impacted. We will update in 15 minutes with more information. https://status.improvmx.com/incident/85352 Mon, 02 May 2022 08:07:00 -0000 https://status.improvmx.com/incident/85352#ab96486d55d140f598a7460e4c630ef0cfe8bebfb47a9f68845891f52312439a Netlify, our hosting provider for the marketing site and app.improvmx.com is currently experiencing an outage. https://www.netlifystatus.com/incidents/m1d4vwctxsrs?u=vy7qn93y8qbp https://status.improvmx.com/incident/85352 Mon, 02 May 2022 08:07:00 -0000 https://status.improvmx.com/incident/85352#ab96486d55d140f598a7460e4c630ef0cfe8bebfb47a9f68845891f52312439a Netlify, our hosting provider for the marketing site and app.improvmx.com is currently experiencing an outage. https://www.netlifystatus.com/incidents/m1d4vwctxsrs?u=vy7qn93y8qbp https://status.improvmx.com/incident/78009 Fri, 25 Mar 2022 16:12:00 -0000 https://status.improvmx.com/incident/78009#bef8a70e2a2de8585012e939132c57649c5f125a9cd0dc268676756526a8ce0e We have managed to identify and exclude the range of IP that was flagged at Gmail. We're able to confirm that we're not seeing soft/hard bounce issues, but will continue to monitor this throughout the rest of the day. https://status.improvmx.com/incident/78009 Fri, 25 Mar 2022 16:12:00 -0000 https://status.improvmx.com/incident/78009#bef8a70e2a2de8585012e939132c57649c5f125a9cd0dc268676756526a8ce0e We have managed to identify and exclude the range of IP that was flagged at Gmail. We're able to confirm that we're not seeing soft/hard bounce issues, but will continue to monitor this throughout the rest of the day. https://status.improvmx.com/incident/78009 Fri, 25 Mar 2022 16:12:00 -0000 https://status.improvmx.com/incident/78009#bef8a70e2a2de8585012e939132c57649c5f125a9cd0dc268676756526a8ce0e We have managed to identify and exclude the range of IP that was flagged at Gmail. We're able to confirm that we're not seeing soft/hard bounce issues, but will continue to monitor this throughout the rest of the day. https://status.improvmx.com/incident/78009 Fri, 25 Mar 2022 13:55:00 -0000 https://status.improvmx.com/incident/78009#ed299d9df2da3b1d685d34e6e202fd455f3fd1b1aeab42c776b8b61795c41cd8 We're currently seeing elevated soft/hard bounces to redirection email addresses set on Gmail. This is sparse and seems to affect only a portion of our IP range. From our initial investigation, it shows that in the small subset of messages that are hard-bounced, senders are still able to receive a bounce notification back. We'll update the report once we know more. https://status.improvmx.com/incident/78009 Fri, 25 Mar 2022 13:55:00 -0000 https://status.improvmx.com/incident/78009#ed299d9df2da3b1d685d34e6e202fd455f3fd1b1aeab42c776b8b61795c41cd8 We're currently seeing elevated soft/hard bounces to redirection email addresses set on Gmail. This is sparse and seems to affect only a portion of our IP range. From our initial investigation, it shows that in the small subset of messages that are hard-bounced, senders are still able to receive a bounce notification back. We'll update the report once we know more. https://status.improvmx.com/incident/78009 Fri, 25 Mar 2022 13:55:00 -0000 https://status.improvmx.com/incident/78009#ed299d9df2da3b1d685d34e6e202fd455f3fd1b1aeab42c776b8b61795c41cd8 We're currently seeing elevated soft/hard bounces to redirection email addresses set on Gmail. This is sparse and seems to affect only a portion of our IP range. From our initial investigation, it shows that in the small subset of messages that are hard-bounced, senders are still able to receive a bounce notification back. We'll update the report once we know more.