Historial de interrupciones de Macabacus

1. 18 de agosto de 2026 a las 15:09 UTCinvestigating

   Nuestra plataforma de gestión de suscripción (Recurly) está experimentando problemas hoy. Inscribirse en las acciones de administración de la adición o la suscripción puede ser afectada. Estamos monitoreando activamente.

2. 18 de agosto de 2026 a las 15:22 UTCinvestigating

   Parece que la cuestión se resuelve. Póngase en contacto con [email protected] si experimenta problemas.

3. 18 de agosto de 2026 a las 15:22 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 12 de junio de 2025 a las 18:25 UTCinvestigating

   We are currently experiencing an issue impacting access to https://macabacus.com. This is due to an ongoing incident with our hosting provider, Kinsta, which leverages Cloudflare. You can track their status here: https://status.kinsta.com. Please note: 1. The Macabacus Admin Console and user sign-in are not affected. 2. Our team is monitoring the situation and will provide updates as they become available. We appreciate your patience as Kinsta works to resolve the issue.

2. 13 de junio de 2025 a las 0:34 UTCresolved

   This incident has been resolved.

1. 27 de febrero de 2025 a las 22:57 UTCinvestigating

   We are currently investigating the issue, and will provide an update shortly.

2. 27 de febrero de 2025 a las 23:11 UTCresolved

   The issue has been resolved. Service has been restored.

1. 10 de enero de 2025 a las 22:26 UTCinvestigating

   We are experiencing service disruptions with the Admin Console due to networking issues reported by Microsoft Azure, which are affecting multiple services globally. Our team is monitoring the situation closely and working to minimize the impact on our services. For updates from Microsoft, visit Azure Status Page - https://azure.status.microsoft/en-us/status We apologize for the inconvenience and will share further updates as we have them.

2. 10 de enero de 2025 a las 22:42 UTCresolved

   The incident has been resolved.

1. 10 de enero de 2025 a las 0:26 UTCinvestigating

   We are experiencing service disruptions with the Admin Console due to networking issues reported by Microsoft Azure, which are affecting multiple services globally. Our team is monitoring the situation closely and working to minimize the impact on our services. For updates from Microsoft, visit Azure Status Page - https://azure.status.microsoft/en-us/status We apologize for the inconvenience and will share further updates as we have them.

2. 10 de enero de 2025 a las 5:28 UTCresolved

   This incident has been mitigated from our side, and service is restored.

1. 30 de enero de 2024 a las 16:01 UTCinvestigating

   We are currently investigating this issue.

2. 30 de enero de 2024 a las 16:31 UTCinvestigating

   Users are currently granted limited access to the add-in. Users should now be able to sign in to the add-in to avoid disruption.

3. 30 de enero de 2024 a las 18:41 UTCresolved

   The issue has been resolved. Please reach out to [email protected] if you continue to experience issues.

1. 8 de enero de 2024 a las 16:08 UTCidentified

   We are currently investigating as it appears that one of our providers is having intermittent issues impacting the performance of our platform. We will update here as we learn more. Thank you for your patience.

2. 8 de enero de 2024 a las 23:45 UTCidentified

   We appreciate your patience. The issue, due to an outage today at Recurly, has been resolved.

3. 9 de enero de 2024 a las 4:20 UTCresolved

   This incident has been resolved.

1. 17 de octubre de 2023 a las 20:03 UTCinvestigating

   We are currently investigating this issue—thank-you for your patience.

2. 17 de octubre de 2023 a las 20:17 UTCinvestigating

   We are continuing to investigate this issue.

3. 17 de octubre de 2023 a las 22:37 UTCresolved

   This incident has been resolved. The root cause of the incident was a partial outage at Recurly, our 3rd party subscription management API.

1. 12 de abril de 2023 a las 16:46 UTCresolved

   Affected users may need to restart affected Office applications or re-activate Macabacus software using the button with key icon at the right edge of the Macabacus tab.

1. 25 de enero de 2023 a las 18:52 UTCresolved

   A fix has been implemented and we are monitoring the results. Affected users may need to restart affected Office applications or re-activate Macabacus software using the button with key icon at the right edge of the Macabacus tab.

1. 30 de abril de 2022 a las 11:51 UTCinvestigating

   We are currently investigating an issue related to user authentication that is forcing some users to wait before accessing some Macabacus features.

2. 30 de abril de 2022 a las 12:53 UTCmonitoring

   A fix has been implemented and we are monitoring the results. Affected users may need to restart affected Office applications or re-activate Macabacus software using the button with key icon at the right edge of the Macabacus tab.

3. 30 de abril de 2022 a las 15:36 UTCresolved

   This incident has been resolved.

1. 3 de agosto de 2020 a las 19:13 UTCinvestigating

   We are currently investigating this issue.

