Incidents reported on status page for Tidbyt https://status.tidbyt.com/ https://d1lppblt9t2x15.cloudfront.net/logos/eb3b846e4484c2166ea2f0a5d64561cb.png https://status.tidbyt.com/ en https://status.tidbyt.com/ Fri, 17 Oct 2025 17:12:43 +0000 https://status.tidbyt.com/#d43fbd84a7d26c481cd087437b1aa8c8df3b8f74f2ffb45ad301aea94ff32f65 App Server recovered https://status.tidbyt.com/ Fri, 17 Oct 2025 17:10:33 +0000 https://status.tidbyt.com/#d43fbd84a7d26c481cd087437b1aa8c8df3b8f74f2ffb45ad301aea94ff32f65 App Server went down https://status.tidbyt.com/ Wed, 15 Oct 2025 12:46:53 +0000 https://status.tidbyt.com/#ed96e93b6bb68271b32fa3227fe39dff57740b214371083e87f2275e810e86e1 App Server recovered https://status.tidbyt.com/ Wed, 15 Oct 2025 12:45:38 +0000 https://status.tidbyt.com/#ed96e93b6bb68271b32fa3227fe39dff57740b214371083e87f2275e810e86e1 App Server went down https://status.tidbyt.com/ Sat, 11 Oct 2025 16:06:02 +0000 https://status.tidbyt.com/#8309be868b96d87ff99177b13a5c8fd9e8e71a9c79655ab0a9b29829604caa71 App Server recovered https://status.tidbyt.com/ Sat, 11 Oct 2025 16:04:56 +0000 https://status.tidbyt.com/#8309be868b96d87ff99177b13a5c8fd9e8e71a9c79655ab0a9b29829604caa71 App Server went down https://status.tidbyt.com/ Mon, 06 Oct 2025 11:00:11 +0000 https://status.tidbyt.com/#bd6ff83b93b18aed3e5a92e1066764f2c415638e809adac149fc2202129fbe1e App Server recovered https://status.tidbyt.com/ Mon, 06 Oct 2025 10:57:57 +0000 https://status.tidbyt.com/#bd6ff83b93b18aed3e5a92e1066764f2c415638e809adac149fc2202129fbe1e App Server went down https://status.tidbyt.com/ Mon, 06 Oct 2025 08:42:21 +0000 https://status.tidbyt.com/#fd5441de7094228f0ba217aa8b6cdb217e76b7d5c5a9c60ffe02daf1e68f309f App Server recovered https://status.tidbyt.com/ Mon, 06 Oct 2025 08:39:00 +0000 https://status.tidbyt.com/#fd5441de7094228f0ba217aa8b6cdb217e76b7d5c5a9c60ffe02daf1e68f309f App Server went down https://status.tidbyt.com/ Wed, 24 Sep 2025 23:02:42 +0000 https://status.tidbyt.com/#0d438e281be0df590e171ed168b5303b56acaae908b729f8c0a9210f11db3b62 App Server recovered https://status.tidbyt.com/ Wed, 24 Sep 2025 23:00:18 +0000 https://status.tidbyt.com/#0d438e281be0df590e171ed168b5303b56acaae908b729f8c0a9210f11db3b62 App Server went down https://status.tidbyt.com/ Sat, 23 Aug 2025 09:12:43 +0000 https://status.tidbyt.com/#9e1eb7a74b0cea7122f9cb75252f6cd69c411cd42ca21d474e9bb6aa31b23fae Community (discuss.tidbyt.com) recovered https://status.tidbyt.com/ Sat, 23 Aug 2025 09:07:45 +0000 https://status.tidbyt.com/#9e1eb7a74b0cea7122f9cb75252f6cd69c411cd42ca21d474e9bb6aa31b23fae Community (discuss.tidbyt.com) went down https://status.tidbyt.com/incident/700736 Tue, 05 Aug 2025 11:42:00 -0000 https://status.tidbyt.com/incident/700736#4c595be3c9d2bef3b3ae83988aedf49d10169fa0dd31fd40af5d81fc7cc25360 We fixed a network issue that was preventing us from reaching out weather data provider. https://status.tidbyt.com/incident/646383 Tue, 29 Jul 2025 14:04:00 -0000 https://status.tidbyt.com/incident/646383#9f943f291859761b57d56f3351f8affb31c0da7171caabc69aeae39296d8c164 Weather data has been restored. https://status.tidbyt.com/incident/646383 Tue, 29 Jul 2025 13:29:00 -0000 https://status.tidbyt.com/incident/646383#a15e5cb00437d1192c3568fd2a024d22d91f0c88f1889c1e29c28b99579e3bd7 We've identified the issue as an anomalous increase in weather queries, and have applied a fixe However, the increase in queries our account to be temporarily limited by our weather data provider. We are waiting on the provider to restore service. https://status.tidbyt.com/incident/646383 Tue, 29 Jul 2025 12:42:00 -0000 https://status.tidbyt.com/incident/646383#8339423ecc696e185c77bf52139da7474449f505701943683ec0d01e4eb5d456 We're investigating an issue with weather data. https://status.tidbyt.com/incident/601782 Thu, 12 Jun 2025 19:47:00 -0000 https://status.tidbyt.com/incident/601782#e0b80ec49daf37ec75267c1d2f92dbadb955a4495d0ae82ab637813e80886fe1 We believe that Tidbyt services are operational. However, we are unable to verify this because of issues with the Google service that we use for monitoring our servers. We'll continue to monitor and verify. https://status.tidbyt.com/incident/601782 Thu, 12 Jun 2025 18:32:00 -0000 https://status.tidbyt.com/incident/601782#ef0b1106ac83c6cc0e493f39b2deee6582be4858d33382113aa3e87b132920fe Some Tidbyts may be experiencing degraded performance or unexpected behavior. We are having intermittent issues reaching our primary database due to an outage at Google Cloud: https://status.firebase.google.com/incidents/nEaBHaPRDXMKAsq9sp7G This is where our database is hosted, and Google is investigating. We'll continue to monitor the situation. https://status.tidbyt.com/incident/601782 Thu, 12 Jun 2025 18:19:00 -0000 https://status.tidbyt.com/incident/601782#c7bbec13e091778c2b5adb1654abe2bdc0a0f6d3a7bed2bf5517f0e1958411d7 We are investigating. https://status.tidbyt.com/incident/521606 Sun, 02 Mar 2025 23:00:00 -0000 https://status.tidbyt.com/incident/521606#8b8e56b282426812854e1f88654e4f80f8f79d4810815f5b2d070826ae290579 We fixed the configuration issue and devices should be able to connect. https://status.tidbyt.com/incident/521606 Sun, 02 Mar 2025 22:21:00 -0000 https://status.tidbyt.com/incident/521606#becd33c617ffd30b232b08891c7b37813afebdaea9fa3243dd6557caaa065d8b A misconfiguration in our SSL stack resulted in Tidbyt devices not being able to connect. https://status.tidbyt.com/incident/439407 Fri, 04 Oct 2024 18:48:00 -0000 https://status.tidbyt.com/incident/439407#f706cb445fddbe0bcc1c64bb79d8e1c0ee3e58ad05f8d32e3ad72a7f21e09db1 We've fixed the issue for now and will investigate the root cause. https://status.tidbyt.com/incident/439407 Fri, 04 Oct 2024 18:47:00 -0000 https://status.tidbyt.com/incident/439407#1c6c6797438eb3c3c484cf9300cb97edb1d8680d70efe4ef8fe220c4d3e0cb99 Services are recovering https://status.tidbyt.com/incident/439407 Fri, 04 Oct 2024 18:42:00 -0000 https://status.tidbyt.com/incident/439407#33fa504d40177b29d48cb5c625734f600186162722418b6513a0991164b4ac2d Devices may reboot or display the Tidbyt logo. We are troubleshooting. https://status.tidbyt.com/incident/274150 Tue, 17 Oct 2023 22:03:00 -0000 https://status.tidbyt.com/incident/274150#8506c5321c3ddab194fd67e246a2bffbf1cd48eb38938aa8ee90c519ab0c8732 A portion of devices are unable to reliably connect to the Tidbyt backend. Apps may be showing stale data. https://status.tidbyt.com/incident/256840 Fri, 08 Sep 2023 19:25:00 -0000 https://status.tidbyt.com/incident/256840#73bf618e99e4e9923664c238b09b490a5412d006e28e8893f6ff3145b9696247 All clear. https://status.tidbyt.com/incident/239774 Mon, 31 Jul 2023 20:05:00 -0000 https://status.tidbyt.com/incident/239774#d7da7b8672d3bff6c8ab719e3f86fa64bc1928b90b9dfbe9752b346355984904 The data provider appears to have fixed the issue on their end. We'll continue monitoring. https://status.tidbyt.com/incident/239774 Mon, 31 Jul 2023 19:02:00 -0000 https://status.tidbyt.com/incident/239774#3918c51924712afc534c93cba0ee7b113a246b22c8b5de847a23ce89b1ef880a Due to ongoing issues with our financial data provider, the stocks app is currently unavailable. We're monitoring the situation and hope to have it back in business soon. https://status.tidbyt.com/incident/213445 Mon, 29 May 2023 18:21:00 -0000 https://status.tidbyt.com/incident/213445#3950bdaba2bcb86add3127ef5f1cc4bdb4077cf5320a0fc5bd54851aee17621e We resolved the issue by restarting an unresponsive cache server. Now we're monitoring to make sure everything has recovered. https://status.tidbyt.com/incident/213445 Mon, 29 May 2023 18:04:00 -0000 https://status.tidbyt.com/incident/213445#c8c7b2794587b2f17be164056f11ef4ce6032be50a77364051f5254cc15b12a2 Apps are not updating. We are investigating the issue. https://status.tidbyt.com/incident/202671 Tue, 02 May 2023 14:07:00 -0000 https://status.tidbyt.com/incident/202671#04b8b53db531e842e8102cd71ab578a072cef899755bbafa27d118b33f582d7d All services have returned to normal. https://status.tidbyt.com/incident/202671 Tue, 02 May 2023 14:07:00 -0000 https://status.tidbyt.com/incident/202671#04b8b53db531e842e8102cd71ab578a072cef899755bbafa27d118b33f582d7d All services have returned to normal. https://status.tidbyt.com/incident/202671 Tue, 02 May 2023 13:58:00 -0000 https://status.tidbyt.com/incident/202671#094f632bd26767edc81c9781e021a46b2433fb463539a0f1d96aaa0d0dd72c59 We have renewed the expired certificate and are monitoring as the system returns to normal. https://status.tidbyt.com/incident/202671 Tue, 02 May 2023 13:58:00 -0000 https://status.tidbyt.com/incident/202671#094f632bd26767edc81c9781e021a46b2433fb463539a0f1d96aaa0d0dd72c59 We have renewed the expired certificate and are monitoring as the system returns to normal. https://status.tidbyt.com/incident/202671 Tue, 02 May 2023 12:55:00 -0000 https://status.tidbyt.com/incident/202671#c23e97e771ff1746e99211a2fd3c60f1adb804a400fbea806400f31512738a75 Due to an expired security certificate, Tidbyt devices were unable to connect or receive updates. **UPDATE:** This situation is now resolved. https://status.tidbyt.com/incident/202671 Tue, 02 May 2023 12:55:00 -0000 https://status.tidbyt.com/incident/202671#c23e97e771ff1746e99211a2fd3c60f1adb804a400fbea806400f31512738a75 Due to an expired security certificate, Tidbyt devices were unable to connect or receive updates. **UPDATE:** This situation is now resolved. https://status.tidbyt.com/incident/140510 Wed, 30 Nov 2022 19:38:00 -0000 https://status.tidbyt.com/incident/140510#450fa5c6ae3fa67fe9913154371df7315d7dcaf62ba0be988c8dbeb7c3aa09c5 The affected database was unrecoverable, so we replaced it with a new database. All apps and Tidbyts should now be operating correctly. https://status.tidbyt.com/incident/140510 Wed, 30 Nov 2022 18:59:00 -0000 https://status.tidbyt.com/incident/140510#fd8b4eaf4d7131a8e8915bdefb36260ec53e66820a8b25cb6be98b9e695a71d6 Due to a database outage, Tidbyt apps are not being updated. Tidbyt devices may reboot until this is resolved. We are working on the issue and are waiting for the database to come back online. https://status.tidbyt.com/incident/121677 Wed, 28 Sep 2022 13:52:00 -0000 https://status.tidbyt.com/incident/121677#278b67d022854017371f361878386642aeabb34b0dcf20b8189f1fef711f087e We are receiving baseball scores from our data provider again. Additionally, we've put fixes in place to prevent an issue like this in the future. https://status.tidbyt.com/incident/121677 Wed, 28 Sep 2022 12:31:00 -0000 https://status.tidbyt.com/incident/121677#3f86275f93737714f40540957b92bb320434e0a570061e1f3f481ac663baff88 The issue is ongoing. We are following up and expect the issue with the data provider will be resolved within the next few hours. https://status.tidbyt.com/incident/121677 Tue, 27 Sep 2022 22:49:00 -0000 https://status.tidbyt.com/incident/121677#dfb2cfd905542d4dbd6630b96ab2cc351fa42a0c92ab7be7bafa9de286d0d9f8 We have escalated the issue with our service provider and they are investigating. https://status.tidbyt.com/incident/121677 Tue, 27 Sep 2022 19:55:00 -0000 https://status.tidbyt.com/incident/121677#caabb8acdcaf9775f6f087cca6ff4df0b3370082b3c22e52575f8280b11b3d0f We are not currently receiving baseball scores from the network. We are working with the provider to resolve the issue. https://status.tidbyt.com/incident/118589 Fri, 16 Sep 2022 19:28:00 -0000 https://status.tidbyt.com/incident/118589#77c6ca28075ce6a9db622fb50f2d3213585d3ee8398d6065a25339849253e1ae We restarted the affected services and they have recovered. https://status.tidbyt.com/incident/118589 Fri, 16 Sep 2022 17:15:00 -0000 https://status.tidbyt.com/incident/118589#72f1fbf653a9c286d0d939153396819d905c30f1ec48892b3587c9e2d218f5b4 Tidbyt just shows the Tidbyt logo. https://status.tidbyt.com/incident/90670 Thu, 26 May 2022 20:42:00 -0000 https://status.tidbyt.com/incident/90670#ea4ae40c3e7f3252177b02287fa4695987e2e8e5e43123f6b694c01cbfc341bc We have reverted the change that caused "PORK" to be displayed instead of AAPL. https://status.tidbyt.com/incident/90670 Thu, 26 May 2022 20:34:00 -0000 https://status.tidbyt.com/incident/90670#2535926cb884a00afdb24c24b24827ca15ed261d7c1609a76a58aa2a1cfad3df If no symbol is selected, the Stocks app is supposed to show AAPL by default. However, it may instead be showing "PORK" with test data. We are investigating. https://status.tidbyt.com/incident/90194 Tue, 24 May 2022 21:44:00 -0000 https://status.tidbyt.com/incident/90194#bc70dc60a400f4ce16274993d180df63248c0a4084ae9f7aea9c6012dbe1e915 We have switched to a backup provider that is returning correct cryptocurrency prices. https://status.tidbyt.com/incident/90194 Tue, 24 May 2022 21:25:00 -0000 https://status.tidbyt.com/incident/90194#2abd89f25bd898aa20e47caf01418b3cb0fd9fe1b225409357684c5884089fbd The provider we use for cryptocurrency prices is returning old data. We've contacted the provider and are investigating alternatives. https://status.tidbyt.com/incident/87617 Thu, 12 May 2022 14:26:00 -0000 https://status.tidbyt.com/incident/87617#acb4cfa00f6f758376a08741f4c7aa625b3623c7de3a3b04872b7cd89a5b5d75 Some Tidbyts are currently showing out-of-date information, or no information at all. We are investigating. UPDATE: We've resolved the issue by restarting the affected component. We're still investigating to figure out what happened and prevent the problem in the future. https://status.tidbyt.com/incident/75386 Fri, 11 Mar 2022 13:21:00 -0000 https://status.tidbyt.com/incident/75386#8b702d23a986cdab0a65e5798a6638e358e8d01bba62f494c1a00c34b94abbad The issue has been resolved by rolling back to a previous version. https://status.tidbyt.com/incident/75386 Fri, 11 Mar 2022 12:39:00 -0000 https://status.tidbyt.com/incident/75386#3b003ed654a178709f6b3a41e1e05372f27bdb9b9875b5bb320211538d72d4ac All operations against api.tidbyt.com are returning HTTP 403 errors. Users of the API cannot push new screens to Tidbyt devices. https://status.tidbyt.com/incident/66382 Sun, 16 Jan 2022 02:03:00 -0000 https://status.tidbyt.com/incident/66382#44a9a7c589dfc5ed653d47f86fa9074f64c1009aefd28833a1050ec3aac1cbcd The issue has been resolved. Automation that caused the issue to recur has been disabled until we can take a look on Monday. https://status.tidbyt.com/incident/66382 Sun, 16 Jan 2022 02:00:00 -0000 https://status.tidbyt.com/incident/66382#e579972e25140583f88a12562244190ede1b2825ad7e86ae56a061480ad3a87b Automation pushed out the broken code again, causing the issue to recur. We are fixing it again and disabling the automation. https://status.tidbyt.com/incident/66382 Sun, 16 Jan 2022 00:52:00 -0000 https://status.tidbyt.com/incident/66382#eceed3fb678ad4c8415f45a1a7b169898691bb2da616edd5b31dfb90c7f8dd8a The issue is now resolved, and Tidbyt should show the correct time. We plan to add additional testing around time zone issues to prevent this type of bug in the future. https://status.tidbyt.com/incident/66382 Sat, 15 Jan 2022 23:00:00 -0000 https://status.tidbyt.com/incident/66382#dadfd01fdde676a85303ab9ee15b9b0bdae1ef9e65ad40e36331d5a0ab1da5d7 Clocks on Tidbyt show the time in the wrong time zone. Weather shows the wrong forecast mode or units (°C, °F).