Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Magemojo outage history

    49 recorded Magemojo incidents since July 2020, with official updates, affected components, duration and resolution information.

    Back to current status

    Service Alert – Email Service Inoperable for Stratus Customers (Updated July 8)

    Started July 9, 2025 at 2:00 PM UTC · 6h 6m

    OutageMajor incident
    Affected components
    Webscale STRATUS - SydneyWebscale STRATUS - FrankfurtWebscale STRATUS - Northern Virginia
    1. July 9, 2025 at 2:00 PM UTCidentified

      Dear Customer, Since approximately 6:43 AM MT on Monday, July 7, email service has been inoperable for a subset of customers on our Stratus platform. Our engineering team has traced the root cause to an underlying AWS infrastructure issue and is collaborating closely with AWS engineers to implement a fix. Current impact Email sending and receiving is currently inoperable for Stratus customers. All other customer groups, remain unaffected. All other Webscale services continue to operate normally. Resolution timeline We anticipate full restoration of email service by 12:00 PM MT tomorrow (Wednesday, July 9). We will send an additional update no later than that time—or sooner if service is restored earlier. We apologize for the disruption and appreciate your patience. If you have urgent concerns before service is restored, please contact us at [email protected]. Thank you for your understanding,

    2. July 9, 2025 at 8:06 PM UTCresolved

      Dear Customer, We’re pleased to report that AWS has resolved the underlying infrastructure issue, and email service for all Stratus customers was fully restored at approximately 2:02 PM MT today. What this means for you Email sending and receiving are now operating normally. No action is required on your end, though we recommend sending a quick test message to confirm everything looks good. Next steps Ongoing monitoring: Our team will closely monitor performance over the next 24 hours to ensure stability. Root Cause Analysis (RCA): We are preparing a detailed RCA that outlines exactly what happened and why. Future mitigation: The RCA will include concrete steps we’re taking—such as platform redundancy and enhanced alerting—to prevent similar incidents. Follow-up report: We will share the RCA and mitigation plan with all affected customers once it is finalized. If you notice any lingering issues, please contact us at [email protected], and we’ll address them immediately. Thank you for your patience while we worked with AWS to bring service back online. ================================================================================================== Dear Customer, This notice provides an update to the advisory sent last night. Current status: Email sending and receiving remain inoperable for Stratus customers only. All other customer groups are unaffected, and all other Webscale services are operating normally. Root cause: An AWS infrastructure fault first detected at 6:43 AM MT on Monday, July 7. Our response: While AWS works on remediation, we are moving Stratus email traffic from AWS to SendGridto accelerate recovery and add redundancy. Updated resolution estimate We now expect full restoration of email service by 5:00 PM MT today (Tuesday, July 8). We will send a confirmation once service is verified—or sooner if conditions change. Thank you for your continued patience. For urgent questions before service is restored, please email [email protected].

    Emergency Maintenance on 1 dev/staging node in USEast (b4faf81)

    Started April 28, 2024 at 10:27 AM UTC · 8h 2m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. April 28, 2024 at 10:27 AM UTCinvestigating

      We are currently investigating this issue.

    2. April 28, 2024 at 10:45 AM UTCidentified

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

    3. April 28, 2024 at 3:34 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. April 28, 2024 at 6:30 PM UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 dev/staging node in USEast (6154b7)

    Started February 26, 2024 at 7:12 PM UTC · 17h 43m

    Pending
    Affected components
    Webscale STRATUS - Northern Virginia
    1. February 26, 2024 at 7:12 PM UTCidentified

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

    2. February 27, 2024 at 12:55 PM UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (eb34d3)

    Started November 13, 2023 at 2:49 PM UTC · 3h 22m

    Pending
    Affected components
    Webscale STRATUS - Northern Virginia
    1. November 13, 2023 at 2:49 PM UTCidentified

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

    2. November 13, 2023 at 6:12 PM UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (eb34d3)

    Started October 30, 2023 at 5:08 PM UTC · 3h 30m

    Pending
    Affected components
    Webscale STRATUS - Northern Virginia
    1. October 30, 2023 at 5:08 PM UTCinvestigating

      We are currently investigating this issue.

    2. October 30, 2023 at 5:55 PM UTCidentified

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

    3. October 30, 2023 at 8:38 PM UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (9c912b)

    Started September 26, 2023 at 5:01 PM UTC · 3h 5m

    Pending
    Affected components
    Webscale STRATUS - Northern Virginia
    1. September 26, 2023 at 5:01 PM UTCidentified

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

    2. September 26, 2023 at 8:06 PM UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (d79319)

    Started July 13, 2023 at 6:42 PM UTC · 17h 31m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. July 13, 2023 at 6:42 PM UTCinvestigating

      We are currently investigating this issue.

    2. July 13, 2023 at 9:58 PM UTCidentified

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

    3. July 14, 2023 at 3:28 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. July 14, 2023 at 12:13 PM UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (2a0fef)

    Started July 11, 2023 at 12:02 PM UTC · 7h 6m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. July 11, 2023 at 1:33 PM UTCidentified

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

    2. July 11, 2023 at 2:55 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. July 11, 2023 at 7:08 PM UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (fd4119)

    Started May 22, 2023 at 3:44 PM UTC · 18h 3m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. May 22, 2023 at 3:44 PM UTCinvestigating

      We are currently investigating this issue.

    2. May 22, 2023 at 7:49 PM UTCidentified

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

    3. May 23, 2023 at 7:37 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. May 23, 2023 at 9:46 AM UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (d1cfc97b) dev/staging type

    Started January 4, 2023 at 1:34 PM UTC · 34m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. January 4, 2023 at 1:34 PM UTCinvestigating

      We are currently investigating this issue.

    2. January 4, 2023 at 1:52 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. January 4, 2023 at 2:08 PM UTCresolved

      This incident has been resolved.

    4. January 4, 2023 at 2:09 PM UTCpostmortem

      Our upstream provider AWS Services notified us that between Wed, 4 Jan 2023 13:17:18 GMT and Wed, 4 Jan 2023 14:03:20 GMT, a small number of EC2 instances were unavailable in the us-east-1 region. The issue has been resolved and the service is operating normally.

    Emergency Maintenance on 1 node in USEast (d1cfc97b) dev/staging type

    Started December 5, 2022 at 8:19 PM UTC · 33m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. December 5, 2022 at 8:19 PM UTCinvestigating

      We are currently investigating this issue.

    2. December 5, 2022 at 8:52 PM UTCresolved

      This incident has been resolved.

    3. December 5, 2022 at 8:57 PM UTCpostmortem

      Our upstream provider AWS informed us that between Mon, 5 Dec 2022 20:22:19 GMT and Mon, 5 Dec 2022 20:55:54 GMT, a small number of EC2 instances were unavailable in the us-east-1 region. The issue has been resolved, and the service is operating normally.

    Frankfurt Node under Emergency maintenance

    Started November 24, 2022 at 2:40 AM UTC · 2h 2m

    IssuesMinor incident
    Affected components
    Webscale STRATUS - Frankfurt
    1. November 24, 2022 at 2:40 AM UTCidentified

      Frankfurt Node under Emergency maintenance due to degradation of the underlying hardware

    2. November 24, 2022 at 4:42 AM UTCresolved

      This incident has been resolved

    Emergency Maintenance on 1 node in USEast (dc298c5)

    Started November 17, 2022 at 7:44 PM UTC · 47m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. November 17, 2022 at 7:44 PM UTCinvestigating

      We are currently investigating this issue.

    2. November 17, 2022 at 8:28 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. November 17, 2022 at 8:31 PM UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (53d61e5)

    Started August 27, 2022 at 6:48 PM UTC · 1h 18m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. August 27, 2022 at 6:48 PM UTCinvestigating

      We are currently investigating this issue.

    2. August 27, 2022 at 7:19 PM UTCidentified

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

    3. August 27, 2022 at 8:05 PM UTCresolved

      This incident has been resolved.

    4. August 29, 2022 at 4:57 PM UTCpostmortem

      The Root cause of this incident for a small subset of stores was due to a bad/degraded AWS EC2 instance. Due to this degradation we have activated HA failover mechanism and balanced stores on new hardware nodes from our fleet. For real time HA recovery additional High Availability Strategies are available: [https://magemojo.com/kb/best-practices/high-availability-strategies/](https://magemojo.com/kb/best-practices/high-availability-strategies/) Please feel free to contact support if you have any questions.

    Emergency Maintenance on 1 node in USEast (4b69ad1)

    Started August 13, 2022 at 11:41 AM UTC · 2h 52m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. August 13, 2022 at 11:41 AM UTCinvestigating

      We are currently investigating this issue.

    2. August 13, 2022 at 12:56 PM UTCidentified

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

    3. August 13, 2022 at 1:44 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. August 13, 2022 at 2:34 PM UTCresolved

      This incident has been resolved.

    5. August 15, 2022 at 11:55 AM UTCpostmortem

      The Root cause of this incident for a small subset of stores was due to a bad/degraded AWS EC2 instance. Due to this degradation we have activated HA failover mechanism and balanced stores on new hardware nodes from our fleet. Please feel free to contact support if you have any questions.

    Emergency Maintenance on 1 node in USEast (03594a)

    Started August 7, 2022 at 12:03 PM UTC · 3h 57m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. August 7, 2022 at 12:03 PM UTCidentified

      AWS has informed us about the detected degradation of the underlying hardware hosting your Amazon EC2 instance associated with this instance. Our Engineers are working on recovery and failover to new hardware.

    2. August 7, 2022 at 1:44 PM UTCidentified

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

    3. August 7, 2022 at 2:42 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. August 7, 2022 at 3:39 PM UTCmonitoring

      We are continuing to monitor for any further issues.

    5. August 7, 2022 at 4:00 PM UTCresolved

      This incident has been resolved.

    6. August 9, 2022 at 8:09 PM UTCpostmortem

      The Root cause of this incident for a small subset of stores was due to a bad/degraded AWS EC2 instance. Due to this degradation we have activated HA failover mechanism and balanced stores on new hardware nodes from our fleet. Please feel free to contact support if you have any questions.

    Stratus Panel down due to a 3rd party issue

    Started June 8, 2022 at 6:46 PM UTC · 40m

    Pending
    Affected components
    Webscale STRATUS - SydneyWebscale STRATUS - FrankfurtWebscale STRATUS - Northern Virginia
    1. June 8, 2022 at 6:46 PM UTCidentified

      Webscale Stratus panel is currently affected by an issue related to a 3rd party outage. Site up-time is not affected by this issue.

    2. June 8, 2022 at 7:25 PM UTCresolved

      This incident has been resolved.

    Partial Outage in Sydney Region (94aef90)

    Started May 4, 2022 at 1:14 PM UTC · 1h 13m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Sydney
    1. May 4, 2022 at 1:14 PM UTCinvestigating

      We are currently investigating this issue.

    2. May 4, 2022 at 1:45 PM UTCidentified

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

    3. May 4, 2022 at 2:01 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. May 4, 2022 at 2:28 PM UTCresolved

      This incident has been resolved.

    5. May 4, 2022 at 2:28 PM UTCpostmortem

      We have been notified that one of the hardware nodes has detected degradation of the underlying hardware. To resolve issue we have applied our built-in High Availability failover mechanism \([https://magemojo.com/kb/best-practices/high-availability-strategies/#what-is-high-availability](https://magemojo.com/kb/best-practices/high-availability-strategies/#what-is-high-availability)\).

    Emergency Maintenance on 1 node in USEast (4119)

    Started February 26, 2022 at 9:20 AM UTC · 1h 14m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. February 26, 2022 at 9:20 AM UTCinvestigating

      We are currently investigating this issue.

    2. February 26, 2022 at 9:44 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. February 26, 2022 at 10:34 AM UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast

    Started December 31, 2021 at 2:50 AM UTC · 3h 49m

    OutageMajor incident
    Affected components
    Webscale STRATUS - Northern Virginia
    1. December 31, 2021 at 2:50 AM UTCidentified

      Emergency Maintenance is being performed on one node in USEast.

    2. December 31, 2021 at 6:39 AM UTCresolved

      This incident has been resolved.

    3. January 5, 2022 at 5:58 PM UTCpostmortem

      The Root cause of this intermittent response for a small subset of stores was due to a bad/degraded AWS EC2 instance. Due to this degradation instance was rebooted in hope of recovery and urgent migration to a fresh node was initiated. Please feel free to contact support if you have any questions.