2. 3 de agosto de 2020 a las 19:42 UTCidentified

   We have traced this to a DNS issue with our web host, and are working on a fix.

3. 3 de agosto de 2020 a las 20:09 UTCmonitoring

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

4. 3 de agosto de 2020 a las 21:23 UTCresolved

   This incident has been resolved.

1. 21 de julio de 2020 a las 21:39 UTCinvestigating

   We are currently investigating this issue.

2. 21 de julio de 2020 a las 21:46 UTCinvestigating

   Possible hardware failure. Continuing to investigate.

3. 21 de julio de 2020 a las 21:51 UTCmonitoring

   The condition has cleared and we are continuing to monitor the situation.

4. 21 de julio de 2020 a las 22:27 UTCresolved

   This incident has been resolved.

1. 4 de mayo de 2020 a las 13:22 UTCinvestigating

   We are currently investigating this issue.

2. 4 de mayo de 2020 a las 14:20 UTCresolved

   This incident has been resolved.

3. 4 de mayo de 2020 a las 17:10 UTCpostmortem

   At approximately 9:15 AM EDT this morning, a Macabacus data center experienced a brief Denial of Service attack resulting in approximately 30 minutes of downtime for the website. The attack has been contained, and no services or data were compromised in the attack.

1. 25 de febrero de 2020 a las 14:33 UTCinvestigating

   We are experiencing intermittent outages affecting our website and user authentication. We are investigating this issue.

2. 25 de febrero de 2020 a las 15:30 UTCinvestigating

   We are continuing to investigate this issue.

3. 25 de febrero de 2020 a las 19:20 UTCinvestigating

   Website performance has improved, but intermittent degradations in performance may occur as we continue to investigate this issue.

4. 25 de febrero de 2020 a las 20:58 UTCinvestigating

   This incident has been resolved.

5. 25 de febrero de 2020 a las 20:58 UTCresolved

   This incident has been resolved.

1. 4 de febrero de 2020 a las 16:57 UTCinvestigating

   We are currently investigating this issue.

2. 4 de febrero de 2020 a las 18:09 UTCinvestigating

   Our web host's shared data center is experiencing a major network outage affecting many websites. The vendor's network engineers are investigating the problem.

3. 4 de febrero de 2020 a las 19:44 UTCinvestigating

   Our vendor's data center experienced a "significant Denial of Service (DoS) attack." Their networking team isolated the multiple sources of the attacks and nullified them. The affected data center has reportedly been performing at normal levels recently, and the vendor has declared the attack contained. Websites hosted in this data center continue to come back up following containment of the attack, so some affected websites, like ours, have not yet recovered. For those unfamiliar with the term, a Denial of Service (DoS) attack is when an attacker floods a site with so much malicious traffic that it is unable to respond to legitimate traffic. The vendor confirmed that no services were breached, and no data was compromised by the attackers.

4. 4 de febrero de 2020 a las 20:21 UTCinvestigating

   We are continuing to investigate this issue.

5. 4 de febrero de 2020 a las 20:23 UTCinvestigating

   Website appears to be back up and functioning normally. We will continue to monitor for issues.

6. 4 de febrero de 2020 a las 20:57 UTCresolved

   This incident has been resolved.

1. 24 de octubre de 2018 a las 10:00 UTCinvestigating

   We are currently investigating an issue affecting user authentication and Admin Console login.

2. 24 de octubre de 2018 a las 10:36 UTCmonitoring

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

3. 24 de octubre de 2018 a las 10:56 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 24 de octubre de 2018 a las 12:23 UTCresolved

   This incident has been resolved.

1. 12 de julio de 2018 a las 14:54 UTCinvestigating

   We are currently investigating this issue

2. 12 de julio de 2018 a las 15:03 UTCresolved

   This incident has been resolved.

1. 20 de julio de 2017 a las 16:49 UTCinvestigating

   The macabacus.com website is experiencing an outage likely related to the one earlier today. We and our technology partner that manages the server are investigating.

2. 20 de julio de 2017 a las 17:18 UTCresolved

   The server outage has been determined to be the result of a failed hardware component. The component has been replaced, and no further outages related to this incident are expected.

1. 20 de julio de 2017 a las 15:25 UTCinvestigating

   The macabacus.com website is down for reasons that we and our technology providers are currently investigating. This outage may affect user authentication and thus access to Macabacus software.

2. 20 de julio de 2017 a las 15:28 UTCmonitoring

   There is no longer an outage at macabacus.com. We are working with our technology partners to determine the root cause and whether to expect further outages.

3. 20 de julio de 2017 a las 15:39 UTCresolved

   This incident was caused by an unexpected failure of a server managed by one of our technology partners. The server has been restored and appears stable. This incident is now resolved.