Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    Historial de interrupciones de Magemojo

    49 incidentes de Magemojo registrados desde julio de 2020, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.

    Volver al estado actual

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

    Comenzó 9 de julio de 2025 a las 14:00 UTC · 6h 6m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - SydneyWebscale STRATUS - FrankfurtWebscale STRATUS - Northern Virginia
    1. 9 de julio de 2025 a las 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 de julio de 2025 a las 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)

    Comenzó 28 de abril de 2024 a las 10:27 UTC · 8h 2m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 28 de abril de 2024 a las 10:27 UTCinvestigating

      We are currently investigating this issue.

    2. 28 de abril de 2024 a las 10:45 UTCidentified

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

    3. 28 de abril de 2024 a las 15:34 UTCmonitoring

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

    4. 28 de abril de 2024 a las 18:30 UTCresolved

      This incident has been resolved.

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

    Comenzó 26 de febrero de 2024 a las 19:12 UTC · 17h 43m

    Pending
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 26 de febrero de 2024 a las 19:12 UTCidentified

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

    2. 27 de febrero de 2024 a las 12:55 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (eb34d3)

    Comenzó 13 de noviembre de 2023 a las 14:49 UTC · 3h 22m

    Pending
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 13 de noviembre de 2023 a las 14:49 UTCidentified

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

    2. 13 de noviembre de 2023 a las 18:12 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (eb34d3)

    Comenzó 30 de octubre de 2023 a las 17:08 UTC · 3h 30m

    Pending
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 30 de octubre de 2023 a las 17:08 UTCinvestigating

      We are currently investigating this issue.

    2. 30 de octubre de 2023 a las 17:55 UTCidentified

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

    3. 30 de octubre de 2023 a las 20:38 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (9c912b)

    Comenzó 26 de septiembre de 2023 a las 17:01 UTC · 3h 5m

    Pending
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 26 de septiembre de 2023 a las 17:01 UTCidentified

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

    2. 26 de septiembre de 2023 a las 20:06 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (d79319)

    Comenzó 13 de julio de 2023 a las 18:42 UTC · 17h 31m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 13 de julio de 2023 a las 18:42 UTCinvestigating

      We are currently investigating this issue.

    2. 13 de julio de 2023 a las 21:58 UTCidentified

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

    3. 14 de julio de 2023 a las 3:28 UTCmonitoring

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

    4. 14 de julio de 2023 a las 12:13 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (2a0fef)

    Comenzó 11 de julio de 2023 a las 12:02 UTC · 7h 6m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 11 de julio de 2023 a las 13:33 UTCidentified

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

    2. 11 de julio de 2023 a las 14:55 UTCmonitoring

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

    3. 11 de julio de 2023 a las 19:08 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (fd4119)

    Comenzó 22 de mayo de 2023 a las 15:44 UTC · 18h 3m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 22 de mayo de 2023 a las 15:44 UTCinvestigating

      We are currently investigating this issue.

    2. 22 de mayo de 2023 a las 19:49 UTCidentified

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

    3. 23 de mayo de 2023 a las 7:37 UTCmonitoring

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

    4. 23 de mayo de 2023 a las 9:46 UTCresolved

      This incident has been resolved.

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

    Comenzó 4 de enero de 2023 a las 13:34 UTC · 34m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 4 de enero de 2023 a las 13:34 UTCinvestigating

      We are currently investigating this issue.

    2. 4 de enero de 2023 a las 13:52 UTCmonitoring

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

    3. 4 de enero de 2023 a las 14:08 UTCresolved

      This incident has been resolved.

    4. 4 de enero de 2023 a las 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

    Comenzó 5 de diciembre de 2022 a las 20:19 UTC · 33m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 5 de diciembre de 2022 a las 20:19 UTCinvestigating

      We are currently investigating this issue.

    2. 5 de diciembre de 2022 a las 20:52 UTCresolved

      This incident has been resolved.

    3. 5 de diciembre de 2022 a las 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

    Comenzó 24 de noviembre de 2022 a las 2:40 UTC · 2h 2m

    IssuesIncidente menor
    Componentes afectados
    Webscale STRATUS - Frankfurt
    1. 24 de noviembre de 2022 a las 2:40 UTCidentified

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

    2. 24 de noviembre de 2022 a las 4:42 UTCresolved

      This incident has been resolved

    Emergency Maintenance on 1 node in USEast (dc298c5)

    Comenzó 17 de noviembre de 2022 a las 19:44 UTC · 47m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 17 de noviembre de 2022 a las 19:44 UTCinvestigating

      We are currently investigating this issue.

    2. 17 de noviembre de 2022 a las 20:28 UTCmonitoring

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

    3. 17 de noviembre de 2022 a las 20:31 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast (53d61e5)

    Comenzó 27 de agosto de 2022 a las 18:48 UTC · 1h 18m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 27 de agosto de 2022 a las 18:48 UTCinvestigating

      We are currently investigating this issue.

    2. 27 de agosto de 2022 a las 19:19 UTCidentified

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

    3. 27 de agosto de 2022 a las 20:05 UTCresolved

      This incident has been resolved.

    4. 29 de agosto de 2022 a las 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)

    Comenzó 13 de agosto de 2022 a las 11:41 UTC · 2h 52m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 13 de agosto de 2022 a las 11:41 UTCinvestigating

      We are currently investigating this issue.

    2. 13 de agosto de 2022 a las 12:56 UTCidentified

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

    3. 13 de agosto de 2022 a las 13:44 UTCmonitoring

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

    4. 13 de agosto de 2022 a las 14:34 UTCresolved

      This incident has been resolved.

    5. 15 de agosto de 2022 a las 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)

    Comenzó 7 de agosto de 2022 a las 12:03 UTC · 3h 57m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 7 de agosto de 2022 a las 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 de agosto de 2022 a las 13:44 UTCidentified

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

    3. 7 de agosto de 2022 a las 14:42 UTCmonitoring

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

    4. 7 de agosto de 2022 a las 15:39 UTCmonitoring

      We are continuing to monitor for any further issues.

    5. 7 de agosto de 2022 a las 16:00 UTCresolved

      This incident has been resolved.

    6. 9 de agosto de 2022 a las 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

    Comenzó 8 de junio de 2022 a las 18:46 UTC · 40m

    Pending
    Componentes afectados
    Webscale STRATUS - SydneyWebscale STRATUS - FrankfurtWebscale STRATUS - Northern Virginia
    1. 8 de junio de 2022 a las 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 de junio de 2022 a las 19:25 UTCresolved

      This incident has been resolved.

    Partial Outage in Sydney Region (94aef90)

    Comenzó 4 de mayo de 2022 a las 13:14 UTC · 1h 13m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Sydney
    1. 4 de mayo de 2022 a las 13:14 UTCinvestigating

      We are currently investigating this issue.

    2. 4 de mayo de 2022 a las 13:45 UTCidentified

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

    3. 4 de mayo de 2022 a las 14:01 UTCmonitoring

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

    4. 4 de mayo de 2022 a las 14:28 UTCresolved

      This incident has been resolved.

    5. 4 de mayo de 2022 a las 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)

    Comenzó 26 de febrero de 2022 a las 9:20 UTC · 1h 14m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 26 de febrero de 2022 a las 9:20 UTCinvestigating

      We are currently investigating this issue.

    2. 26 de febrero de 2022 a las 9:44 UTCmonitoring

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

    3. 26 de febrero de 2022 a las 10:34 UTCresolved

      This incident has been resolved.

    Emergency Maintenance on 1 node in USEast

    Comenzó 31 de diciembre de 2021 a las 2:50 UTC · 3h 49m

    OutageIncidente mayor
    Componentes afectados
    Webscale STRATUS - Northern Virginia
    1. 31 de diciembre de 2021 a las 2:50 UTCidentified

      Emergency Maintenance is being performed on one node in USEast.

    2. 31 de diciembre de 2021 a las 6:39 UTCresolved

      This incident has been resolved.

    3. 5 de enero de 2022 a las 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.