Incidents | Tector Incidents reported on status page for Tector https://status.tector.com/ https://d1lppblt9t2x15.cloudfront.net/logos/368f428b905418b248b43de875a7ebd9.png Incidents | Tector https://status.tector.com/ en dev.tector.com/api/v1 recovered https://status.tector.com/ Sat, 04 Jul 2026 12:07:07 +0000 https://status.tector.com/#01f2c685175e6d6b92ff8d208cb9e04a54c2075a0e5ec77a8c6921f4576e27b7 dev.tector.com/api/v1 recovered dev.tector.com/api/v1 went down https://status.tector.com/ Sat, 04 Jul 2026 12:03:28 +0000 https://status.tector.com/#01f2c685175e6d6b92ff8d208cb9e04a54c2075a0e5ec77a8c6921f4576e27b7 dev.tector.com/api/v1 went down dev.tector.com/api/v1 recovered https://status.tector.com/ Fri, 19 Jun 2026 03:02:20 +0000 https://status.tector.com/#bedc262b18ec8182597ba3cfc6b52995b8d955a08ae6c4cff8c8043cab6ac4b6 dev.tector.com/api/v1 recovered dev.tector.com/api/v1 went down https://status.tector.com/ Fri, 19 Jun 2026 02:58:17 +0000 https://status.tector.com/#bedc262b18ec8182597ba3cfc6b52995b8d955a08ae6c4cff8c8043cab6ac4b6 dev.tector.com/api/v1 went down app.tector.com recovered https://status.tector.com/ Tue, 19 May 2026 21:59:56 +0000 https://status.tector.com/#12501cc662c636f2a42e87fa0fe825e23c24e0f7d577cd45a444b2cbf42e9462 app.tector.com recovered app.tector.com went down https://status.tector.com/ Tue, 19 May 2026 20:54:57 +0000 https://status.tector.com/#12501cc662c636f2a42e87fa0fe825e23c24e0f7d577cd45a444b2cbf42e9462 app.tector.com went down app.tector.com recovered https://status.tector.com/ Mon, 11 May 2026 14:04:51 +0000 https://status.tector.com/#f4fcc238efedbd8c383a6a86e40b943c1e4e84baf385e6b054d4d395435e05ee app.tector.com recovered app.tector.com went down https://status.tector.com/ Mon, 11 May 2026 13:54:51 +0000 https://status.tector.com/#f4fcc238efedbd8c383a6a86e40b943c1e4e84baf385e6b054d4d395435e05ee app.tector.com went down Loss of sensor transmission due to data ingestion outage https://status.tector.com/incident/856279 Tue, 24 Mar 2026 08:30:00 -0000 https://status.tector.com/incident/856279#8d0ff4a8d91cf88bfb6aa2674b107b2808ae26bc89b198374a4c5cb11490f316 Resolved data ingestion outage. Loss of sensor transmission due to data ingestion outage https://status.tector.com/incident/856279 Tue, 24 Mar 2026 08:00:00 -0000 https://status.tector.com/incident/856279#4445ad03f9b4842c245c7f42d946b6b3e4ee0affca7e05ec3bd3ed795f321c80 We’ve unfortunately experienced a bug in our data pipeline that resulted in the loss of all sensor transmissions over a 21-hour period (from 2026-03-23 11:00 to 2026-03-24 08:00 UTC). The issue was caused by a failure in our external data ingestion service—the entry point through which all external data is received. Following a code change deployed the previous day, the service did not start successfully. This failure was not detected by our existing error handling and reporting systems, as the error occurred during the startup phase, prior to full initialization. We are addressing this gap to ensure similar issues are captured and reported in the future.