Incidents reported on status page for TagoIO https://status.tago.io/ https://d1lppblt9t2x15.cloudfront.net/logos/d2ccc803244258bf04b5fc6948f5622a.png https://status.tago.io/ en https://status.tago.io/incident/748660 Wed, 22 Oct 2025 22:28:37 -0000 https://status.tago.io/incident/748660#97afc94869cded7589bdb33a215d360fec2686abb2bc56f394927a7142096bcd Maintenance completed https://status.tago.io/incident/748660 Wed, 22 Oct 2025 03:50:59 -0000 https://status.tago.io/incident/748660#ae4f5922d6e9f0b2d9c927e53f48aab273809f92ba356343034a08de9b21650c We’ve identified an issue where data records from US-E1 accounts are displaying incorrect values. No data has been lost — only the displayed information is affected. Our team is currently recalculating the data to restore accurate results. https://status.tago.io/incident/748660 Wed, 22 Oct 2025 03:50:59 -0000 https://status.tago.io/incident/748660#ae4f5922d6e9f0b2d9c927e53f48aab273809f92ba356343034a08de9b21650c We’ve identified an issue where data records from US-E1 accounts are displaying incorrect values. No data has been lost — only the displayed information is affected. Our team is currently recalculating the data to restore accurate results. https://status.tago.io/ Tue, 21 Oct 2025 05:26:15 +0000 https://status.tago.io/#2c7481aebe71460872504fb24271e26b5fbc1613e5016c72dc5955ac1bfaa2c2 MQTT Broker @ US-E1 recovered https://status.tago.io/ Tue, 21 Oct 2025 05:15:53 +0000 https://status.tago.io/#2c7481aebe71460872504fb24271e26b5fbc1613e5016c72dc5955ac1bfaa2c2 MQTT Broker @ US-E1 went down https://status.tago.io/ Tue, 21 Oct 2025 04:30:04 +0000 https://status.tago.io/#f4c2e2a735f899ebe2618a2c407fe294e693781c73a5d20a3dbd2865fe942c75 Service - Analysis @ US-E1 recovered https://status.tago.io/ Tue, 21 Oct 2025 04:25:55 +0000 https://status.tago.io/#978379ecf456aebe386ac142cef502b21e527aa17010ddd339f75e78e08488a9 Service - Actions @ US-E1 recovered https://status.tago.io/incident/747243 Tue, 21 Oct 2025 04:21:00 -0000 https://status.tago.io/incident/747243#326aa3f3966c5e77719f36a06a4fe4ea3284a7682f0aed2f5678b2ae07419fbe All TagoIO services are now fully operational following the resolution of the AWS us-east-1 outage. We've confirmed that data ingestion, database layers, payload parsing, and analysis execution are back to normal with no lingering issues. Any backlogged data should have processed successfully. Thank you for your patience during this time. https://status.tago.io/incident/747243 Tue, 21 Oct 2025 04:21:00 -0000 https://status.tago.io/incident/747243#326aa3f3966c5e77719f36a06a4fe4ea3284a7682f0aed2f5678b2ae07419fbe All TagoIO services are now fully operational following the resolution of the AWS us-east-1 outage. We've confirmed that data ingestion, database layers, payload parsing, and analysis execution are back to normal with no lingering issues. Any backlogged data should have processed successfully. Thank you for your patience during this time. https://status.tago.io/incident/747243 Tue, 21 Oct 2025 04:21:00 -0000 https://status.tago.io/incident/747243#326aa3f3966c5e77719f36a06a4fe4ea3284a7682f0aed2f5678b2ae07419fbe All TagoIO services are now fully operational following the resolution of the AWS us-east-1 outage. We've confirmed that data ingestion, database layers, payload parsing, and analysis execution are back to normal with no lingering issues. Any backlogged data should have processed successfully. Thank you for your patience during this time. https://status.tago.io/ Tue, 21 Oct 2025 03:58:04 +0000 https://status.tago.io/#f9d4b276b9232fedea3a521ef8e770e3fa2e7011d0dc08eeba5ebf396ec24a61 MQTT Broker @ US-E1 recovered https://status.tago.io/ Tue, 21 Oct 2025 03:57:28 +0000 https://status.tago.io/#bf597b15ea2b41ed895ebd6a01e5afff33184479e66fb8fbe5d67a647004764d API @ US-E1 recovered https://status.tago.io/incident/747243 Mon, 20 Oct 2025 23:33:00 -0000 https://status.tago.io/incident/747243#3573d8106324478cd5931683bb4d95600a8a6f319c79a70f3f8e3c4568179d95 We're actively working to bring TagoIO services back online as soon as possible. The remaining AWS service in us-east-1 is expected to be restored within the next few hours. Once that's complete, we'll be able to fully reactivate our systems. We'll keep monitoring and provide another update soon. https://status.tago.io/ Mon, 20 Oct 2025 19:34:45 +0000 https://status.tago.io/#f9d4b276b9232fedea3a521ef8e770e3fa2e7011d0dc08eeba5ebf396ec24a61 MQTT Broker @ US-E1 went down https://status.tago.io/ Mon, 20 Oct 2025 18:19:38 +0000 https://status.tago.io/#bf597b15ea2b41ed895ebd6a01e5afff33184479e66fb8fbe5d67a647004764d API @ US-E1 went down https://status.tago.io/ Mon, 20 Oct 2025 17:45:05 +0000 https://status.tago.io/#f4c2e2a735f899ebe2618a2c407fe294e693781c73a5d20a3dbd2865fe942c75 Service - Analysis @ US-E1 went down https://status.tago.io/ Mon, 20 Oct 2025 17:41:44 +0000 https://status.tago.io/#978379ecf456aebe386ac142cef502b21e527aa17010ddd339f75e78e08488a9 Service - Actions @ US-E1 went down https://status.tago.io/ Mon, 20 Oct 2025 12:07:27 +0000 https://status.tago.io/#7c744d1f99263076788f334586cec4fd12796dc286a65a35d86aacc7d849b937 Service - Actions @ US-E1 recovered https://status.tago.io/ Mon, 20 Oct 2025 11:53:12 +0000 https://status.tago.io/#25e5cb5c871a5437feb43887de2751df76e4334e9d5a85c22038d74dd91a815e Service - Analysis @ US-E1 recovered https://status.tago.io/ Mon, 20 Oct 2025 07:37:27 +0000 https://status.tago.io/#25e5cb5c871a5437feb43887de2751df76e4334e9d5a85c22038d74dd91a815e Service - Analysis @ US-E1 went down https://status.tago.io/ Mon, 20 Oct 2025 07:25:34 +0000 https://status.tago.io/#7c744d1f99263076788f334586cec4fd12796dc286a65a35d86aacc7d849b937 Service - Actions @ US-E1 went down https://status.tago.io/incident/747243 Mon, 20 Oct 2025 07:20:00 -0000 https://status.tago.io/incident/747243#9542d581cdb0dd0009216841bac8b8f5931c9adfc67fb052cc5042b7aa614eaa We’re currently impacted by an ongoing AWS outage in the us-east-1 region. This is causing higher error rates, latency, and intermittent 500 responses across some services. AWS has acknowledged the issue and is working on recovery: https://health.aws.amazon.com/health/status If possible on your end, temporarily increase retry/backoff on sends from your Network Server to reduce drops during the outage. If you buffer messages, keep them queued—most backlogged data should process once AWS recovers. We’re monitoring closely; no action is required on your side. Systems should return to normal as AWS recovers. We’ll share an update as soon as restoration is confirmed. Thank you for your patience. https://status.tago.io/ Mon, 15 Sep 2025 03:08:15 +0000 https://status.tago.io/#a34c80ba7b83de2fb4a2ccc20bf6e5873396567e35249f018d1759a3c55b8d2a Service - Actions @ US-E1 recovered https://status.tago.io/ Mon, 15 Sep 2025 03:03:02 +0000 https://status.tago.io/#a34c80ba7b83de2fb4a2ccc20bf6e5873396567e35249f018d1759a3c55b8d2a Service - Actions @ US-E1 went down https://status.tago.io/incident/414915 Mon, 19 Aug 2024 14:30:00 -0000 https://status.tago.io/incident/414915#b96dd57ce67c73cef55f074055ddbc1f7afbae53b5454daf98da28ccd140cc7d Maintenance completed https://status.tago.io/incident/414915 Mon, 19 Aug 2024 14:00:00 -0000 https://status.tago.io/incident/414915#34bcf3185d4d9590673f14b46bfc3977823b6c8f3129e5c138b12a241183996f On August 19th, 2024, we will perform a scheduled update to our Action service from 10:00 AM to 10:30 AM (EST). All TagoIO services should remain fully operational throughout this maintenance window. If you experience any issues or have questions, please contact us at support@tago.io. https://status.tago.io/incident/372803 Wed, 22 May 2024 00:23:00 -0000 https://status.tago.io/incident/372803#061b0f5b8d81bacb680d8043749cc91f1e5b73fd51f9b76a239b7949a175f241 We want to let you know that the issue affecting our MQTT has been successfully resolved. The service is now fully operational. https://status.tago.io/incident/372809 Wed, 22 May 2024 00:16:00 -0000 https://status.tago.io/incident/372809#190e947cc9e24e1e50e93105a1fa3425a47279b83c476619a2901ae2c1d7f8ed We want to update you that the issue affecting our API has been successfully resolved. The service is now fully operational. https://status.tago.io/incident/372809 Tue, 21 May 2024 23:54:00 -0000 https://status.tago.io/incident/372809#7f2df6767b1035c84b4e9bfad9fd090ace60d625a6055e94288d5cf301d85b21 We regret to inform you that our API is currently down. Our technical team is aware of the issue and is working diligently to resolve it as quickly as possible. https://status.tago.io/incident/372803 Tue, 21 May 2024 23:33:00 -0000 https://status.tago.io/incident/372803#4c40b81ba3bc52e048f415bc4c7c38d24e7a8b0250a46ada8fd0a8ce614a5879 Our MQTT service is currently down due to a DDoS (Distributed Denial-of-Service) attack. Our team is actively working to mitigate the issue and restore normal operations as soon as possible. https://status.tago.io/incident/320851 Thu, 01 Feb 2024 12:37:00 -0000 https://status.tago.io/incident/320851#c4f846d092dea06bd5ca6bce0a52701f68438a002f8981b732998fc1206372b1 We have addressed the slow response times. We will keep monitoring to make sure everything is stable. Thanks for your patience. https://status.tago.io/incident/320851 Thu, 01 Feb 2024 12:00:00 -0000 https://status.tago.io/incident/320851#b8688aea6aa0892b924626daa025ac107c2a76490db27ff0c09930386d81b758 We are currently investigating reports of slowness affecting some operations like loading data. Our team is actively working to identify and resolve these issues. We appreciate your patience during this time. https://status.tago.io/incident/313449 Tue, 16 Jan 2024 12:55:00 -0000 https://status.tago.io/incident/313449#c2f3c77117619848a04081d9396a0c936c16b6856dff75a0780c1b51c4408c53 We are currently investigating reports of instability affecting some regions. Our team is actively working to identify and resolve these issues. We appreciate your patience during this time. https://status.tago.io/incident/240159 Tue, 01 Aug 2023 13:04:00 -0000 https://status.tago.io/incident/240159#b66bd8f84410f1915e1bc9629c54000886d4bf87376bd9f2d7337a9b715f9c56 Today, during about 10 minutes, between 12:54 UTC and 13:04 UTC, some of our accounts may have experienced a Request Rate Limit issue which led our servers to deny access to API requests. Our team swiftly identified and addressed the situation to ensure minimal impact on your experience. Sorry for this inconvenience.