Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Cronologia delle interruzioni di Magemojo

    49 Magemojo incidents · luglio 2020 — official updates, affected components, duration and resolution details.

    Torna allo stato attuale

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

    Inizio 9 luglio 2025 alle ore 14:00 UTC · 6h 6m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - SydneyWebscale STRATUS - FrankfurtWebscale STRATUS - Northern Virginia
    1. 9 luglio 2025 alle ore 14:00 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. 9 luglio 2025 alle ore 20:06 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)

    Inizio 28 aprile 2024 alle ore 10:27 UTC · 8h 2m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 28 aprile 2024 alle ore 10:27 UTCinvestigating

      We are currently investigating this issue.

    2. 28 aprile 2024 alle ore 10:45 UTCidentified

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

    3. 28 aprile 2024 alle ore 15:34 UTCmonitoring

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

    4. 28 aprile 2024 alle ore 18:30 UTCresolved

      This incident has been resolved.

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

    Inizio 26 febbraio 2024 alle ore 19:12 UTC · 17h 43m

    Pending
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 26 febbraio 2024 alle ore 19:12 UTCidentified

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

    2. 27 febbraio 2024 alle ore 12:55 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (eb34d3)

    Inizio 13 novembre 2023 alle ore 14:49 UTC · 3h 22m

    Pending
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 13 novembre 2023 alle ore 14:49 UTCidentified

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

    2. 13 novembre 2023 alle ore 18:12 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (eb34d3)

    Inizio 30 ottobre 2023 alle ore 17:08 UTC · 3h 30m

    Pending
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 30 ottobre 2023 alle ore 17:08 UTCinvestigating

      We are currently investigating this issue.

    2. 30 ottobre 2023 alle ore 17:55 UTCidentified

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

    3. 30 ottobre 2023 alle ore 20:38 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (9c912b)

    Inizio 26 settembre 2023 alle ore 17:01 UTC · 3h 5m

    Pending
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 26 settembre 2023 alle ore 17:01 UTCidentified

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

    2. 26 settembre 2023 alle ore 20:06 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (d79319)

    Inizio 13 luglio 2023 alle ore 18:42 UTC · 17h 31m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 13 luglio 2023 alle ore 18:42 UTCinvestigating

      We are currently investigating this issue.

    2. 13 luglio 2023 alle ore 21:58 UTCidentified

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

    3. 14 luglio 2023 alle ore 03:28 UTCmonitoring

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

    4. 14 luglio 2023 alle ore 12:13 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (2a0fef)

    Inizio 11 luglio 2023 alle ore 12:02 UTC · 7h 6m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 11 luglio 2023 alle ore 13:33 UTCidentified

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

    2. 11 luglio 2023 alle ore 14:55 UTCmonitoring

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

    3. 11 luglio 2023 alle ore 19:08 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (fd4119)

    Inizio 22 maggio 2023 alle ore 15:44 UTC · 18h 3m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 22 maggio 2023 alle ore 15:44 UTCinvestigating

      We are currently investigating this issue.

    2. 22 maggio 2023 alle ore 19:49 UTCidentified

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

    3. 23 maggio 2023 alle ore 07:37 UTCmonitoring

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

    4. 23 maggio 2023 alle ore 09:46 UTCresolved

      This incident has been resolved.

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

    Inizio 4 gennaio 2023 alle ore 13:34 UTC · 34m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 4 gennaio 2023 alle ore 13:34 UTCinvestigating

      We are currently investigating this issue.

    2. 4 gennaio 2023 alle ore 13:52 UTCmonitoring

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

    3. 4 gennaio 2023 alle ore 14:08 UTCresolved

      This incident has been resolved.

    4. 4 gennaio 2023 alle ore 14:09 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

    Inizio 5 dicembre 2022 alle ore 20:19 UTC · 33m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 5 dicembre 2022 alle ore 20:19 UTCinvestigating

      We are currently investigating this issue.

    2. 5 dicembre 2022 alle ore 20:52 UTCresolved

      This incident has been resolved.

    3. 5 dicembre 2022 alle ore 20:57 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

    Inizio 24 novembre 2022 alle ore 02:40 UTC · 2h 2m

    IssuesIncidente minore
    Componenti interessati
    Webscale STRATUS - Frankfurt
    1. 24 novembre 2022 alle ore 02:40 UTCidentified

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

    2. 24 novembre 2022 alle ore 04:42 UTCresolved

      This incident has been resolved

    Emergency Maintenance on 1 node in USEast (dc298c5)

    Inizio 17 novembre 2022 alle ore 19:44 UTC · 47m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 17 novembre 2022 alle ore 19:44 UTCinvestigating

      We are currently investigating this issue.

    2. 17 novembre 2022 alle ore 20:28 UTCmonitoring

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

    3. 17 novembre 2022 alle ore 20:31 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (53d61e5)

    Inizio 27 agosto 2022 alle ore 18:48 UTC · 1h 18m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 27 agosto 2022 alle ore 18:48 UTCinvestigating

      We are currently investigating this issue.

    2. 27 agosto 2022 alle ore 19:19 UTCidentified

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

    3. 27 agosto 2022 alle ore 20:05 UTCresolved

      This incident has been resolved.

    4. 29 agosto 2022 alle ore 16:57 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)

    Inizio 13 agosto 2022 alle ore 11:41 UTC · 2h 52m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 13 agosto 2022 alle ore 11:41 UTCinvestigating

      We are currently investigating this issue.

    2. 13 agosto 2022 alle ore 12:56 UTCidentified

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

    3. 13 agosto 2022 alle ore 13:44 UTCmonitoring

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

    4. 13 agosto 2022 alle ore 14:34 UTCresolved

      This incident has been resolved.

    5. 15 agosto 2022 alle ore 11:55 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)

    Inizio 7 agosto 2022 alle ore 12:03 UTC · 3h 57m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 7 agosto 2022 alle ore 12:03 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. 7 agosto 2022 alle ore 13:44 UTCidentified

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

    3. 7 agosto 2022 alle ore 14:42 UTCmonitoring

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

    4. 7 agosto 2022 alle ore 15:39 UTCmonitoring

      We are continuing to monitor for any further issues.

    5. 7 agosto 2022 alle ore 16:00 UTCresolved

      This incident has been resolved.

    6. 9 agosto 2022 alle ore 20:09 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

    Inizio 8 giugno 2022 alle ore 18:46 UTC · 40m

    Pending
    Componenti interessati
    Webscale STRATUS - SydneyWebscale STRATUS - FrankfurtWebscale STRATUS - Northern Virginia
    1. 8 giugno 2022 alle ore 18:46 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. 8 giugno 2022 alle ore 19:25 UTCresolved

      This incident has been resolved.

    Partial Outage in Sydney Region (94aef90)

    Inizio 4 maggio 2022 alle ore 13:14 UTC · 1h 13m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Sydney
    1. 4 maggio 2022 alle ore 13:14 UTCinvestigating

      We are currently investigating this issue.

    2. 4 maggio 2022 alle ore 13:45 UTCidentified

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

    3. 4 maggio 2022 alle ore 14:01 UTCmonitoring

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

    4. 4 maggio 2022 alle ore 14:28 UTCresolved

      This incident has been resolved.

    5. 4 maggio 2022 alle ore 14:28 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)

    Inizio 26 febbraio 2022 alle ore 09:20 UTC · 1h 14m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 26 febbraio 2022 alle ore 09:20 UTCinvestigating

      We are currently investigating this issue.

    2. 26 febbraio 2022 alle ore 09:44 UTCmonitoring

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

    3. 26 febbraio 2022 alle ore 10:34 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast

    Inizio 31 dicembre 2021 alle ore 02:50 UTC · 3h 49m

    OutageIncidente maggiore
    Componenti interessati
    Webscale STRATUS - Northern Virginia
    1. 31 dicembre 2021 alle ore 02:50 UTCidentified

      Emergency Maintenance is being performed on one node in USEast.

    2. 31 dicembre 2021 alle ore 06:39 UTCresolved

      This incident has been resolved.

    3. 5 gennaio 2022 alle ore 17:58 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.