Incidents reported on status page for elastic.io https://status1.elastic.io/ https://d1lppblt9t2x15.cloudfront.net/logos/78ca1416b9d4f7e5e5a56e68a94b2b3b.png https://status1.elastic.io/ en https://status1.elastic.io/incident/475798 Wed, 11 Dec 2024 06:21:39 -0000 https://status1.elastic.io/incident/475798#b109d1751225b6cb5565c62c19f89fe5f0c600aef179683de54945fb29c5972f AU cluster API recovered. https://status1.elastic.io/incident/475798 Wed, 11 Dec 2024 06:14:30 -0000 https://status1.elastic.io/incident/475798#baa566928d744ba31d635e9e3ef9333406540280e8071bfc4f729ecef8b4c875 AU cluster API went down. https://status1.elastic.io/incident/460148 Wed, 27 Nov 2024 11:00:11 +0000 https://status1.elastic.io/incident/460148#e4f8eb7ecb200ea53485985392d248eb41b8c30eba12b86f14de25e226a9cac3 Maintenance completed https://status1.elastic.io/incident/460148 Wed, 27 Nov 2024 11:00:11 +0000 https://status1.elastic.io/incident/460148#e4f8eb7ecb200ea53485985392d248eb41b8c30eba12b86f14de25e226a9cac3 Maintenance completed https://status1.elastic.io/incident/460148 Wed, 27 Nov 2024 11:00:11 +0000 https://status1.elastic.io/incident/460148#e4f8eb7ecb200ea53485985392d248eb41b8c30eba12b86f14de25e226a9cac3 Maintenance completed https://status1.elastic.io/incident/460148 Wed, 27 Nov 2024 11:00:11 +0000 https://status1.elastic.io/incident/460148#e4f8eb7ecb200ea53485985392d248eb41b8c30eba12b86f14de25e226a9cac3 Maintenance completed https://status1.elastic.io/incident/460148 Wed, 27 Nov 2024 10:00:11 -0000 https://status1.elastic.io/incident/460148#fab4d4a24a5603144281f79223e6bda6911a2457e7460bafd077f31d5b604c1e We would like to inform you of a scheduled maintenance period for our systems, as part of our ongoing commitment to enhance the overall performance and reliability of our platform. Maintenance Schedule: Date: 27.11.2024 Time: 11:00 AM CET to 12:00 PM CET Affected System: During this maintenance window, MongoDB will be upgraded to v6.0. This system is a critical component of our platform, and the updates will significantly enhance its performance and responsiveness. The planned enhancements aim to improve overall system efficiency, providing you with a more seamless and reliable user experience. Possible Interruptions: No downtime or service interruption is expected. However, there is a small chance that some related services may restart and send warnings. We apologize for any inconvenience this interruption may cause and appreciate your understanding and patience as we work to improve our services. To minimize the interruption, feel free to Suspend your flows during the maintenance period. Should you have any questions or need further assistance, please do not hesitate to contact us. Thank you for your cooperation and support! Best regards, EIO Team https://status1.elastic.io/incident/460148 Wed, 27 Nov 2024 10:00:11 -0000 https://status1.elastic.io/incident/460148#fab4d4a24a5603144281f79223e6bda6911a2457e7460bafd077f31d5b604c1e We would like to inform you of a scheduled maintenance period for our systems, as part of our ongoing commitment to enhance the overall performance and reliability of our platform. Maintenance Schedule: Date: 27.11.2024 Time: 11:00 AM CET to 12:00 PM CET Affected System: During this maintenance window, MongoDB will be upgraded to v6.0. This system is a critical component of our platform, and the updates will significantly enhance its performance and responsiveness. The planned enhancements aim to improve overall system efficiency, providing you with a more seamless and reliable user experience. Possible Interruptions: No downtime or service interruption is expected. However, there is a small chance that some related services may restart and send warnings. We apologize for any inconvenience this interruption may cause and appreciate your understanding and patience as we work to improve our services. To minimize the interruption, feel free to Suspend your flows during the maintenance period. Should you have any questions or need further assistance, please do not hesitate to contact us. Thank you for your cooperation and support! Best regards, EIO Team https://status1.elastic.io/incident/460148 Wed, 27 Nov 2024 10:00:11 -0000 https://status1.elastic.io/incident/460148#fab4d4a24a5603144281f79223e6bda6911a2457e7460bafd077f31d5b604c1e We would like to inform you of a scheduled maintenance period for our systems, as part of our ongoing commitment to enhance the overall performance and reliability of our platform. Maintenance Schedule: Date: 27.11.2024 Time: 11:00 AM CET to 12:00 PM CET Affected System: During this maintenance window, MongoDB will be upgraded to v6.0. This system is a critical component of our platform, and the updates will significantly enhance its performance and responsiveness. The planned enhancements aim to improve overall system efficiency, providing you with a more seamless and reliable user experience. Possible Interruptions: No downtime or service interruption is expected. However, there is a small chance that some related services may restart and send warnings. We apologize for any inconvenience this interruption may cause and appreciate your understanding and patience as we work to improve our services. To minimize the interruption, feel free to Suspend your flows during the maintenance period. Should you have any questions or need further assistance, please do not hesitate to contact us. Thank you for your cooperation and support! Best regards, EIO Team https://status1.elastic.io/incident/460148 Wed, 27 Nov 2024 10:00:11 -0000 https://status1.elastic.io/incident/460148#fab4d4a24a5603144281f79223e6bda6911a2457e7460bafd077f31d5b604c1e We would like to inform you of a scheduled maintenance period for our systems, as part of our ongoing commitment to enhance the overall performance and reliability of our platform. Maintenance Schedule: Date: 27.11.2024 Time: 11:00 AM CET to 12:00 PM CET Affected System: During this maintenance window, MongoDB will be upgraded to v6.0. This system is a critical component of our platform, and the updates will significantly enhance its performance and responsiveness. The planned enhancements aim to improve overall system efficiency, providing you with a more seamless and reliable user experience. Possible Interruptions: No downtime or service interruption is expected. However, there is a small chance that some related services may restart and send warnings. We apologize for any inconvenience this interruption may cause and appreciate your understanding and patience as we work to improve our services. To minimize the interruption, feel free to Suspend your flows during the maintenance period. Should you have any questions or need further assistance, please do not hesitate to contact us. Thank you for your cooperation and support! Best regards, EIO Team https://status1.elastic.io/incident/455634 Mon, 04 Nov 2024 12:06:22 -0000 https://status1.elastic.io/incident/455634#9a6fae3e749b9c128a2dba82123ecb2c78cb79a66670181715648911d5bff07a US cluster frontend recovered. https://status1.elastic.io/incident/455634 Mon, 04 Nov 2024 12:00:38 -0000 https://status1.elastic.io/incident/455634#6f06665303094172397fc8c7fd79d87ea72fa556b0217165afa9e12c1e82ccfa US cluster frontend went down. https://status1.elastic.io/incident/455634 Mon, 04 Nov 2024 11:31:52 -0000 https://status1.elastic.io/incident/455634#2ce6f1c4255c5ea5bd283f8ba4036d971f2d6fcc4edcb4504794593b54b49b7c AU cluster Realtime recovered. https://status1.elastic.io/incident/455634 Mon, 04 Nov 2024 11:25:55 -0000 https://status1.elastic.io/incident/455634#a1f7cc700aad9ec419d990cddda08080d6e9d8fd3c6e303065839010557507b6 AU cluster Realtime went down. https://status1.elastic.io/incident/450466 Fri, 25 Oct 2024 08:01:00 -0000 https://status1.elastic.io/incident/450466#5849de84a21ee950b8831aa7a77bc5717fbc3053367ef34022320925aace1886 All services were back online at 10:01 CET. This notification was sent manually. https://status1.elastic.io/incident/450377 Fri, 25 Oct 2024 07:25:00 -0000 https://status1.elastic.io/incident/450377#6aade9f8808f02dd0a2357e03aa1c8b0d6fb9bcf9b30994fd59e2020459ec8f6 The platform is operational, and messages are being processed. However, one of the replication nodes of our message broker is down. Our team is investigating the cause. https://status1.elastic.io/incident/450374 Fri, 25 Oct 2024 07:23:00 -0000 https://status1.elastic.io/incident/450374#f65d633dbe3cdb1fdd91aa2ad971dc10b31c845f2554fbde18679b3bedf9c485 Erroneous report https://status1.elastic.io/incident/450360 Fri, 25 Oct 2024 06:42:00 -0000 https://status1.elastic.io/incident/450360#d099e05e10955e6938e086b59f8866b5b8e334fc76f32ea8e5b3c0df78acd0b5 EU cluster Realtime went down. https://status1.elastic.io/incident/444253 Mon, 14 Oct 2024 09:59:18 -0000 https://status1.elastic.io/incident/444253#9ab798b28b773d7177f8a42908fb1a74b62ae76c8c3e157321053ec292bd4170 AU cluster Realtime recovered. https://status1.elastic.io/incident/444253 Mon, 14 Oct 2024 09:45:10 -0000 https://status1.elastic.io/incident/444253#656f0b1ade5e35d89f682efd37f0c688ffe2506b557fb14575f2e86d1c6c6dc5 AU cluster Realtime went down. https://status1.elastic.io/incident/438638 Thu, 03 Oct 2024 09:01:00 -0000 https://status1.elastic.io/incident/438638#5d7090fd8d841c2126c3d92bc2872ea3380581e0ddb9258ebf36ea324854d011 The service came back online 30 minutes ago. The status was updated manually as it was not processed automatically. https://status1.elastic.io/incident/438638 Thu, 03 Oct 2024 08:20:00 -0000 https://status1.elastic.io/incident/438638#115a1e05ccfecc958722ac860eec19130e8b812edd9302aaa020a214d303c595 We are preparing the platform for the new release, which includes improvements to the Webhook quota. There may be minimal interruptions during the service restart. https://status1.elastic.io/incident/427111 Tue, 10 Sep 2024 13:56:32 -0000 https://status1.elastic.io/incident/427111#b7312b49c0babddd00d717feafaafde5fbefdd28ed72d015fc4ae58d1d011cf4 AU cluster Realtime recovered. https://status1.elastic.io/incident/427111 Tue, 10 Sep 2024 13:37:07 -0000 https://status1.elastic.io/incident/427111#cf630497656fad01d00cdce4089f2497cf961f5a6b90ffab95efb325fe726978 AU cluster Realtime went down. https://status1.elastic.io/incident/420144 Tue, 27 Aug 2024 15:19:55 -0000 https://status1.elastic.io/incident/420144#43cdd78e01d20dd4a52fb3308e676b506476c778cd0b725b19deb6802b386ded EU cluster WebHook recovered. https://status1.elastic.io/incident/420144 Tue, 27 Aug 2024 15:02:00 -0000 https://status1.elastic.io/incident/420144#c4f3552e3fac5bac7271b13ea7b147e8aecdeef7239d7cc03776864fe8c929a4 EU cluster WebHook went down. EIO team comment: The issue was inside the monitoring service: `DNS lookup failure`. The Webhook service continued to work. https://status1.elastic.io/incident/414253 Thu, 15 Aug 2024 08:14:00 -0000 https://status1.elastic.io/incident/414253#bae23ed2b13296a52097dd96321de153f2ea61b521b1aef3477939c90a09d82e ☁︎ Incident Summary On August 11, 2024, at approximately 20:00 CET, the platform on the EU instance began experiencing instability, followed by downtime and maintenance, which lasted until August 13, 2024, at 14:00 CET. ☁︎ Impact ● Services Affected: ○ Platform UI: Partial availability, followed by downtime ○ Platform services: Partial availability, followed by downtime ○ Integration flows: stopped for a 6-hour platform maintenance ☁︎ Timeframe ● Entire incident tracking: ○ 11.08.2024 20:00 CET - 13.08.2024 14:00 CET ● Detailed: ○ 11.08.2024 20:00 CET - 13.08.2024 ≈1:00 CET The platform receives messages and stores them. There was a timeframe, during approximately 6 hours the messages were partially processed. ○ 13.08.2024 ≈1:00 CET - 13.08.2024 ≈8:00 CET Partial availability of platform services. ○ 13.08.2024 ≈8:00 CET - 13.08.2024 14:00 CET Maintenance. All flows have been stopped for the duration of the maintenance. ☁︎ Root Cause The main issue happened with the networking part on one of the RabbitMQ nodes. Since RabbitMQ operates in a clustered state, this issue did not affect the platform until 20:00 CET. Typically, we experience an increase in load during the evening, which is expected behaviour for our platform and does not generally cause any problems. However, the malfunctioning RabbitMQ node entered a partial split-brain state. ☁︎ Description During the period of platform instability, our Development and DevOps teams concentrated on stabilizing the platform. All these actions were performed with the primary objective of preventing any incoming data loss. Despite extensive efforts, all available options for recovering the existing RabbitMQ functionality were unsuccessful, and the duration of the platform instability kept increasing. Consequently, we decided to perform a more significant step by resetting the RabbitMQ cluster. This essential step required a temporary stop of all flows. Once this action was completed, all affected platform services were back to standard operation. Additionally, the following steps were done: - Upgrading RabbitMQ nodes - Re-working RabbitMQ queues policies The maintenance process allowed our team to enhance the stability of the RabbitMQ cluster and platform services in terms of queues management. These actions will protect the platform's functionality against similar issues in the future. ☁︎ Additional Measures ● Elastic.io will enhance the status page to provide more detailed information about the status of platform services. ● Maintenance to apply the same enhancements to the US instance, AU instance, and private instances. ● Provide the new enhanced platform notification service https://status1.elastic.io/incident/414253 Thu, 15 Aug 2024 08:14:00 -0000 https://status1.elastic.io/incident/414253#bae23ed2b13296a52097dd96321de153f2ea61b521b1aef3477939c90a09d82e ☁︎ Incident Summary On August 11, 2024, at approximately 20:00 CET, the platform on the EU instance began experiencing instability, followed by downtime and maintenance, which lasted until August 13, 2024, at 14:00 CET. ☁︎ Impact ● Services Affected: ○ Platform UI: Partial availability, followed by downtime ○ Platform services: Partial availability, followed by downtime ○ Integration flows: stopped for a 6-hour platform maintenance ☁︎ Timeframe ● Entire incident tracking: ○ 11.08.2024 20:00 CET - 13.08.2024 14:00 CET ● Detailed: ○ 11.08.2024 20:00 CET - 13.08.2024 ≈1:00 CET The platform receives messages and stores them. There was a timeframe, during approximately 6 hours the messages were partially processed. ○ 13.08.2024 ≈1:00 CET - 13.08.2024 ≈8:00 CET Partial availability of platform services. ○ 13.08.2024 ≈8:00 CET - 13.08.2024 14:00 CET Maintenance. All flows have been stopped for the duration of the maintenance. ☁︎ Root Cause The main issue happened with the networking part on one of the RabbitMQ nodes. Since RabbitMQ operates in a clustered state, this issue did not affect the platform until 20:00 CET. Typically, we experience an increase in load during the evening, which is expected behaviour for our platform and does not generally cause any problems. However, the malfunctioning RabbitMQ node entered a partial split-brain state. ☁︎ Description During the period of platform instability, our Development and DevOps teams concentrated on stabilizing the platform. All these actions were performed with the primary objective of preventing any incoming data loss. Despite extensive efforts, all available options for recovering the existing RabbitMQ functionality were unsuccessful, and the duration of the platform instability kept increasing. Consequently, we decided to perform a more significant step by resetting the RabbitMQ cluster. This essential step required a temporary stop of all flows. Once this action was completed, all affected platform services were back to standard operation. Additionally, the following steps were done: - Upgrading RabbitMQ nodes - Re-working RabbitMQ queues policies The maintenance process allowed our team to enhance the stability of the RabbitMQ cluster and platform services in terms of queues management. These actions will protect the platform's functionality against similar issues in the future. ☁︎ Additional Measures ● Elastic.io will enhance the status page to provide more detailed information about the status of platform services. ● Maintenance to apply the same enhancements to the US instance, AU instance, and private instances. ● Provide the new enhanced platform notification service https://status1.elastic.io/incident/414253 Thu, 15 Aug 2024 08:14:00 -0000 https://status1.elastic.io/incident/414253#bae23ed2b13296a52097dd96321de153f2ea61b521b1aef3477939c90a09d82e ☁︎ Incident Summary On August 11, 2024, at approximately 20:00 CET, the platform on the EU instance began experiencing instability, followed by downtime and maintenance, which lasted until August 13, 2024, at 14:00 CET. ☁︎ Impact ● Services Affected: ○ Platform UI: Partial availability, followed by downtime ○ Platform services: Partial availability, followed by downtime ○ Integration flows: stopped for a 6-hour platform maintenance ☁︎ Timeframe ● Entire incident tracking: ○ 11.08.2024 20:00 CET - 13.08.2024 14:00 CET ● Detailed: ○ 11.08.2024 20:00 CET - 13.08.2024 ≈1:00 CET The platform receives messages and stores them. There was a timeframe, during approximately 6 hours the messages were partially processed. ○ 13.08.2024 ≈1:00 CET - 13.08.2024 ≈8:00 CET Partial availability of platform services. ○ 13.08.2024 ≈8:00 CET - 13.08.2024 14:00 CET Maintenance. All flows have been stopped for the duration of the maintenance. ☁︎ Root Cause The main issue happened with the networking part on one of the RabbitMQ nodes. Since RabbitMQ operates in a clustered state, this issue did not affect the platform until 20:00 CET. Typically, we experience an increase in load during the evening, which is expected behaviour for our platform and does not generally cause any problems. However, the malfunctioning RabbitMQ node entered a partial split-brain state. ☁︎ Description During the period of platform instability, our Development and DevOps teams concentrated on stabilizing the platform. All these actions were performed with the primary objective of preventing any incoming data loss. Despite extensive efforts, all available options for recovering the existing RabbitMQ functionality were unsuccessful, and the duration of the platform instability kept increasing. Consequently, we decided to perform a more significant step by resetting the RabbitMQ cluster. This essential step required a temporary stop of all flows. Once this action was completed, all affected platform services were back to standard operation. Additionally, the following steps were done: - Upgrading RabbitMQ nodes - Re-working RabbitMQ queues policies The maintenance process allowed our team to enhance the stability of the RabbitMQ cluster and platform services in terms of queues management. These actions will protect the platform's functionality against similar issues in the future. ☁︎ Additional Measures ● Elastic.io will enhance the status page to provide more detailed information about the status of platform services. ● Maintenance to apply the same enhancements to the US instance, AU instance, and private instances. ● Provide the new enhanced platform notification service https://status1.elastic.io/incident/414253 Thu, 15 Aug 2024 08:14:00 -0000 https://status1.elastic.io/incident/414253#bae23ed2b13296a52097dd96321de153f2ea61b521b1aef3477939c90a09d82e ☁︎ Incident Summary On August 11, 2024, at approximately 20:00 CET, the platform on the EU instance began experiencing instability, followed by downtime and maintenance, which lasted until August 13, 2024, at 14:00 CET. ☁︎ Impact ● Services Affected: ○ Platform UI: Partial availability, followed by downtime ○ Platform services: Partial availability, followed by downtime ○ Integration flows: stopped for a 6-hour platform maintenance ☁︎ Timeframe ● Entire incident tracking: ○ 11.08.2024 20:00 CET - 13.08.2024 14:00 CET ● Detailed: ○ 11.08.2024 20:00 CET - 13.08.2024 ≈1:00 CET The platform receives messages and stores them. There was a timeframe, during approximately 6 hours the messages were partially processed. ○ 13.08.2024 ≈1:00 CET - 13.08.2024 ≈8:00 CET Partial availability of platform services. ○ 13.08.2024 ≈8:00 CET - 13.08.2024 14:00 CET Maintenance. All flows have been stopped for the duration of the maintenance. ☁︎ Root Cause The main issue happened with the networking part on one of the RabbitMQ nodes. Since RabbitMQ operates in a clustered state, this issue did not affect the platform until 20:00 CET. Typically, we experience an increase in load during the evening, which is expected behaviour for our platform and does not generally cause any problems. However, the malfunctioning RabbitMQ node entered a partial split-brain state. ☁︎ Description During the period of platform instability, our Development and DevOps teams concentrated on stabilizing the platform. All these actions were performed with the primary objective of preventing any incoming data loss. Despite extensive efforts, all available options for recovering the existing RabbitMQ functionality were unsuccessful, and the duration of the platform instability kept increasing. Consequently, we decided to perform a more significant step by resetting the RabbitMQ cluster. This essential step required a temporary stop of all flows. Once this action was completed, all affected platform services were back to standard operation. Additionally, the following steps were done: - Upgrading RabbitMQ nodes - Re-working RabbitMQ queues policies The maintenance process allowed our team to enhance the stability of the RabbitMQ cluster and platform services in terms of queues management. These actions will protect the platform's functionality against similar issues in the future. ☁︎ Additional Measures ● Elastic.io will enhance the status page to provide more detailed information about the status of platform services. ● Maintenance to apply the same enhancements to the US instance, AU instance, and private instances. ● Provide the new enhanced platform notification service https://status1.elastic.io/incident/414253 Thu, 15 Aug 2024 08:14:00 -0000 https://status1.elastic.io/incident/414253#bae23ed2b13296a52097dd96321de153f2ea61b521b1aef3477939c90a09d82e ☁︎ Incident Summary On August 11, 2024, at approximately 20:00 CET, the platform on the EU instance began experiencing instability, followed by downtime and maintenance, which lasted until August 13, 2024, at 14:00 CET. ☁︎ Impact ● Services Affected: ○ Platform UI: Partial availability, followed by downtime ○ Platform services: Partial availability, followed by downtime ○ Integration flows: stopped for a 6-hour platform maintenance ☁︎ Timeframe ● Entire incident tracking: ○ 11.08.2024 20:00 CET - 13.08.2024 14:00 CET ● Detailed: ○ 11.08.2024 20:00 CET - 13.08.2024 ≈1:00 CET The platform receives messages and stores them. There was a timeframe, during approximately 6 hours the messages were partially processed. ○ 13.08.2024 ≈1:00 CET - 13.08.2024 ≈8:00 CET Partial availability of platform services. ○ 13.08.2024 ≈8:00 CET - 13.08.2024 14:00 CET Maintenance. All flows have been stopped for the duration of the maintenance. ☁︎ Root Cause The main issue happened with the networking part on one of the RabbitMQ nodes. Since RabbitMQ operates in a clustered state, this issue did not affect the platform until 20:00 CET. Typically, we experience an increase in load during the evening, which is expected behaviour for our platform and does not generally cause any problems. However, the malfunctioning RabbitMQ node entered a partial split-brain state. ☁︎ Description During the period of platform instability, our Development and DevOps teams concentrated on stabilizing the platform. All these actions were performed with the primary objective of preventing any incoming data loss. Despite extensive efforts, all available options for recovering the existing RabbitMQ functionality were unsuccessful, and the duration of the platform instability kept increasing. Consequently, we decided to perform a more significant step by resetting the RabbitMQ cluster. This essential step required a temporary stop of all flows. Once this action was completed, all affected platform services were back to standard operation. Additionally, the following steps were done: - Upgrading RabbitMQ nodes - Re-working RabbitMQ queues policies The maintenance process allowed our team to enhance the stability of the RabbitMQ cluster and platform services in terms of queues management. These actions will protect the platform's functionality against similar issues in the future. ☁︎ Additional Measures ● Elastic.io will enhance the status page to provide more detailed information about the status of platform services. ● Maintenance to apply the same enhancements to the US instance, AU instance, and private instances. ● Provide the new enhanced platform notification service https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 11:43:12 -0000 https://status1.elastic.io/incident/412251#f1c309e58026b225a63b1846b7570f0e9858160e8d3bb5fa22bfe36b13b1d765 EU cluster frontend and EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 11:43:12 -0000 https://status1.elastic.io/incident/412251#f1c309e58026b225a63b1846b7570f0e9858160e8d3bb5fa22bfe36b13b1d765 EU cluster frontend and EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 11:40:46 -0000 https://status1.elastic.io/incident/412251#1da582835bc28f10ec7407e7e5926a4f0d7fa5aed8dc009b7477abfa6ea4faab EU cluster Realtime recovered. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 09:42:20 -0000 https://status1.elastic.io/incident/412251#7f542232657451c5bf4afe2f1af519d1df1e72122f3fd70c9ed02b7296631b2a EU cluster API recovered. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 09:28:21 -0000 https://status1.elastic.io/incident/412251#226b1b400433c3ba036b3e3da4e1d2035d33f7c9c7bac8fa0420e59291676c99 EU cluster frontend went down. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 09:10:53 -0000 https://status1.elastic.io/incident/412251#93b27a323c3cfea99b800a29003532fbe5c34de9cd2d32cb2866e43097222861 EU cluster API went down. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 08:52:38 -0000 https://status1.elastic.io/incident/412251#23ce80afeaba54c57ea01854fdd46308bf01d9101bb9792c209684bc864a52fe EU cluster API recovered. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 08:51:20 -0000 https://status1.elastic.io/incident/412251#525de6d342ae01eead94f943e32711aef00770b0aebda775b300c668bdefef89 EU cluster frontend recovered. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 08:06:19 -0000 https://status1.elastic.io/incident/412251#07b1f523dc97083db5c2f5ad476fed71844cd47b5b8c2c11c68d21046c95d5b6 EU cluster frontend went down. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 07:10:40 -0000 https://status1.elastic.io/incident/412251#c5c0d1b6cf86432e3cab7318496277363745743b5871e5476aa6a1235fc51890 EU cluster API went down. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 00:32:20 -0000 https://status1.elastic.io/incident/412251#6e86dbb561ca4496cc87e98c32b0f9c761c462bc163634f64c534fdb0186158d EU cluster frontend recovered. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 00:31:33 -0000 https://status1.elastic.io/incident/412251#cad4f5ce7951a873e0ce2002926b170478723aba4c4032a076a263b48641cfcf EU cluster API recovered. https://status1.elastic.io/incident/412251 Tue, 13 Aug 2024 00:22:18 -0000 https://status1.elastic.io/incident/412251#3c1d987960dcf18382198fcf331cbcf5783c1c35ab760383a876003afd79cea9 EU cluster frontend went down. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 21:45:21 -0000 https://status1.elastic.io/incident/412251#23ffefdb73f0c03ef6d592afeb046b8b1c7273704a3d2a228f8bda3e6b2238a0 EU cluster API went down. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 21:32:48 -0000 https://status1.elastic.io/incident/412251#75c4a13f980d276829a25ac558aa0d32f21704d0b5f3c9b6121948ab1e4e2e07 EU cluster Realtime went down. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 21:30:19 -0000 https://status1.elastic.io/incident/412251#1464d8c7893458f51efd51ab71ae113b9d034753754072b4b7ed102a519aad21 EU cluster WebHook went down. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 21:23:51 -0000 https://status1.elastic.io/incident/412251#001ed01d1ed7d135253ef34620f648576269092396d3b410e88ba53015b0fe77 EU cluster Realtime recovered. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 08:40:48 -0000 https://status1.elastic.io/incident/412251#6f89cc82a51528cb511c7ab17aec83f4baad1535595540b25bc7615a2821a708 EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 08:18:47 -0000 https://status1.elastic.io/incident/412251#5a29ebe05253aaf837cf5c596aaa4a7e9977b3104579f27c67e48f5aca9efbaf EU cluster WebHook went down. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 06:28:43 -0000 https://status1.elastic.io/incident/412251#bf16a073c4b95bb953e062ca8e78e0931d717e709061ed55c85d5dc0b7c38bc0 EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 06:21:06 -0000 https://status1.elastic.io/incident/412251#c00d45346458fc79de5c12c742449846e63ad49fff2f3455c44ebdeb4238a3c1 EU cluster WebHook went down. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 05:21:43 -0000 https://status1.elastic.io/incident/412251#3652b8d0baa91e95cacc934231f3943a41dd895dbcf7bd33b393127b6a768729 EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 05:01:02 -0000 https://status1.elastic.io/incident/412251#dae39c7c98950f4d865a0169be07517020deef9baa7582f8ac52e6d21e9141c9 EU cluster WebHook went down. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 04:35:18 -0000 https://status1.elastic.io/incident/412251#06e82dd7358424d41bb276f0674bfc1f3dbbed5a020686919126239575d38cd9 EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 04:09:11 -0000 https://status1.elastic.io/incident/412251#afd50371ba74ab04feeb6e94addf57b029f565fd0a25f2374fce4ce1bfb3274d EU cluster WebHook went down. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 01:41:21 -0000 https://status1.elastic.io/incident/412251#cd40072f0e22230e692b849c2784a2e2e6b57c36fbba99cb6200c4f346742832 EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Mon, 12 Aug 2024 01:29:50 -0000 https://status1.elastic.io/incident/412251#368742d000a04d5b5ef5c5f7aa3bea7c55c311691d2eec1d5fc2bbe54838f68c EU cluster WebHook went down. https://status1.elastic.io/incident/412251 Sun, 11 Aug 2024 21:37:54 -0000 https://status1.elastic.io/incident/412251#b3cb84d4d42c673f199f56d2a6920bec9c5a92218323a51350f4637006078c23 EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Sun, 11 Aug 2024 21:28:10 -0000 https://status1.elastic.io/incident/412251#9ed5e00f926a12afbfc1e0ed18fe5f3d218e697f430230c16a7786ffb3439506 EU cluster WebHook went down. https://status1.elastic.io/incident/412251 Sun, 11 Aug 2024 20:53:30 -0000 https://status1.elastic.io/incident/412251#2ead2234f98b38f1c685d54bc3f54ba30054933952ee9755b9fa462d14f87f20 EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Sun, 11 Aug 2024 20:20:52 -0000 https://status1.elastic.io/incident/412251#eafaf4a0f3a49d11a96d1a3dde0a64038d55891998a7385743cf55a436db4263 EU cluster WebHook went down. https://status1.elastic.io/incident/412251 Sun, 11 Aug 2024 19:52:00 -0000 https://status1.elastic.io/incident/412251#0713eaac0b31e591ef38425cd82d49817d8dd613f23a9a33e1f51014e69d54fa EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Sun, 11 Aug 2024 19:22:39 -0000 https://status1.elastic.io/incident/412251#21339cc66ae3f6f9183d182ddc9197c79ca801c54410841b17786700f6abfc1c EU cluster WebHook went down. https://status1.elastic.io/incident/412251 Sun, 11 Aug 2024 18:41:23 -0000 https://status1.elastic.io/incident/412251#5cf9175be51f1eb25ac03323d756dfe5aaa2f12b1a9aba1175e0ef6a53ba6616 EU cluster WebHook recovered. https://status1.elastic.io/incident/412251 Sun, 11 Aug 2024 18:27:25 -0000 https://status1.elastic.io/incident/412251#e83b8c41d7e91d72f41bbf2babeae0e4d4b6aeda57f395e72464938606b8059b EU cluster WebHook went down. https://status1.elastic.io/incident/412251 Sun, 11 Aug 2024 17:43:10 -0000 https://status1.elastic.io/incident/412251#f632521e8e5e0cf85a7b339751772c9aa9614a7a82d9d28b85e7422bd5d2fde7 EU cluster Realtime went down. https://status1.elastic.io/incident/387393 Fri, 21 Jun 2024 07:03:10 -0000 https://status1.elastic.io/incident/387393#68ea6d8130b10b9734f6877fd2c6c506060afe0ddab4a50a71ab1fd6d8f9544d US cluster Realtime recovered. https://status1.elastic.io/incident/387393 Fri, 21 Jun 2024 06:58:10 -0000 https://status1.elastic.io/incident/387393#4da33614c6c46917e4066f0d931460d80587ebe483ba9bed6e9dc7cd9203350d US cluster API recovered. https://status1.elastic.io/incident/387393 Fri, 21 Jun 2024 06:56:42 -0000 https://status1.elastic.io/incident/387393#445903a33570af33c9c574acb1d722d6bc7afbbf21f791be1880aa3c402f709b US cluster frontend recovered. https://status1.elastic.io/incident/387393 Fri, 21 Jun 2024 06:50:12 -0000 https://status1.elastic.io/incident/387393#54c342ed1441cdb7982d5949d5daba039e21981b6e8f1711f576fbe37d5db36b US cluster API went down. https://status1.elastic.io/incident/387393 Fri, 21 Jun 2024 06:38:07 -0000 https://status1.elastic.io/incident/387393#37bcf4d65d8a83b5fc6a326ae937fcc1b438f0e18fa598be1be0b25428c5839a US cluster API recovered. https://status1.elastic.io/incident/387393 Fri, 21 Jun 2024 06:35:20 -0000 https://status1.elastic.io/incident/387393#ef089d5b41248eb8e51cffbbb0bd71d44c0655b2e36cb092e13a1665be4e21c8 US cluster Realtime went down. https://status1.elastic.io/incident/387393 Fri, 21 Jun 2024 06:31:50 -0000 https://status1.elastic.io/incident/387393#916b8bfeabb889bb0414ec761d53b9b37eabc238f39e9876b922a4ffdb1a9b23 US cluster API and US cluster frontend went down. https://status1.elastic.io/incident/387393 Fri, 21 Jun 2024 06:31:50 -0000 https://status1.elastic.io/incident/387393#916b8bfeabb889bb0414ec761d53b9b37eabc238f39e9876b922a4ffdb1a9b23 US cluster API and US cluster frontend went down. https://status1.elastic.io/incident/386859 Fri, 21 Jun 2024 06:30:00 +0000 https://status1.elastic.io/incident/386859#62de1f9c94369f43dac24d259fec64e670a0f54e9ff7b125aec038430d8f28eb Maintenance completed https://status1.elastic.io/incident/386859 Fri, 21 Jun 2024 06:30:00 +0000 https://status1.elastic.io/incident/386859#62de1f9c94369f43dac24d259fec64e670a0f54e9ff7b125aec038430d8f28eb Maintenance completed https://status1.elastic.io/incident/386859 Fri, 21 Jun 2024 06:30:00 +0000 https://status1.elastic.io/incident/386859#62de1f9c94369f43dac24d259fec64e670a0f54e9ff7b125aec038430d8f28eb Maintenance completed https://status1.elastic.io/incident/386859 Fri, 21 Jun 2024 06:00:00 -0000 https://status1.elastic.io/incident/386859#63c395f396d6a4963588d205bfb2cd5aca8cc8ded319f8e3b39ea2ffdd1e02e5 Due to the need for database replication, operations conducted on the US cluster may encounter downtime. No data loss is expected. The expected downtime duration is a maximum of 5 minutes. https://status1.elastic.io/incident/386859 Fri, 21 Jun 2024 06:00:00 -0000 https://status1.elastic.io/incident/386859#63c395f396d6a4963588d205bfb2cd5aca8cc8ded319f8e3b39ea2ffdd1e02e5 Due to the need for database replication, operations conducted on the US cluster may encounter downtime. No data loss is expected. The expected downtime duration is a maximum of 5 minutes. https://status1.elastic.io/incident/386859 Fri, 21 Jun 2024 06:00:00 -0000 https://status1.elastic.io/incident/386859#63c395f396d6a4963588d205bfb2cd5aca8cc8ded319f8e3b39ea2ffdd1e02e5 Due to the need for database replication, operations conducted on the US cluster may encounter downtime. No data loss is expected. The expected downtime duration is a maximum of 5 minutes. https://status1.elastic.io/incident/387147 Thu, 20 Jun 2024 19:03:43 -0000 https://status1.elastic.io/incident/387147#8b395b0fa8e065ee031022405b52524835cb985caca2524c1aee5d6fbbde0c55 EU cluster Realtime recovered. https://status1.elastic.io/incident/387147 Thu, 20 Jun 2024 18:59:42 -0000 https://status1.elastic.io/incident/387147#e2b9add51421efa0e7455794fccd9a183ca420b76b5db11d665019e37262c969 EU cluster Realtime went down. https://status1.elastic.io/incident/379835 Wed, 05 Jun 2024 10:40:32 -0000 https://status1.elastic.io/incident/379835#8e6cc3f8523dc1e03afdbc0cba25493a8b14e4b557dabf836922e488cd01cd47 AU cluster Realtime recovered. https://status1.elastic.io/incident/379835 Wed, 05 Jun 2024 10:34:16 -0000 https://status1.elastic.io/incident/379835#29c67e6bed251638661f08135a521919b1525d3e97fa52e41787441944a30934 AU cluster Realtime went down. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 14:14:08 -0000 https://status1.elastic.io/incident/375784#1fae4a3aec60966d70e126277d8feae7799e3d7af00a66b3c17b33566315ed6b US cluster Realtime recovered. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 14:04:10 -0000 https://status1.elastic.io/incident/375784#a5f3b75948e79fe9bee9e218e5fb91894414f81cdd75b148cdccb9098d68d191 US cluster Realtime went down. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 13:39:07 -0000 https://status1.elastic.io/incident/375784#1859126230993bd036b2410012df7654a69cf9db848f6385f365c8cbfae962f8 US cluster Realtime recovered. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 13:29:15 -0000 https://status1.elastic.io/incident/375784#5fa5b919f8b88b56af0d2d21585f88cd347f319e117fa89e34e0b67ef0d28432 US cluster Realtime went down. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 13:24:08 -0000 https://status1.elastic.io/incident/375784#2c8988eda338cc1afd8c63033eb1e255995057142332c58fd12b6ffcaf6c210a US cluster Realtime recovered. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 13:14:06 -0000 https://status1.elastic.io/incident/375784#63b0161b244c45b21e5ec78d3514070e7bd4a6a3445964779466edbf680ca9f0 US cluster Realtime went down. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 12:59:07 -0000 https://status1.elastic.io/incident/375784#d37bf3e2a05103e2c9a6e856ede7962c88726e579a18b12fdb8fec7ef51ac9ab US cluster Realtime recovered. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 12:49:12 -0000 https://status1.elastic.io/incident/375784#27227c987f4f2fb4335769b61259c1ff3298930e9a0c3b43b39c732210568acf US cluster Realtime went down. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 12:15:31 -0000 https://status1.elastic.io/incident/375784#60408114015420f841d2b92abbba5032bcf9e482922302da18b9da936d3d1049 US cluster Realtime recovered. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 12:10:00 -0000 https://status1.elastic.io/incident/375784#65822faffbaba7f8f659f003fa02232669b73c17cdbc383543f464a1764b0fa3 US cluster Realtime went down. https://status1.elastic.io/incident/375811 Tue, 28 May 2024 11:00:00 +0000 https://status1.elastic.io/incident/375811#95fdb9fd07f1b1b9c642ea918fb7afd70728fe61c501608763e2184d9603eae5 Maintenance completed https://status1.elastic.io/incident/375811 Tue, 28 May 2024 11:00:00 +0000 https://status1.elastic.io/incident/375811#95fdb9fd07f1b1b9c642ea918fb7afd70728fe61c501608763e2184d9603eae5 Maintenance completed https://status1.elastic.io/incident/375811 Tue, 28 May 2024 11:00:00 +0000 https://status1.elastic.io/incident/375811#95fdb9fd07f1b1b9c642ea918fb7afd70728fe61c501608763e2184d9603eae5 Maintenance completed https://status1.elastic.io/incident/375784 Tue, 28 May 2024 09:41:43 -0000 https://status1.elastic.io/incident/375784#d9d304eae39afbf51a1257717f44dba98fc2b419ee9563b2f0bd29d3241b02e3 US cluster Realtime recovered. https://status1.elastic.io/incident/375809 Tue, 28 May 2024 09:30:00 +0000 https://status1.elastic.io/incident/375809#d60d936df25358a97fbf96c8faa9092fdd01ae1d5e875072cfec4f545b9ec9c6 Maintenance completed https://status1.elastic.io/incident/375809 Tue, 28 May 2024 09:30:00 +0000 https://status1.elastic.io/incident/375809#d60d936df25358a97fbf96c8faa9092fdd01ae1d5e875072cfec4f545b9ec9c6 Maintenance completed https://status1.elastic.io/incident/375809 Tue, 28 May 2024 09:30:00 +0000 https://status1.elastic.io/incident/375809#d60d936df25358a97fbf96c8faa9092fdd01ae1d5e875072cfec4f545b9ec9c6 Maintenance completed https://status1.elastic.io/incident/375784 Tue, 28 May 2024 09:03:23 -0000 https://status1.elastic.io/incident/375784#9a8a43fc20ad55f6bcb372b070b19bc3c757a82f3d93f60ce826cb876e6aa546 US cluster frontend recovered. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 08:57:56 -0000 https://status1.elastic.io/incident/375784#629ef7d80ea0d3b51272eb90723463a5c1efdec37910610657b8ccf527fb1495 US cluster frontend went down. https://status1.elastic.io/incident/375784 Tue, 28 May 2024 08:44:11 -0000 https://status1.elastic.io/incident/375784#ed5e3896cc46672aa0f871acb161dd87fcf4fef0c26a07a9da39750efb62dfd7 US cluster Realtime went down. https://status1.elastic.io/incident/375809 Tue, 28 May 2024 08:30:00 -0000 https://status1.elastic.io/incident/375809#b620638d1f6a53b23cffcbfb242a97116e531109f21fb0d413bf31a4c36195a8 Kubernetes update on US cluster https://status1.elastic.io/incident/375809 Tue, 28 May 2024 08:30:00 -0000 https://status1.elastic.io/incident/375809#b620638d1f6a53b23cffcbfb242a97116e531109f21fb0d413bf31a4c36195a8 Kubernetes update on US cluster https://status1.elastic.io/incident/375809 Tue, 28 May 2024 08:30:00 -0000 https://status1.elastic.io/incident/375809#b620638d1f6a53b23cffcbfb242a97116e531109f21fb0d413bf31a4c36195a8 Kubernetes update on US cluster https://status1.elastic.io/incident/375811 Mon, 27 May 2024 22:00:00 -0000 https://status1.elastic.io/incident/375811#8e1a6ec3e955cd5c8cf2622d79751674fc73105b0eab32a0a9f85e73d62f93bf Kubernetes upgrade on AU cluster https://status1.elastic.io/incident/375811 Mon, 27 May 2024 22:00:00 -0000 https://status1.elastic.io/incident/375811#8e1a6ec3e955cd5c8cf2622d79751674fc73105b0eab32a0a9f85e73d62f93bf Kubernetes upgrade on AU cluster https://status1.elastic.io/incident/375811 Mon, 27 May 2024 22:00:00 -0000 https://status1.elastic.io/incident/375811#8e1a6ec3e955cd5c8cf2622d79751674fc73105b0eab32a0a9f85e73d62f93bf Kubernetes upgrade on AU cluster https://status1.elastic.io/incident/361789 Sun, 28 Apr 2024 06:48:24 -0000 https://status1.elastic.io/incident/361789#717d9a19320c94ed47479f9221846562031be787fb2c106c0d17c9052b65e7e7 US cluster Realtime recovered. https://status1.elastic.io/incident/361789 Sun, 28 Apr 2024 06:38:17 -0000 https://status1.elastic.io/incident/361789#8d28a3474af810dc223056b7bb2779be91b3bfe52d22c53c75d1cd8900438030 US cluster Realtime went down. https://status1.elastic.io/incident/361464 Sat, 27 Apr 2024 11:09:56 -0000 https://status1.elastic.io/incident/361464#4c4357278db89e28ee47e5ea42e8a5c3719b485fd53474f0fc76c7fdf761893e EU cluster WebHook recovered. https://status1.elastic.io/incident/361464 Sat, 27 Apr 2024 11:07:15 -0000 https://status1.elastic.io/incident/361464#6bacbd4b865b858fa217678fad919799d99a59ee792679ee5be1319f5a5aea1a EU cluster Realtime recovered. https://status1.elastic.io/incident/361464 Sat, 27 Apr 2024 10:33:59 -0000 https://status1.elastic.io/incident/361464#b4175279ee8e1051abe5b8d53e598002302e0fe7db1716b7c391aaf16cec7444 EU cluster WebHook went down. https://status1.elastic.io/incident/361464 Sat, 27 Apr 2024 10:26:26 -0000 https://status1.elastic.io/incident/361464#efbd6e506537c97e74b6e66f68dabfb9bde45e8226ecdc1189086c80e8ca8eb8 EU cluster Realtime went down. https://status1.elastic.io/incident/361464 Sat, 27 Apr 2024 08:56:01 -0000 https://status1.elastic.io/incident/361464#7bbac6659773a63db7ce5ec3ac9f47f00e6f5ed9de186646a83e77a0ea2439ac EU cluster Realtime recovered. https://status1.elastic.io/incident/361464 Sat, 27 Apr 2024 07:38:27 -0000 https://status1.elastic.io/incident/361464#425acb315b283fc69bfe27557ac4c6e5256b8d6f08faef1f8bd170eac060d3df EU cluster Realtime went down. https://status1.elastic.io/incident/354018 Thu, 11 Apr 2024 10:58:14 -0000 https://status1.elastic.io/incident/354018#cf0e2a8d4f906504e43c1932e1d985b817e2be04fd9aac938545952c15fe85c4 US cluster Realtime recovered. https://status1.elastic.io/incident/354018 Thu, 11 Apr 2024 10:13:10 -0000 https://status1.elastic.io/incident/354018#0e8f6c15b8838d686cbedb87d750ea2a3b0eb4280b469fb855905946236a5db3 US cluster Realtime went down. https://status1.elastic.io/incident/347805 Sat, 30 Mar 2024 11:29:58 -0000 https://status1.elastic.io/incident/347805#3e45dcb939c5d874e8dd56add08a09baa88281735339158168a202f03c63e028 EU cluster Realtime recovered. https://status1.elastic.io/incident/347805 Sat, 30 Mar 2024 10:36:14 -0000 https://status1.elastic.io/incident/347805#84f159784ead7534fc3d7aa27093f7f241511909e68b97613923939c0e7e0994 EU cluster Realtime went down. https://status1.elastic.io/incident/347805 Sat, 30 Mar 2024 10:28:47 -0000 https://status1.elastic.io/incident/347805#0426aa27c3c156878aff395625c3eaf2b1971ac37ddac4b29934b9774888dc52 EU cluster Realtime recovered. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 15:23:25 -0000 https://status1.elastic.io/incident/347805#be59c5a661085bd560d2f9bcb16daff5e70a66271f686243e84a4c261019bcb5 EU cluster WebHook recovered. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 15:20:19 -0000 https://status1.elastic.io/incident/347805#a3d08f0549ccc023db65f9fcf4b329d79022312b72cf66142c4692fcf94ef367 EU cluster API recovered. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 14:53:30 -0000 https://status1.elastic.io/incident/347805#a45f44ea095d2b76d40a21ca7cc7173c2336d4177f294d9bba3963d80e7f5eb3 EU cluster API went down. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 14:13:47 -0000 https://status1.elastic.io/incident/347805#bcf330682f7c9119a428e6ede487a0be30f49de0cfad04a68fa222bd69a49475 EU cluster Realtime went down. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 14:10:24 -0000 https://status1.elastic.io/incident/347805#28203cdf63729a3ab88f9acf7d2f1abfad3b22ae8d5ebb3bfcee8c913f098137 EU cluster WebHook went down. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 14:04:47 -0000 https://status1.elastic.io/incident/347805#8fd8d03d52768fd38e949326bc71b98c842f6b8fa252e9580d2faa4214168f05 EU cluster Realtime recovered. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 10:23:21 -0000 https://status1.elastic.io/incident/347805#dec0c0717586b4ffe18420e2416424f9afbcc87f2ddf89fbe1d50055abde4732 EU cluster frontend recovered. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 10:19:20 -0000 https://status1.elastic.io/incident/347805#6a5897315ec092097a2abfb3637b6e4a57ae6c012cff5bcf56d0f381f4a3b5e5 EU cluster frontend went down. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 09:32:28 -0000 https://status1.elastic.io/incident/347805#bc25d43c06571fe18c1d2d3336fbfc6532dc45bb033a1f614b700054de8e1887 EU cluster frontend recovered. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 09:21:23 -0000 https://status1.elastic.io/incident/347805#ae2e89843176f9c65399ae6433a211d3c93fec1d6a22ec9586524034b496b1bc EU cluster WebHook recovered. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 09:16:28 -0000 https://status1.elastic.io/incident/347805#4639fd8b2c15f228554cffbb36ff2631108b6350dff0cd8707fde68106542a7d EU cluster frontend went down. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 09:13:16 -0000 https://status1.elastic.io/incident/347805#8d3a13521e9040622c89c85cc2ea23d94cca50ff4e97d4e71c0add2ce76e643f EU cluster WebHook went down. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 08:38:18 -0000 https://status1.elastic.io/incident/347805#02ab62100435f406007913d9be075a22bd44bcfeec5a365ceb0b47ab44313d94 EU cluster frontend recovered. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 08:34:22 -0000 https://status1.elastic.io/incident/347805#9e4a1fb108684a2052ab93b8387133f46d08d3c3bdf80636ab786c5dd9b97c5e EU cluster frontend went down. https://status1.elastic.io/incident/347805 Fri, 29 Mar 2024 08:05:38 -0000 https://status1.elastic.io/incident/347805#aa4d1a295098b736838a13f53e7382b9d95c8e3d4a834ae6c61c6f2c0aa45727 EU cluster Realtime went down. https://status1.elastic.io/incident/347609 Thu, 28 Mar 2024 23:44:26 -0000 https://status1.elastic.io/incident/347609#0713f6ca55a5af7c7b8bcee531e0408a9dfb65d5228848dea82daf483a81b157 EU cluster Realtime recovered. https://status1.elastic.io/incident/347609 Thu, 28 Mar 2024 22:10:30 -0000 https://status1.elastic.io/incident/347609#1d593a96f1b3e70cc5fd4386aab8492a207679db4ef81be9a3fc67bda1e0c768 EU cluster Realtime went down. https://status1.elastic.io/incident/347424 Thu, 28 Mar 2024 15:09:13 -0000 https://status1.elastic.io/incident/347424#99020d5f87308f91b565c1d2a585c2c87953e0d1417b2590ec643224825f5a52 EU cluster Realtime recovered. https://status1.elastic.io/incident/347424 Thu, 28 Mar 2024 14:57:00 -0000 https://status1.elastic.io/incident/347424#c9e4c37886eae4a09390e3089671a8a125214655fe47306871cda57c3783bbbf Dear valued users, We regret to inform you that, as a result of unexpectedly high demand, our services are currently encountering delays in processing requests directed to services. Furthermore, there has been a noticeable decline in the velocity of container log retrieval. Rest assured, our dedicated team is diligently working to rectify these issues and restore optimal service performance in a timely manner. We sincerely appreciate your patience and understanding during this period of heightened activity. Elastic.io Support Team https://status1.elastic.io/incident/347424 Thu, 28 Mar 2024 14:13:51 -0000 https://status1.elastic.io/incident/347424#a349f63571d4b9b9242f97638d677dc3de4bffb65a73dd0b03d5077c16cc34eb EU cluster Realtime recovered. https://status1.elastic.io/incident/347424 Thu, 28 Mar 2024 14:12:47 -0000 https://status1.elastic.io/incident/347424#f25578ef877dee222366fdfd2beb4b6d8a94ce64152f2d913392898f7606b967 EU cluster Realtime went down. https://status1.elastic.io/incident/347424 Thu, 28 Mar 2024 13:43:20 -0000 https://status1.elastic.io/incident/347424#fac1aac3d57f233c773645b351f991e8daf92018697fbbb803e21ea668fa10fd EU cluster Realtime recovered. https://status1.elastic.io/incident/347424 Thu, 28 Mar 2024 13:37:07 -0000 https://status1.elastic.io/incident/347424#a72f5ea1ec440403f21493c06e9d5ee2c0eed501e560934c4c0ac6dcb1acaefc EU cluster Realtime went down. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 17:47:09 -0000 https://status1.elastic.io/incident/345860#c915c6fb53240bcf8dd23b16671d2f4310e369e78a67998afab08c90cad188f7 EU cluster Realtime recovered. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 17:27:56 -0000 https://status1.elastic.io/incident/345860#5d6afa58462376aaa1107a8e054e7617a74f84760f722b2d90eb4ee304e83247 EU cluster WebHook recovered. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 17:25:53 -0000 https://status1.elastic.io/incident/345860#1937e2c0de2aa2f575e7c16b7e8cd4313778a646a8f068476d6b5d184e9ef83b EU cluster API and EU cluster frontend recovered. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 17:25:53 -0000 https://status1.elastic.io/incident/345860#1937e2c0de2aa2f575e7c16b7e8cd4313778a646a8f068476d6b5d184e9ef83b EU cluster API and EU cluster frontend recovered. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 17:01:18 -0000 https://status1.elastic.io/incident/345860#fea41af1c089245c38f6a0e5e99aed1ec7f8c55927be70368a115802c4243ac4 EU cluster Realtime went down. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 16:57:02 -0000 https://status1.elastic.io/incident/345860#56a68fa1dfba60aafa57d58c66ffc5608d7125a9c3d222431d539f3612c7da29 EU cluster API went down. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 16:53:08 -0000 https://status1.elastic.io/incident/345860#57fe29e03273c0e907bdb1d56a23fe772455af93c8d8c41df406c727920a5668 EU cluster WebHook went down. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 16:52:12 -0000 https://status1.elastic.io/incident/345860#f23df74c2158d8e558baa346d9ff4e07837809fde215f88f920e56ad3a9aa5f4 EU cluster Realtime recovered. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 16:51:06 -0000 https://status1.elastic.io/incident/345860#1396c8184e30855ea601e201acbfe62789749c6f5c7dd27a39f89cb0fcd7a370 EU cluster API recovered. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 16:48:16 -0000 https://status1.elastic.io/incident/345860#efadf926e6b7c87f9b74058468483c40b68ff6f8797a5e1433473ceeb75f0e84 EU cluster Realtime went down. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 16:47:01 -0000 https://status1.elastic.io/incident/345860#fb3adab3c26767250a911bbe954bed26efb4f78227fca9e8c5c8ca7442ba817a EU cluster API went down. https://status1.elastic.io/incident/345860 Mon, 25 Mar 2024 16:45:51 -0000 https://status1.elastic.io/incident/345860#852f33d545ff6132f9a900da9cd7b0ee56bc8f7944aad6a2f0291e56547c8a57 EU cluster frontend went down. https://status1.elastic.io/incident/333681 Mon, 04 Mar 2024 09:15:41 -0000 https://status1.elastic.io/incident/333681#426e6fdaee86c4a5dcdafbc886559044be33b90e149bdf8450087277275a5de5 EU cluster Realtime recovered. https://status1.elastic.io/incident/333681 Thu, 29 Feb 2024 16:05:59 -0000 https://status1.elastic.io/incident/333681#173f43b3825932c89114dfcf218979cdeb3f94a15a881fc0bfdf7b9128e26d23 EU cluster Realtime went down. https://status1.elastic.io/incident/333681 Thu, 29 Feb 2024 11:32:25 -0000 https://status1.elastic.io/incident/333681#6bc0ea78268d680c3f408f50c13b3ba73454ceb89d99654d123650a602803f99 US cluster Realtime recovered. https://status1.elastic.io/incident/333681 Thu, 29 Feb 2024 11:28:50 -0000 https://status1.elastic.io/incident/333681#933171a9d9ac7e98b01acab0edc96438baf74f09681a2948355436bcce3a4cf7 US cluster API recovered. https://status1.elastic.io/incident/333681 Thu, 29 Feb 2024 11:23:23 -0000 https://status1.elastic.io/incident/333681#65cb6ab0155e5d2854f13a69a69a39801124975d11f70ffb1d35d983e4767073 US cluster API went down. https://status1.elastic.io/incident/333681 Thu, 29 Feb 2024 11:23:05 -0000 https://status1.elastic.io/incident/333681#3ab134b7ff56527abc97cc5cbcd33dde45e131de0ee1d257a46e8db945404f49 US cluster Realtime went down. https://status1.elastic.io/incident/333681 Thu, 29 Feb 2024 11:20:06 -0000 https://status1.elastic.io/incident/333681#136da22ca8e638ba4a1279bbdd5105b503a874c506747fc709c22ce7bcffec1a US cluster Realtime recovered. https://status1.elastic.io/incident/333681 Thu, 29 Feb 2024 11:11:32 -0000 https://status1.elastic.io/incident/333681#15c44a65c221ed8608f4c62a5ec31942638df484a6837415e00aad37a806f2f1 US cluster Realtime went down. https://status1.elastic.io/incident/318234 Fri, 26 Jan 2024 22:13:00 -0000 https://status1.elastic.io/incident/318234#bba8f6a6d3317a17d6d3d69f51349399d6f14f6321f1a2ab14802a34730c4a42 EU cluster Realtime recovered. https://status1.elastic.io/incident/318234 Fri, 26 Jan 2024 21:45:43 -0000 https://status1.elastic.io/incident/318234#32cbe8493a6f9c34adfad5b5b87d9955208996298476a46970860066c77e0fbb EU cluster Realtime went down. https://status1.elastic.io/incident/265631 Thu, 28 Sep 2023 17:19:41 -0000 https://status1.elastic.io/incident/265631#f8821020074e5e89aecf317a22284f17d478da64c1920b8a4e2c5481e5d5e591 EU cluster Realtime recovered. https://status1.elastic.io/incident/265631 Thu, 28 Sep 2023 17:15:24 -0000 https://status1.elastic.io/incident/265631#4784c517bf0616ad376452efb1ceccfa3d16c1250f73d1f46c67d8c20d770741 EU cluster Realtime went down. https://status1.elastic.io/incident/234803 Wed, 02 Aug 2023 16:00:00 +0000 https://status1.elastic.io/incident/234803#6d59cfccc046cbc00537ee0337d8ac418fdc2227c04f5b925620929d37871034 Maintenance completed https://status1.elastic.io/incident/234803 Wed, 02 Aug 2023 16:00:00 +0000 https://status1.elastic.io/incident/234803#6d59cfccc046cbc00537ee0337d8ac418fdc2227c04f5b925620929d37871034 Maintenance completed https://status1.elastic.io/incident/234803 Wed, 02 Aug 2023 16:00:00 +0000 https://status1.elastic.io/incident/234803#6d59cfccc046cbc00537ee0337d8ac418fdc2227c04f5b925620929d37871034 Maintenance completed https://status1.elastic.io/incident/234803 Wed, 02 Aug 2023 12:00:00 -0000 https://status1.elastic.io/incident/234803#59a11b562c079d4d83acf4e138fe0cd27c0366dddaf0a14686b8b2a57c0989c2 ClickHouse upgrade to v.21.8.14.5 https://status1.elastic.io/incident/234803 Wed, 02 Aug 2023 12:00:00 -0000 https://status1.elastic.io/incident/234803#59a11b562c079d4d83acf4e138fe0cd27c0366dddaf0a14686b8b2a57c0989c2 ClickHouse upgrade to v.21.8.14.5 https://status1.elastic.io/incident/234803 Wed, 02 Aug 2023 12:00:00 -0000 https://status1.elastic.io/incident/234803#59a11b562c079d4d83acf4e138fe0cd27c0366dddaf0a14686b8b2a57c0989c2 ClickHouse upgrade to v.21.8.14.5 https://status1.elastic.io/incident/225252 Tue, 27 Jun 2023 08:55:25 -0000 https://status1.elastic.io/incident/225252#fb0592f2c60ac287accb3c6d24791087e2a8744d22e3294cf922ad2fa4796d79 US cluster frontend recovered. https://status1.elastic.io/incident/225252 Tue, 27 Jun 2023 08:41:09 -0000 https://status1.elastic.io/incident/225252#4f34c3c446a19c82279cf69c0c2119efcb59619a322b9ec013a0de14bea32878 US cluster frontend went down. https://status1.elastic.io/incident/219498 Wed, 14 Jun 2023 17:00:00 +0000 https://status1.elastic.io/incident/219498#75717f515aa88b370f315102aa25b7afdf3b7f576942016365381ea083b0655d Maintenance completed https://status1.elastic.io/incident/219498 Wed, 14 Jun 2023 17:00:00 +0000 https://status1.elastic.io/incident/219498#75717f515aa88b370f315102aa25b7afdf3b7f576942016365381ea083b0655d Maintenance completed https://status1.elastic.io/incident/219498 Wed, 14 Jun 2023 17:00:00 +0000 https://status1.elastic.io/incident/219498#75717f515aa88b370f315102aa25b7afdf3b7f576942016365381ea083b0655d Maintenance completed https://status1.elastic.io/incident/219498 Wed, 14 Jun 2023 17:00:00 +0000 https://status1.elastic.io/incident/219498#75717f515aa88b370f315102aa25b7afdf3b7f576942016365381ea083b0655d Maintenance completed https://status1.elastic.io/incident/219498 Wed, 14 Jun 2023 14:00:00 -0000 https://status1.elastic.io/incident/219498#31aae868ca4f0fd54e039e6fd8169ec562d5783be89234155751bb1ec02fb343 As part of elastic.io's work to continually deliver new features and enhance our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our EU cluster. Date: 14th of June 2023, Wednesday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/219498 Wed, 14 Jun 2023 14:00:00 -0000 https://status1.elastic.io/incident/219498#31aae868ca4f0fd54e039e6fd8169ec562d5783be89234155751bb1ec02fb343 As part of elastic.io's work to continually deliver new features and enhance our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our EU cluster. Date: 14th of June 2023, Wednesday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/219498 Wed, 14 Jun 2023 14:00:00 -0000 https://status1.elastic.io/incident/219498#31aae868ca4f0fd54e039e6fd8169ec562d5783be89234155751bb1ec02fb343 As part of elastic.io's work to continually deliver new features and enhance our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our EU cluster. Date: 14th of June 2023, Wednesday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/219498 Wed, 14 Jun 2023 14:00:00 -0000 https://status1.elastic.io/incident/219498#31aae868ca4f0fd54e039e6fd8169ec562d5783be89234155751bb1ec02fb343 As part of elastic.io's work to continually deliver new features and enhance our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our EU cluster. Date: 14th of June 2023, Wednesday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/214184 Wed, 31 May 2023 13:29:56 -0000 https://status1.elastic.io/incident/214184#26908cb0565b80faedd879a4ccd9e58120ac06aacfa0cf07355fe773c3529c88 US cluster Realtime recovered. https://status1.elastic.io/incident/214184 Wed, 31 May 2023 13:22:08 -0000 https://status1.elastic.io/incident/214184#a7680d6501ff25e93cf6a5407d60a89e9998c38e4536bbe0311ee6d6521e6e40 US cluster Realtime went down. https://status1.elastic.io/incident/214184 Wed, 31 May 2023 12:34:04 -0000 https://status1.elastic.io/incident/214184#776d751cca9450f44cbfdfbce88a084decaaedd4fcd9e78d92dc632a8f248d0f US cluster Realtime recovered. https://status1.elastic.io/incident/214184 Wed, 31 May 2023 12:27:23 -0000 https://status1.elastic.io/incident/214184#1dabce2ea017049051dde4859069dad93f2bc9ae72496010a192e123fd49829a US cluster Realtime went down. https://status1.elastic.io/incident/214184 Wed, 31 May 2023 12:21:07 -0000 https://status1.elastic.io/incident/214184#26ee7ad1007b58102e638bf1d6bb6400fd5602ae2e1fc93bcb9fadbc58298de9 US cluster Realtime recovered. https://status1.elastic.io/incident/214184 Wed, 31 May 2023 12:14:28 -0000 https://status1.elastic.io/incident/214184#c642d6049575ca469c277c357b5cad6c9f6ec09e93b20da0a4b7d48b3f5f39b8 US cluster Realtime went down. https://status1.elastic.io/incident/213720 Wed, 31 May 2023 12:00:00 +0000 https://status1.elastic.io/incident/213720#59175eb94f7c3b3dd81de9ce9ab80631653e5063a80906b9b0354cd892167f85 Maintenance completed https://status1.elastic.io/incident/213720 Wed, 31 May 2023 12:00:00 +0000 https://status1.elastic.io/incident/213720#59175eb94f7c3b3dd81de9ce9ab80631653e5063a80906b9b0354cd892167f85 Maintenance completed https://status1.elastic.io/incident/213720 Wed, 31 May 2023 12:00:00 +0000 https://status1.elastic.io/incident/213720#59175eb94f7c3b3dd81de9ce9ab80631653e5063a80906b9b0354cd892167f85 Maintenance completed https://status1.elastic.io/incident/213720 Tue, 30 May 2023 22:00:00 -0000 https://status1.elastic.io/incident/213720#85b59b1b737ba91264ee5fa127167361d3450ad67108fc4c0fd9539d758279eb As part of elastic.io's work to continually deliver new features and enhance our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our US cluster. Date: 31th of May 2023, Wednesday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/213720 Tue, 30 May 2023 22:00:00 -0000 https://status1.elastic.io/incident/213720#85b59b1b737ba91264ee5fa127167361d3450ad67108fc4c0fd9539d758279eb As part of elastic.io's work to continually deliver new features and enhance our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our US cluster. Date: 31th of May 2023, Wednesday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/213720 Tue, 30 May 2023 22:00:00 -0000 https://status1.elastic.io/incident/213720#85b59b1b737ba91264ee5fa127167361d3450ad67108fc4c0fd9539d758279eb As part of elastic.io's work to continually deliver new features and enhance our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our US cluster. Date: 31th of May 2023, Wednesday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/212034 Thu, 25 May 2023 18:10:15 -0000 https://status1.elastic.io/incident/212034#9c7aeca518c9e2d706cda11b2c9b741294a970df2052b95027abb5c71a4c5f8d EU cluster Realtime recovered. https://status1.elastic.io/incident/212034 Thu, 25 May 2023 18:04:42 -0000 https://status1.elastic.io/incident/212034#8b4afefc62933123f5630730dc655af8d45dc78911945cf79bd249d32941d458 EU cluster Realtime went down. https://status1.elastic.io/incident/212034 Thu, 25 May 2023 17:28:46 -0000 https://status1.elastic.io/incident/212034#757369b2dcdd15c1a0d7910e83834b66269e74d3d54ee5e461c91eb54b5280fb EU cluster Realtime recovered. https://status1.elastic.io/incident/212034 Thu, 25 May 2023 17:00:43 -0000 https://status1.elastic.io/incident/212034#8e99ac52439ed00eb85876d202e9474ebe4750e959dfbbcf6b8f071dd28f05bd EU cluster Realtime went down. https://status1.elastic.io/incident/212007 Thu, 25 May 2023 17:00:00 +0000 https://status1.elastic.io/incident/212007#6a0059ebd1fbe546ade3259bdec1a80a0f3ada31087918f24a2488f4c2dea269 Maintenance completed https://status1.elastic.io/incident/212007 Thu, 25 May 2023 17:00:00 +0000 https://status1.elastic.io/incident/212007#6a0059ebd1fbe546ade3259bdec1a80a0f3ada31087918f24a2488f4c2dea269 Maintenance completed https://status1.elastic.io/incident/212007 Thu, 25 May 2023 17:00:00 +0000 https://status1.elastic.io/incident/212007#6a0059ebd1fbe546ade3259bdec1a80a0f3ada31087918f24a2488f4c2dea269 Maintenance completed https://status1.elastic.io/incident/212007 Thu, 25 May 2023 17:00:00 +0000 https://status1.elastic.io/incident/212007#6a0059ebd1fbe546ade3259bdec1a80a0f3ada31087918f24a2488f4c2dea269 Maintenance completed https://status1.elastic.io/incident/212007 Thu, 25 May 2023 15:00:00 -0000 https://status1.elastic.io/incident/212007#db99449dab3a16a7778cb09ed5dd17404e276a8c75f57dbf411a7935cf35858f As part of elastic.io's work to continually deliver new features and enhancing our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our European cluster. Date: 25th of May 2023, Thursday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/212007 Thu, 25 May 2023 15:00:00 -0000 https://status1.elastic.io/incident/212007#db99449dab3a16a7778cb09ed5dd17404e276a8c75f57dbf411a7935cf35858f As part of elastic.io's work to continually deliver new features and enhancing our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our European cluster. Date: 25th of May 2023, Thursday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/212007 Thu, 25 May 2023 15:00:00 -0000 https://status1.elastic.io/incident/212007#db99449dab3a16a7778cb09ed5dd17404e276a8c75f57dbf411a7935cf35858f As part of elastic.io's work to continually deliver new features and enhancing our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our European cluster. Date: 25th of May 2023, Thursday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/212007 Thu, 25 May 2023 15:00:00 -0000 https://status1.elastic.io/incident/212007#db99449dab3a16a7778cb09ed5dd17404e276a8c75f57dbf411a7935cf35858f As part of elastic.io's work to continually deliver new features and enhancing our platform, We occasionally need to schedule Maintenance for our services so that they can be upgraded and for you to get the most of our newly added services and features. One of these scheduled maintenance windows will be happening soon on our European cluster. Date: 25th of May 2023, Thursday Duration: 2 hours During this time, some of our services may not be available for a short period of several minutes. In addition, as individual Kubernetes pods are updated to the new version some flows may be momentarily delayed. This upgrade is necessary to ensure that we continue to provide the highest level of service to our customers, with improved stability and security. The Kubernetes upgrade will enable us to take advantage of the latest features and security enhancements, which will improve our overall system performance and help us better meet the needs of our customers. We understand that any maintenance downtime is inconvenient, and we will work to minimize the impact on your business operations. Our team will be monitoring the systems during the upgrade to ensure that everything runs smoothly. If you have any questions or concerns, please do not hesitate to contact our customer support team, who will be available throughout the maintenance period. If you need more information, and or have an objection on date/time of the maintenance, please do not hesitate to contact us immediately. https://status1.elastic.io/incident/206139 Thu, 11 May 2023 10:19:01 -0000 https://status1.elastic.io/incident/206139#56240d4cd8f60c8c7a242945189464ea040ab22c42817e9fd338e47ccced543e EU cluster API recovered. https://status1.elastic.io/incident/206139 Thu, 11 May 2023 10:17:49 -0000 https://status1.elastic.io/incident/206139#661b93ffa28592487345e2dd8ed89151083d913d76d57e0d4a43ed6f0ddab4f5 EU cluster API went down. https://status1.elastic.io/incident/206139 Thu, 11 May 2023 10:09:20 -0000 https://status1.elastic.io/incident/206139#cc41b550b0b201c9d8922bcee90ea57ccbfda301f3c148f41f281422496a9414 EU cluster Realtime recovered. https://status1.elastic.io/incident/206139 Thu, 11 May 2023 10:07:28 -0000 https://status1.elastic.io/incident/206139#94c1143ea5029a8403a710d435984549e71aee27065981e92f6270099090c463 EU cluster Realtime went down. https://status1.elastic.io/incident/200209 Tue, 25 Apr 2023 15:52:52 -0000 https://status1.elastic.io/incident/200209#f05abde61edea78d6fd979d97be27a8bb20ea33632884a4caa8ecb5cd38adb79 US cluster Realtime recovered. https://status1.elastic.io/incident/200209 Tue, 25 Apr 2023 15:44:35 -0000 https://status1.elastic.io/incident/200209#70d98a66439b8e40ff048b035a88e3de83ae5ea0e03c48567dad1aee53bf3550 US cluster Realtime went down. https://status1.elastic.io/incident/195805 Thu, 13 Apr 2023 09:11:54 -0000 https://status1.elastic.io/incident/195805#f3e0107d46538ed29296161c27ca1e8888da6e6dfeda23e249050d55b61e3579 US cluster Realtime recovered. https://status1.elastic.io/incident/195805 Thu, 13 Apr 2023 09:05:32 -0000 https://status1.elastic.io/incident/195805#2b6a7dc0623e581e1fba3ceb9e12ef985ac22cf44b46cc6fdca74db4bf7ce82a US cluster Realtime went down. https://status1.elastic.io/incident/191546 Fri, 31 Mar 2023 23:54:44 -0000 https://status1.elastic.io/incident/191546#f66e84c62619e1579be7d3f9abb827865749bf4661497b986e6301f9ab0e8d2d EU cluster WebHook recovered. https://status1.elastic.io/incident/191546 Fri, 31 Mar 2023 23:49:26 -0000 https://status1.elastic.io/incident/191546#d8ed4e22a2fa6d3d418225b68a43ca0b9b2196ed6023997dc6ac018940bfabfe EU cluster frontend recovered. https://status1.elastic.io/incident/191546 Fri, 31 Mar 2023 23:47:20 -0000 https://status1.elastic.io/incident/191546#e88b63fefb7becf798863eeecf8b84e4f6d623615d09fface0c685009576937e EU cluster Realtime recovered. https://status1.elastic.io/incident/191546 Fri, 31 Mar 2023 23:45:15 -0000 https://status1.elastic.io/incident/191546#6b5c5cfa4dca6e971b0e96f6c8c00a183ae0c2657c75b60da82755d6d8e5b1c1 EU cluster API recovered. https://status1.elastic.io/incident/191546 Fri, 31 Mar 2023 23:44:08 -0000 https://status1.elastic.io/incident/191546#49ca3cf9270dfad43f9c4028b41b8228ec52eeeafc9e86bf65ed6b11eb2d42c2 EU cluster Realtime went down. https://status1.elastic.io/incident/191546 Fri, 31 Mar 2023 23:42:25 -0000 https://status1.elastic.io/incident/191546#85eddaf54cc24e667adfd9ffbb145bd06dfb76808307a626b17d3be83a54bd98 EU cluster frontend and EU cluster WebHook went down. https://status1.elastic.io/incident/191546 Fri, 31 Mar 2023 23:42:25 -0000 https://status1.elastic.io/incident/191546#85eddaf54cc24e667adfd9ffbb145bd06dfb76808307a626b17d3be83a54bd98 EU cluster frontend and EU cluster WebHook went down. https://status1.elastic.io/incident/191546 Fri, 31 Mar 2023 23:40:54 -0000 https://status1.elastic.io/incident/191546#74e536c2a71b220946c3bd3e044a095f9b417616e58ff65ed9120f8b512f7119 EU cluster API went down. https://status1.elastic.io/incident/187547 Tue, 21 Mar 2023 17:45:14 -0000 https://status1.elastic.io/incident/187547#509d8e3bc81dc7c38deb710fa377bb1e5539cab046dbe2f17bad3d0c131560c5 EU cluster Realtime recovered. https://status1.elastic.io/incident/187547 Tue, 21 Mar 2023 16:55:24 -0000 https://status1.elastic.io/incident/187547#ef07e43d10b2e0eb1e805dc75f1efe58c1f249f9a52eba9811e50d4b7d414ce0 EU cluster Realtime went down. https://status1.elastic.io/incident/173784 Fri, 10 Feb 2023 14:51:04 -0000 https://status1.elastic.io/incident/173784#30f0b0979c2d51cf9bb503b423673e4917cb4700adf1fdba56eec3bdf997478c EU cluster frontend recovered. https://status1.elastic.io/incident/173784 Fri, 10 Feb 2023 14:47:05 -0000 https://status1.elastic.io/incident/173784#5a1e68505a300c5f2066684524fd4ac40371b80d4784e09d6f2d08e7b5e9fda6 EU cluster frontend went down. https://status1.elastic.io/incident/173498 Thu, 09 Feb 2023 21:09:52 -0000 https://status1.elastic.io/incident/173498#ab1105ddb1390c801fee6f4aef869eb4f495d8c9630c1a532a3e98bf06621707 EU cluster frontend recovered. https://status1.elastic.io/incident/173498 Thu, 09 Feb 2023 21:05:23 -0000 https://status1.elastic.io/incident/173498#780b06eb0c37b147c02347c0b198efbbefe11e622c127c622818efdab1f084a2 EU cluster frontend went down. https://status1.elastic.io/incident/173498 Thu, 09 Feb 2023 21:02:08 -0000 https://status1.elastic.io/incident/173498#04d41aac097bb38989e516e64880a1e34e67f3b0f552b259a40187e3f596326a EU cluster frontend recovered. https://status1.elastic.io/incident/173498 Thu, 09 Feb 2023 21:01:07 -0000 https://status1.elastic.io/incident/173498#bf2d291ab0c1a0f3e64eacc181c0565a8bc22d76e3e0ac63236c0199875805ea EU cluster API recovered. https://status1.elastic.io/incident/173498 Thu, 09 Feb 2023 20:56:58 -0000 https://status1.elastic.io/incident/173498#11dfc88372d39dc2c62819e6b5ca92469388ac3364dcf89c3520499b5991e431 EU cluster API went down. https://status1.elastic.io/incident/173498 Thu, 09 Feb 2023 20:55:51 -0000 https://status1.elastic.io/incident/173498#43b6e81726e9032bea894752037819e12908d5ab1a01f8d4d4f7c30828f0afa4 EU cluster frontend went down. https://status1.elastic.io/incident/170976 Thu, 02 Feb 2023 16:43:00 -0000 https://status1.elastic.io/incident/170976#7f82a94adeea528b4218355064dd661ce950a352dfec678e7e0a1133efe8afbb Two short periods of degraded service were experienced today between 15:51 and 15:57 CET and 16:13 and 16:21 CET. API, front-end, and webhook response rates were slow during this time and and some customers may have experienced time outs. No data loss resulted. The cause was due to flows abusing the storage (Maester) and queueing service limits. These flows have been suspended and we are working with the client to optimise their flows. All services are restored and working normally. Services within the US cluster were not affected. We apologise for the inconvenience https://status1.elastic.io/incident/170976 Thu, 02 Feb 2023 16:43:00 -0000 https://status1.elastic.io/incident/170976#7f82a94adeea528b4218355064dd661ce950a352dfec678e7e0a1133efe8afbb Two short periods of degraded service were experienced today between 15:51 and 15:57 CET and 16:13 and 16:21 CET. API, front-end, and webhook response rates were slow during this time and and some customers may have experienced time outs. No data loss resulted. The cause was due to flows abusing the storage (Maester) and queueing service limits. These flows have been suspended and we are working with the client to optimise their flows. All services are restored and working normally. Services within the US cluster were not affected. We apologise for the inconvenience https://status1.elastic.io/incident/170976 Thu, 02 Feb 2023 16:43:00 -0000 https://status1.elastic.io/incident/170976#7f82a94adeea528b4218355064dd661ce950a352dfec678e7e0a1133efe8afbb Two short periods of degraded service were experienced today between 15:51 and 15:57 CET and 16:13 and 16:21 CET. API, front-end, and webhook response rates were slow during this time and and some customers may have experienced time outs. No data loss resulted. The cause was due to flows abusing the storage (Maester) and queueing service limits. These flows have been suspended and we are working with the client to optimise their flows. All services are restored and working normally. Services within the US cluster were not affected. We apologise for the inconvenience https://status1.elastic.io/incident/170976 Thu, 02 Feb 2023 16:43:00 -0000 https://status1.elastic.io/incident/170976#7f82a94adeea528b4218355064dd661ce950a352dfec678e7e0a1133efe8afbb Two short periods of degraded service were experienced today between 15:51 and 15:57 CET and 16:13 and 16:21 CET. API, front-end, and webhook response rates were slow during this time and and some customers may have experienced time outs. No data loss resulted. The cause was due to flows abusing the storage (Maester) and queueing service limits. These flows have been suspended and we are working with the client to optimise their flows. All services are restored and working normally. Services within the US cluster were not affected. We apologise for the inconvenience https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 15:21:37 -0000 https://status1.elastic.io/incident/170938#a0c6ce3527e4c98e12c5861dd239b7baf281b9384de054c7b388b48d0095ad47 EU cluster frontend recovered. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 15:20:50 -0000 https://status1.elastic.io/incident/170938#a0c486a4b9dd32d0f9728c46fa383a2d46f35514aa5778de502306b8d81e8d1e EU cluster API recovered. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 15:20:42 -0000 https://status1.elastic.io/incident/170938#ffa276304bb6f2495ecf312b196d185928c1eeb3672ada3b05c6b89776f2cd70 EU cluster Realtime recovered. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 15:14:43 -0000 https://status1.elastic.io/incident/170938#31d581a67db2760931c4e4f518578c3aa5cd08b134239b1950f79a3451ef1337 EU cluster API went down. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 15:14:03 -0000 https://status1.elastic.io/incident/170938#7191d0cd308365e1337e1834db90c02b7edfa5c6d134b89d63c314ad4e91f106 EU cluster Realtime went down. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 15:13:40 -0000 https://status1.elastic.io/incident/170938#b7cbda8fe09b6b4dfbb93682a9d4cbac58fba61d603eb2bdfdf141827a6e0b3f EU cluster frontend went down. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 14:57:40 -0000 https://status1.elastic.io/incident/170938#7b7eba0ca72527c9c73daa411fc597c22ffd84b1e07b80a85ca4c37c742639bd EU cluster frontend recovered. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 14:56:06 -0000 https://status1.elastic.io/incident/170938#ddcb75617ac2618d83bacf25aa3078738f41db9ccd69f174aac045fc124de79e EU cluster Realtime recovered. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 14:55:51 -0000 https://status1.elastic.io/incident/170938#c762e526102d4bd5a5a08997823a432323f177e90a625fbb5833f2b4906c4342 EU cluster API recovered. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 14:52:04 -0000 https://status1.elastic.io/incident/170938#73a8c2fcd3e7fccdb66fa570d5bc16137cc3a2be3e26c02a8bbdf7b9b830b02a EU cluster Realtime went down. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 14:51:46 -0000 https://status1.elastic.io/incident/170938#124b36545a256dde16b466ba8e661c2a7d05140041a9c8590ac265385d06b645 EU cluster API went down. https://status1.elastic.io/incident/170938 Thu, 02 Feb 2023 14:51:24 -0000 https://status1.elastic.io/incident/170938#0436245addf7db8f3caf9849f7d65f1b014fb20b02f2b6284525c8c8b1407f47 EU cluster frontend went down. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 18:58:04 -0000 https://status1.elastic.io/incident/170601#54d2b28e7d7800cec62985fa5d0527fe971507a71ab30bdfc609346b0732ca25 EU cluster frontend recovered. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 18:57:43 -0000 https://status1.elastic.io/incident/170601#c44c29288637cd38de541d67f59cdd6884e30d615bbfd207f24c8692fb4a9591 EU cluster Realtime recovered. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 18:56:52 -0000 https://status1.elastic.io/incident/170601#b6d7d475ffb65de7771635b610337139397ff28d6e1c113c06b8344358f1c538 EU cluster API recovered. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 18:53:40 -0000 https://status1.elastic.io/incident/170601#76b7ca21315d88248e32c6a23a19421d926351235485dc78e3bf5bcbaf679506 EU cluster Realtime went down. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 18:53:09 -0000 https://status1.elastic.io/incident/170601#79a03fad33b2eac03f662e4a6460b51f6d6909118b1e555b432a1124807b3d9b EU cluster API went down. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 18:52:02 -0000 https://status1.elastic.io/incident/170601#33bc09beb20671e66b0f8ef5fa011b9cbbc83d1753a0d8f067170ab9a4937b82 EU cluster frontend went down. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 18:45:59 -0000 https://status1.elastic.io/incident/170601#11297262d6dfff811beb86e056711b6f59967f8a02968ea1fe25159a9e1315fc EU cluster frontend recovered. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 18:41:06 -0000 https://status1.elastic.io/incident/170601#83bd28e32a2ac3f9e43b9dffd293954892ceb686d75a2df4d0c3a7ee08047d63 EU cluster frontend went down. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 18:06:01 -0000 https://status1.elastic.io/incident/170601#0f5ffc891b4c4cc7f153f993a8936d990edab33e0f46629e13fad47be9f1eea8 EU cluster frontend recovered. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 18:01:57 -0000 https://status1.elastic.io/incident/170601#844949d5fb38ff7ae6cdb97db0ec7d7ba31dc4c4920d6fe81e36452d9b3895d8 EU cluster frontend went down. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 17:58:01 -0000 https://status1.elastic.io/incident/170601#ab66da1e68f61694f8a3b1c053bdbdb35a67a2172e85d42dcf47c749cec507ad EU cluster frontend recovered. https://status1.elastic.io/incident/170601 Wed, 01 Feb 2023 17:52:58 -0000 https://status1.elastic.io/incident/170601#41dba23512bb84945810638906a843a1af581f72826f08efe98ea49d0c37da34 EU cluster frontend went down. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 19:10:01 -0000 https://status1.elastic.io/incident/170218#32541d9629d804b37e379c6c5afea785d3bc822605bf792d6ab38205bb32a1ae EU cluster frontend recovered. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 19:08:56 -0000 https://status1.elastic.io/incident/170218#14a932e3803b60a52feb457d05ae0e3d360652a9d7b2cca57fa8df0aedb46830 EU cluster API and EU cluster Realtime recovered. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 19:08:56 -0000 https://status1.elastic.io/incident/170218#14a932e3803b60a52feb457d05ae0e3d360652a9d7b2cca57fa8df0aedb46830 EU cluster API and EU cluster Realtime recovered. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 19:05:16 -0000 https://status1.elastic.io/incident/170218#fbcfb8a746196a2fb5c991cc60ea620eebfb967fdb65579114c95b1e80600cca EU cluster API went down. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 19:04:17 -0000 https://status1.elastic.io/incident/170218#746cd0b620a62c1ae3e835fdcc927bde72ba845e7032031c9cc2b9afc8db4016 EU cluster Realtime went down. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 19:03:44 -0000 https://status1.elastic.io/incident/170218#4704a91fc29d7a78e1f9310f1ebcc07d861357d67eabcb7053c0c2347d976ae9 EU cluster frontend went down. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 18:56:48 -0000 https://status1.elastic.io/incident/170218#79c909eeb0b58b04748c3bbf1660231693de0f3f54f845b0b2481b8c64c4295a EU cluster frontend recovered. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 18:55:32 -0000 https://status1.elastic.io/incident/170218#e916aa65db71d83a64499fa08effb4e3d4ade17b56643810a56835669820b019 EU cluster API recovered. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 18:55:28 -0000 https://status1.elastic.io/incident/170218#775297640347b7e258643f238f687bb278e2edf49aeb61bfb228b4b36c1032d5 EU cluster Realtime recovered. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 18:51:26 -0000 https://status1.elastic.io/incident/170218#c9793dec169851864b76041861e1e4296ec245c321197fc24d44f77df8b21158 EU cluster Realtime went down. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 18:51:08 -0000 https://status1.elastic.io/incident/170218#5c4d3c1e099999af93c2e0c5b41e658bd0414884578f1a62ab0f0cddf1b12650 EU cluster API went down. https://status1.elastic.io/incident/170218 Tue, 31 Jan 2023 18:50:35 -0000 https://status1.elastic.io/incident/170218#4e264715b146df4f4642edf8211c8986a249a01e0e3a718d37fac7b287d8aa1c EU cluster frontend went down. https://status1.elastic.io/incident/166598 Mon, 23 Jan 2023 10:21:00 -0000 https://status1.elastic.io/incident/166598#5ca284143315f9fd923259cf0f0e29893a3c5f59bcc7ce6b974a6ffd38c76ad0 # Post-mortem ## Issue On Friday 20th Jan, 2023 a significant spike in data volume was observed, this spike was also accompanied by an increase in data package size. The following increase in data processing times, increased message queue processing times and data volume combined to overwhelm our Kubernetes master node. At 16:02 CET, the platform service became unavailable. Google support where unable to correct this and so it was necessary to recreate the platform. During the downtime, our Webhook and queueing system remained available, except for brief periods during relaunching platform versions. Status / Resolution At 02:53 CET on Saturday 21 Jan, 2023 a stable version of the platform was relaunched. Due to the huge load increase, plus the backlog of messages, it was necessary to re-start integration flows in phases while monitoring platform health. The last phase of flow re-starts occurred at 10:00 CET on Saturday 21 Jan, 2023. ## Prevention / Corrective Actions Preventing these issues in the future will be achieved by the pending upgrade of our core scheduling service. Implementation is scheduled for mid-February 2023. In addition, we will work with clients to optimise their integration flow design to avoid such instances and possibly migrating higher volume clients to a separate elastic.io instance. We apologise sincerely for any inconvenience and thank you for your trust in [elastic.io](https://www.elastic.io) https://status1.elastic.io/incident/166598 Sat, 21 Jan 2023 02:00:00 -0000 https://status1.elastic.io/incident/166598#d46b5fae888829bcef5b56d79c85c410baeeeb3056ace35d30dbd85ede062a66 EU cluster RealtimThe platform is re-launched and service is resumed. Unfortunately with reduced capacity. Significant delays in processing data are to be expected, especially where message sizes are large. Data loss is believed to be minimal - our webhook and queueing system were down only shortly while redeploying platform versions. We apologise sincerely for the disruption in service and will continue to monitor and optimise over the weekend. Delays in data processing are to be expected over the weekend as we work to clear the message backlog. Kind regards Your elastic.io Teame recovered. https://status1.elastic.io/incident/166598 Sat, 21 Jan 2023 00:30:07 -0000 https://status1.elastic.io/incident/166598#26f51670613a48201bef1f8a4051ee457041f141e03a7df413242f2e10be78bf EU cluster WebHook recovered. https://status1.elastic.io/incident/166598 Sat, 21 Jan 2023 00:28:21 -0000 https://status1.elastic.io/incident/166598#b2a7aaca19bdb8761f7cdd0eec9bc0e86fbaa666dfcacf58f286a06921a98d72 EU cluster API recovered. https://status1.elastic.io/incident/166598 Sat, 21 Jan 2023 00:28:17 -0000 https://status1.elastic.io/incident/166598#2f680fa607ef51682d0aba5b14b02af660766ad487fca82271c918fae809a8b2 EU cluster frontend recovered. https://status1.elastic.io/incident/166598 Sat, 21 Jan 2023 00:19:54 -0000 https://status1.elastic.io/incident/166598#92286943f3427cf46463dfedd978a320078bdbe34d1ffc65c3ab73be23cd46ba EU cluster WebHook went down. https://status1.elastic.io/incident/166598 Sat, 21 Jan 2023 00:18:54 -0000 https://status1.elastic.io/incident/166598#f48e23c0be1677ad11f2ca3c0c745f48652b5e5df10e1111c58813203ba6c238 EU cluster frontend went down. https://status1.elastic.io/incident/166598 Sat, 21 Jan 2023 00:18:52 -0000 https://status1.elastic.io/incident/166598#607329bce5dc8a0d3fcaca79318808d56fdce1deb16bde44680bbcd65fc52dfc EU cluster API went down. https://status1.elastic.io/incident/166598 Fri, 20 Jan 2023 23:06:01 -0000 https://status1.elastic.io/incident/166598#90962632b88f611be25707e48ef19838bae418903bcb8a9823fc50a601baf185 EU cluster Realtime went down. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 21:59:00 -0000 https://status1.elastic.io/incident/166491#4f1a65cf762e1060ea93a6a1c905e0c2a0a17a58a9937a76de4e8b9831bca869 Most of the flows have started. We are monitoring the situation. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 21:59:00 -0000 https://status1.elastic.io/incident/166491#4f1a65cf762e1060ea93a6a1c905e0c2a0a17a58a9937a76de4e8b9831bca869 Most of the flows have started. We are monitoring the situation. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 21:59:00 -0000 https://status1.elastic.io/incident/166491#4f1a65cf762e1060ea93a6a1c905e0c2a0a17a58a9937a76de4e8b9831bca869 Most of the flows have started. We are monitoring the situation. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 21:59:00 -0000 https://status1.elastic.io/incident/166491#4f1a65cf762e1060ea93a6a1c905e0c2a0a17a58a9937a76de4e8b9831bca869 Most of the flows have started. We are monitoring the situation. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 21:31:00 -0000 https://status1.elastic.io/incident/166491#f8e09010d60c64b69f9f362fe51094f980755ae6103d50fdd275665bc2ac1581 We are starting the integration flows in batches. System is stable. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 21:31:00 -0000 https://status1.elastic.io/incident/166491#f8e09010d60c64b69f9f362fe51094f980755ae6103d50fdd275665bc2ac1581 We are starting the integration flows in batches. System is stable. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 21:31:00 -0000 https://status1.elastic.io/incident/166491#f8e09010d60c64b69f9f362fe51094f980755ae6103d50fdd275665bc2ac1581 We are starting the integration flows in batches. System is stable. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 21:31:00 -0000 https://status1.elastic.io/incident/166491#f8e09010d60c64b69f9f362fe51094f980755ae6103d50fdd275665bc2ac1581 We are starting the integration flows in batches. System is stable. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 20:58:00 -0000 https://status1.elastic.io/incident/166491#d7532ad940e45cb2abf7ebdf59963f3a1574906136096beae96a1b57d4e4d1ae The platform remains down and rebuilding is taking longer than expected. The team is working full speed to re-launch the platform. Thank you for your patience. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 20:58:00 -0000 https://status1.elastic.io/incident/166491#d7532ad940e45cb2abf7ebdf59963f3a1574906136096beae96a1b57d4e4d1ae The platform remains down and rebuilding is taking longer than expected. The team is working full speed to re-launch the platform. Thank you for your patience. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 20:58:00 -0000 https://status1.elastic.io/incident/166491#d7532ad940e45cb2abf7ebdf59963f3a1574906136096beae96a1b57d4e4d1ae The platform remains down and rebuilding is taking longer than expected. The team is working full speed to re-launch the platform. Thank you for your patience. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 20:58:00 -0000 https://status1.elastic.io/incident/166491#d7532ad940e45cb2abf7ebdf59963f3a1574906136096beae96a1b57d4e4d1ae The platform remains down and rebuilding is taking longer than expected. The team is working full speed to re-launch the platform. Thank you for your patience. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 19:16:00 -0000 https://status1.elastic.io/incident/166491#d3d834c7e260654f8fa94c4e6eb1a79fe67b9518feb8207dd8d89afa083fd782 We have re-created the cluster and recovering the integration flows. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 19:16:00 -0000 https://status1.elastic.io/incident/166491#d3d834c7e260654f8fa94c4e6eb1a79fe67b9518feb8207dd8d89afa083fd782 We have re-created the cluster and recovering the integration flows. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 19:16:00 -0000 https://status1.elastic.io/incident/166491#d3d834c7e260654f8fa94c4e6eb1a79fe67b9518feb8207dd8d89afa083fd782 We have re-created the cluster and recovering the integration flows. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 19:16:00 -0000 https://status1.elastic.io/incident/166491#d3d834c7e260654f8fa94c4e6eb1a79fe67b9518feb8207dd8d89afa083fd782 We have re-created the cluster and recovering the integration flows. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 17:44:00 -0000 https://status1.elastic.io/incident/166491#8e2f1a40fc8a2ed8f8ceaba2813207117901ecdf399687a9c8605245945a8ebf The issue is with our Kubernetes Master node. We have been working with Google support to find a solution and we are now rebuilding the platform and hope to be in full service mode asap. We are doing everything possible to minimise any possible data loss. We will keep you informed as situation improves. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 17:44:00 -0000 https://status1.elastic.io/incident/166491#8e2f1a40fc8a2ed8f8ceaba2813207117901ecdf399687a9c8605245945a8ebf The issue is with our Kubernetes Master node. We have been working with Google support to find a solution and we are now rebuilding the platform and hope to be in full service mode asap. We are doing everything possible to minimise any possible data loss. We will keep you informed as situation improves. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 17:44:00 -0000 https://status1.elastic.io/incident/166491#8e2f1a40fc8a2ed8f8ceaba2813207117901ecdf399687a9c8605245945a8ebf The issue is with our Kubernetes Master node. We have been working with Google support to find a solution and we are now rebuilding the platform and hope to be in full service mode asap. We are doing everything possible to minimise any possible data loss. We will keep you informed as situation improves. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 17:44:00 -0000 https://status1.elastic.io/incident/166491#8e2f1a40fc8a2ed8f8ceaba2813207117901ecdf399687a9c8605245945a8ebf The issue is with our Kubernetes Master node. We have been working with Google support to find a solution and we are now rebuilding the platform and hope to be in full service mode asap. We are doing everything possible to minimise any possible data loss. We will keep you informed as situation improves. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 17:26:00 -0000 https://status1.elastic.io/incident/166491#d1207b5178a367c9dbd8a96de1d90ccde07e689aa04f34a18a354b6d04cbe789 Currently we are in the middle of recovery. By our estimation it would be another 2 hours until the platform is operational. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 17:26:00 -0000 https://status1.elastic.io/incident/166491#d1207b5178a367c9dbd8a96de1d90ccde07e689aa04f34a18a354b6d04cbe789 Currently we are in the middle of recovery. By our estimation it would be another 2 hours until the platform is operational. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 17:26:00 -0000 https://status1.elastic.io/incident/166491#d1207b5178a367c9dbd8a96de1d90ccde07e689aa04f34a18a354b6d04cbe789 Currently we are in the middle of recovery. By our estimation it would be another 2 hours until the platform is operational. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 17:26:00 -0000 https://status1.elastic.io/incident/166491#d1207b5178a367c9dbd8a96de1d90ccde07e689aa04f34a18a354b6d04cbe789 Currently we are in the middle of recovery. By our estimation it would be another 2 hours until the platform is operational. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:49:00 -0000 https://status1.elastic.io/incident/166491#e5bd47aa319696e64d909b26167fbba99400d151688b9bfe189f2ab200edadd5 We are in touch with Google support to resolve this a.s.a.p. - Kubernetes API server seems to be the issue https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:49:00 -0000 https://status1.elastic.io/incident/166491#e5bd47aa319696e64d909b26167fbba99400d151688b9bfe189f2ab200edadd5 We are in touch with Google support to resolve this a.s.a.p. - Kubernetes API server seems to be the issue https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:49:00 -0000 https://status1.elastic.io/incident/166491#e5bd47aa319696e64d909b26167fbba99400d151688b9bfe189f2ab200edadd5 We are in touch with Google support to resolve this a.s.a.p. - Kubernetes API server seems to be the issue https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:49:00 -0000 https://status1.elastic.io/incident/166491#e5bd47aa319696e64d909b26167fbba99400d151688b9bfe189f2ab200edadd5 We are in touch with Google support to resolve this a.s.a.p. - Kubernetes API server seems to be the issue https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:14:00 -0000 https://status1.elastic.io/incident/166491#615b58d5712070a374550c2fca53cdde7a27388db39b209d676e03b71c45b602 We are having problems connected with the Google Cloud Platform Kubernetes engine. All our services are affected. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:14:00 -0000 https://status1.elastic.io/incident/166491#615b58d5712070a374550c2fca53cdde7a27388db39b209d676e03b71c45b602 We are having problems connected with the Google Cloud Platform Kubernetes engine. All our services are affected. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:14:00 -0000 https://status1.elastic.io/incident/166491#615b58d5712070a374550c2fca53cdde7a27388db39b209d676e03b71c45b602 We are having problems connected with the Google Cloud Platform Kubernetes engine. All our services are affected. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:14:00 -0000 https://status1.elastic.io/incident/166491#615b58d5712070a374550c2fca53cdde7a27388db39b209d676e03b71c45b602 We are having problems connected with the Google Cloud Platform Kubernetes engine. All our services are affected. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:02:54 -0000 https://status1.elastic.io/incident/166491#c8afc1b2d3fd72fe32d2350c76df8475124394efaad4cc3c54587ddffdb3389e EU cluster Realtime went down. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:02:52 -0000 https://status1.elastic.io/incident/166491#a0e6b7c0209157e855be0271fb78351f4367b65ec680314c698d2c12d3d48938 EU cluster API went down. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:02:24 -0000 https://status1.elastic.io/incident/166491#d24be38f2c5bf6735adfb632c9381f23231a720565a7e4942ef032f9b2712e7b EU cluster frontend went down. https://status1.elastic.io/incident/166491 Fri, 20 Jan 2023 15:02:22 -0000 https://status1.elastic.io/incident/166491#36f5537b6039efaac2347bf0ea7a9e9b89bc94c0d7ef722aba78dbca247ad18a EU cluster WebHook went down. https://status1.elastic.io/incident/165671 Thu, 05 Jan 2023 17:02:00 -0000 https://status1.elastic.io/incident/165671#2f5346eed230edb4591b0d7128db56023412c13dc48a2bf687035f88737086e7 Flow sample retrieval is not working ## Issue The recent issues experienced in the platform are because of our core scheduling service becoming temporarily overwhelmed because of a high volume of messages combined with many errors generated by integration flows transporting large batches of data. Issues experienced included: * Slow and failing sample retrieval * Slow processing of message queues ## Status/Resolution The issues are now resolved, and no data loss is observed or reported. ## Prevention/Corrective Actions Preventing these issues in the future will be achieved by the pending upgrade of our core scheduling service. Implementation is scheduled for mid-February 2023. In addition, we will work with clients to optimise their integration flow design to avoid such instances. We apologise sincerely for any inconvenience and thank you for your trust in [elastic.io](https://www.elastic.io) https://status1.elastic.io/incident/165671 Thu, 05 Jan 2023 11:29:00 -0000 https://status1.elastic.io/incident/165671#8775637c79217eb92639d6e68ba53c46dfdc4dc366e48e28fdf672cbd362ed7b A fix has been implemented and we are monitoring the results. https://status1.elastic.io/incident/165671 Thu, 05 Jan 2023 10:52:00 -0000 https://status1.elastic.io/incident/165671#0577b3fdf0a1f88dd6699ed04593b01df806382e411d09e11176885658e487b9 The issue has been identified and a fix is being implemented. https://status1.elastic.io/incident/165671 Thu, 05 Jan 2023 10:26:00 -0000 https://status1.elastic.io/incident/165671#d0f50e08606b639678f0094756e418d941f8e1efc32ec86553c83b41b6a556b9 We are investigating the problem of flow sample retrieval. https://status1.elastic.io/incident/165670 Fri, 30 Dec 2022 07:30:00 -0000 https://status1.elastic.io/incident/165670#a3352a499433bee884720e2887dbf267d6f86c63cb90d0c5b4799b86271a505c Slow Webhook transactions and Maester requests ## Issue Significantly increased platform load was experienced from 23:40 CET on 29.12.2023. Speed of message processing was affected. The condition remained stable, but slow until sporadic time-outs began to occur for Webhook and Maester requests. At 07:30 CET on 30.12.2022 webhook and Maester requests began to fail. ## Status/Resolution The issue was resolved at 08:14 CET on 30.12.2022 by scaling system services to cope with the increased load. No data loss has been identified. ## Prevention/Corrective actions More refined monitoring is being implemented to provide more advanced warning of load issues. The services concerned have been expanded to accommodate increased load. We apologise sincerely for any inconvenience and thank you for your trust in [elastic.io](https://www.elastic.io) https://status1.elastic.io/incident/165670 Fri, 30 Dec 2022 07:30:00 -0000 https://status1.elastic.io/incident/165670#a3352a499433bee884720e2887dbf267d6f86c63cb90d0c5b4799b86271a505c Slow Webhook transactions and Maester requests ## Issue Significantly increased platform load was experienced from 23:40 CET on 29.12.2023. Speed of message processing was affected. The condition remained stable, but slow until sporadic time-outs began to occur for Webhook and Maester requests. At 07:30 CET on 30.12.2022 webhook and Maester requests began to fail. ## Status/Resolution The issue was resolved at 08:14 CET on 30.12.2022 by scaling system services to cope with the increased load. No data loss has been identified. ## Prevention/Corrective actions More refined monitoring is being implemented to provide more advanced warning of load issues. The services concerned have been expanded to accommodate increased load. We apologise sincerely for any inconvenience and thank you for your trust in [elastic.io](https://www.elastic.io) https://status1.elastic.io/incident/165670 Fri, 30 Dec 2022 07:30:00 -0000 https://status1.elastic.io/incident/165670#a3352a499433bee884720e2887dbf267d6f86c63cb90d0c5b4799b86271a505c Slow Webhook transactions and Maester requests ## Issue Significantly increased platform load was experienced from 23:40 CET on 29.12.2023. Speed of message processing was affected. The condition remained stable, but slow until sporadic time-outs began to occur for Webhook and Maester requests. At 07:30 CET on 30.12.2022 webhook and Maester requests began to fail. ## Status/Resolution The issue was resolved at 08:14 CET on 30.12.2022 by scaling system services to cope with the increased load. No data loss has been identified. ## Prevention/Corrective actions More refined monitoring is being implemented to provide more advanced warning of load issues. The services concerned have been expanded to accommodate increased load. We apologise sincerely for any inconvenience and thank you for your trust in [elastic.io](https://www.elastic.io) https://status1.elastic.io/incident/165670 Fri, 30 Dec 2022 07:14:00 -0000 https://status1.elastic.io/incident/165670#9b0f93391063edac9e253f4362385a6743d1a0cde7e25d5551b13616faace704 The issue was resolved by scaling platform caching services to increase processing speed. https://status1.elastic.io/incident/165670 Fri, 30 Dec 2022 07:14:00 -0000 https://status1.elastic.io/incident/165670#9b0f93391063edac9e253f4362385a6743d1a0cde7e25d5551b13616faace704 The issue was resolved by scaling platform caching services to increase processing speed. https://status1.elastic.io/incident/165670 Fri, 30 Dec 2022 07:14:00 -0000 https://status1.elastic.io/incident/165670#9b0f93391063edac9e253f4362385a6743d1a0cde7e25d5551b13616faace704 The issue was resolved by scaling platform caching services to increase processing speed. https://status1.elastic.io/incident/165670 Fri, 30 Dec 2022 06:30:00 -0000 https://status1.elastic.io/incident/165670#2725bf014a19f81fcd8cde7ac094c0f55e87b1bc51fb7423bc1a91af25d6f119 Webhook executions and requests to our storage service Maester were timing out due to slow responses. https://status1.elastic.io/incident/165670 Fri, 30 Dec 2022 06:30:00 -0000 https://status1.elastic.io/incident/165670#2725bf014a19f81fcd8cde7ac094c0f55e87b1bc51fb7423bc1a91af25d6f119 Webhook executions and requests to our storage service Maester were timing out due to slow responses. https://status1.elastic.io/incident/165670 Fri, 30 Dec 2022 06:30:00 -0000 https://status1.elastic.io/incident/165670#2725bf014a19f81fcd8cde7ac094c0f55e87b1bc51fb7423bc1a91af25d6f119 Webhook executions and requests to our storage service Maester were timing out due to slow responses. https://status1.elastic.io/incident/165669 Fri, 09 Dec 2022 22:18:00 -0000 https://status1.elastic.io/incident/165669#1676ec74753402e4107681b8b88c80acdc90257e3323a37122ad106710516f25 Flow start/stop process is delayed This incident has been resolved. https://status1.elastic.io/incident/165669 Fri, 09 Dec 2022 16:39:00 -0000 https://status1.elastic.io/incident/165669#02772fefd9f4564548c8c4fe40a5fa166b7fe71b147f96ba06f3e72d3abc4a60 We are currently investigating the delayed response of flow stop and start. In addition, the draft publishing is affected. https://status1.elastic.io/incident/165706 Thu, 08 Dec 2022 00:01:00 -0000 https://status1.elastic.io/incident/165706#f874f8cc0e6d8a7a2b6723de2fc680450b0bf55ebeb3cac4765d4510bf04a3d7 UI service recovered. No integrations were affected. https://status1.elastic.io/incident/165706 Thu, 08 Dec 2022 00:00:00 -0000 https://status1.elastic.io/incident/165706#136d73d72521f18e0605c8ef3e90a55fce7cbea0ce106967ef726d1ba97fbbe5 The US cluster UI restarted causing downtime. https://status1.elastic.io/incident/165668 Mon, 26 Sep 2022 10:39:00 -0000 https://status1.elastic.io/incident/165668#f0c1b18416038e535259001aa296c312a643401202a1830f44cf796286e7e811 All integration flows run properly. https://status1.elastic.io/incident/165668 Mon, 26 Sep 2022 09:57:00 -0000 https://status1.elastic.io/incident/165668#84fe72b556229df83640ce1c6b2b1fcdad0380c8f2f4f49984069a95335c1d2b A fix has been implemented and we are monitoring the results. https://status1.elastic.io/incident/165668 Mon, 26 Sep 2022 09:27:00 -0000 https://status1.elastic.io/incident/165668#b49e89858f565356df789d48907acab26bf28c57d91b556d3278bf0591c42255 The implemented fix is working and the flows steps are started to run faster. https://status1.elastic.io/incident/165668 Mon, 26 Sep 2022 08:52:00 -0000 https://status1.elastic.io/incident/165668#7100800dfbeaca2080e2e7e5f802ad92ac039d22f9087771d101142e8f7b948f We have identified the root cause of the problem and the fix is being implemented. https://status1.elastic.io/incident/165668 Mon, 26 Sep 2022 08:42:00 -0000 https://status1.elastic.io/incident/165668#bc7af73d1c73eee922408485446344950bbcc7b62488967f4799f84c8e03b1f4 Currently we are experiencing delays in the flow executions. Our team is looking into the issue right now. https://status1.elastic.io/incident/115577 Thu, 02 Jun 2022 11:56:00 -0000 https://status1.elastic.io/incident/115577#629c45c7911520349c30ff1185a7ab7cf4e824f139a66e30ac9de208f9713275 This incident has been resolved. https://status1.elastic.io/incident/115577 Thu, 02 Jun 2022 11:30:00 -0000 https://status1.elastic.io/incident/115577#f8abcf5b8d6570903c7dcf3a276d75f27ecced23cb5e56de702180180c5b0757 A fix has been implemented and we are monitoring the results. https://status1.elastic.io/incident/115577 Thu, 02 Jun 2022 11:08:00 -0000 https://status1.elastic.io/incident/115577#30974e37f072406cb2635239e986cb84e8153435da7bc29a69e51a0ca5f26ede The issue has been identified and a fix is being implemented. https://status1.elastic.io/incident/115577 Thu, 02 Jun 2022 10:51:00 -0000 https://status1.elastic.io/incident/115577#21e040550f84da5c12365c8902f99ab456d25640f3dcf214edbb4a12a473c72b We are currently investigating this issue. https://status1.elastic.io/incident/115588 Wed, 13 Apr 2022 09:09:00 -0000 https://status1.elastic.io/incident/115588#6369feea104ebe219f466f58792d5b9b5af9e27d420042f7365f6af375a217aa This incident has been resolved. https://status1.elastic.io/incident/115588 Wed, 13 Apr 2022 08:26:00 -0000 https://status1.elastic.io/incident/115588#c965a052a79d5cd2ac487fc6758a8af9d294893dcc259585d729d1d0c2222e17 A fix has been implemented and we are monitoring the results. https://status1.elastic.io/incident/115588 Wed, 13 Apr 2022 08:22:00 -0000 https://status1.elastic.io/incident/115588#0d6b096581bbb9d38faf09f59d6281d3c0cb48428c5535a9b4232f2a1edd6602 The issue has been identified and a fix is being implemented. https://status1.elastic.io/incident/115588 Wed, 13 Apr 2022 08:07:00 -0000 https://status1.elastic.io/incident/115588#b7be5e0e975e3853a47f82b6ed174a00f403dfd0fb997d654f465e5c039b3319 We are currently investigating this issue. https://status1.elastic.io/incident/115592 Mon, 11 Apr 2022 09:26:00 -0000 https://status1.elastic.io/incident/115592#fdd5fcee93a7a07e1015d56147b8562e14b59fac9742e12fb5a3efb6ac3284d5 This incident has been resolved. https://status1.elastic.io/incident/115592 Mon, 11 Apr 2022 09:17:00 -0000 https://status1.elastic.io/incident/115592#f72e18acda69d26d181ecc3a3c747bb1e1fb5894cfa38b57173deba4e1198579 A fix has been implemented and we are monitoring the results. https://status1.elastic.io/incident/115592 Mon, 11 Apr 2022 09:15:00 -0000 https://status1.elastic.io/incident/115592#fc6b87ed605a17b910ac961ef1e191f2e30a5a2846697c2c1207526a0a770dc8 The issue has been identified and a fix is being implemented. https://status1.elastic.io/incident/115592 Mon, 11 Apr 2022 09:11:00 -0000 https://status1.elastic.io/incident/115592#b548dd724aa9dd692ba89828d63643747f0e47ac5b55ad28305310c52266f437 We are currently investigating this issue. https://status1.elastic.io/incident/115593 Tue, 01 Mar 2022 13:59:00 -0000 https://status1.elastic.io/incident/115593#06a375c3343d73d560f30d637a2b201f7af4b72144c19f290f81870fa13ff2fe This incident has been resolved. https://status1.elastic.io/incident/115593 Tue, 01 Mar 2022 13:55:00 -0000 https://status1.elastic.io/incident/115593#48428428b4a5082d5554223b43693b9df521b354b31069c07da965b2ab361ff8 A fix has been implemented and we are monitoring the results. https://status1.elastic.io/incident/115593 Tue, 01 Mar 2022 13:42:00 -0000 https://status1.elastic.io/incident/115593#45e38ca5d7f1f0327fab0bf638847e1abeb6ba88df47da595b866e85e8a9d791 The issue has been identified and a fix is being implemented. https://status1.elastic.io/incident/115593 Tue, 01 Mar 2022 13:24:00 -0000 https://status1.elastic.io/incident/115593#1f421a139c971306fa298d4a7e0cba76b7880b3ce6d048f3e7f0014ebdc9ad2b Our investigation is still ongoing. At this moment we see intermediate timeouts. https://status1.elastic.io/incident/115593 Tue, 01 Mar 2022 11:05:00 -0000 https://status1.elastic.io/incident/115593#83a9d7c59087e76d12aea1ea1c9d3e654cc1e5f80302418c3f9b301dfa3f6f1e We are currently investigating the reports of slow response times from the platform webhook endpoint.