Incidents reported on status page for Turso https://status.turso.tech/ https://d1lppblt9t2x15.cloudfront.net/logos/ce36349b1a2ff16fe9785f064af061c0.png https://status.turso.tech/ en https://status.turso.tech/ Wed, 26 Nov 2025 14:18:19 +0000 https://status.turso.tech/#30a3572a231fd22147925225d3fda8f262fea01922f0c78cba86ef40c11b431b Johannesburg, South Africa recovered https://status.turso.tech/ Wed, 26 Nov 2025 14:18:19 +0000 https://status.turso.tech/#30a3572a231fd22147925225d3fda8f262fea01922f0c78cba86ef40c11b431b Global recovered https://status.turso.tech/ Wed, 26 Nov 2025 14:18:16 +0000 https://status.turso.tech/#fc73449ac1a2a67d0f3c1aad29b51522ef5dcac7584b5467c1bc2ea77a9377ee Singapore, Singapore recovered https://status.turso.tech/ Wed, 26 Nov 2025 14:18:16 +0000 https://status.turso.tech/#fc73449ac1a2a67d0f3c1aad29b51522ef5dcac7584b5467c1bc2ea77a9377ee Global recovered https://status.turso.tech/ Wed, 26 Nov 2025 14:12:38 +0000 https://status.turso.tech/#30a3572a231fd22147925225d3fda8f262fea01922f0c78cba86ef40c11b431b Johannesburg, South Africa went down https://status.turso.tech/ Wed, 26 Nov 2025 14:12:38 +0000 https://status.turso.tech/#30a3572a231fd22147925225d3fda8f262fea01922f0c78cba86ef40c11b431b Global went down https://status.turso.tech/ Wed, 26 Nov 2025 14:12:27 +0000 https://status.turso.tech/#fc73449ac1a2a67d0f3c1aad29b51522ef5dcac7584b5467c1bc2ea77a9377ee Singapore, Singapore went down https://status.turso.tech/ Wed, 26 Nov 2025 14:12:27 +0000 https://status.turso.tech/#fc73449ac1a2a67d0f3c1aad29b51522ef5dcac7584b5467c1bc2ea77a9377ee Global went down https://status.turso.tech/ Mon, 17 Nov 2025 10:52:36 +0000 https://status.turso.tech/#a4e9138ca02cc1b81b3086ba54f249e7613ba305e876c31eae622676084246bd Mumbai, India recovered https://status.turso.tech/ Mon, 17 Nov 2025 10:52:36 +0000 https://status.turso.tech/#a4e9138ca02cc1b81b3086ba54f249e7613ba305e876c31eae622676084246bd Global recovered https://status.turso.tech/ Mon, 17 Nov 2025 10:44:44 +0000 https://status.turso.tech/#a4e9138ca02cc1b81b3086ba54f249e7613ba305e876c31eae622676084246bd Mumbai, India went down https://status.turso.tech/ Mon, 17 Nov 2025 10:44:44 +0000 https://status.turso.tech/#a4e9138ca02cc1b81b3086ba54f249e7613ba305e876c31eae622676084246bd Global went down https://status.turso.tech/ Thu, 13 Nov 2025 19:44:16 +0000 https://status.turso.tech/#d0788f96036644fb7e61e869be1dbebf2ee7dbf3b3b851e340da9efa460f66fe Mumbai, India recovered https://status.turso.tech/ Thu, 13 Nov 2025 19:44:16 +0000 https://status.turso.tech/#d0788f96036644fb7e61e869be1dbebf2ee7dbf3b3b851e340da9efa460f66fe Global recovered https://status.turso.tech/ Thu, 13 Nov 2025 19:28:25 +0000 https://status.turso.tech/#d0788f96036644fb7e61e869be1dbebf2ee7dbf3b3b851e340da9efa460f66fe Mumbai, India went down https://status.turso.tech/ Thu, 13 Nov 2025 19:28:25 +0000 https://status.turso.tech/#d0788f96036644fb7e61e869be1dbebf2ee7dbf3b3b851e340da9efa460f66fe Global went down https://status.turso.tech/incident/762288 Tue, 11 Nov 2025 15:12:00 -0000 https://status.turso.tech/incident/762288#1a8d31256aa5856d163c92b85ef47fe2eaa37b9e2f6146c34ab2c833564d6b2b Fly.io is experiencing an incident (https://status.flyio.net/incidents/12r6ygv9zc03) in their SJC region due to network issues, Users with databases (primaries or replicas) in the SJC region of fly.io may experience temporary availability issues. https://status.turso.tech/ Thu, 06 Nov 2025 03:41:23 +0000 https://status.turso.tech/#3b58a3cdfe1cf2b1ed136c4d1cd37e5893ea24d849d3d66d0b409b502b69b9b2 Singapore, Singapore recovered https://status.turso.tech/ Thu, 06 Nov 2025 03:41:23 +0000 https://status.turso.tech/#3b58a3cdfe1cf2b1ed136c4d1cd37e5893ea24d849d3d66d0b409b502b69b9b2 Global recovered https://status.turso.tech/ Thu, 06 Nov 2025 03:41:22 +0000 https://status.turso.tech/#6037b36459f4836da60c6564e78ca7e53577bc35726994ddd0a98b49f09bcdc6 Johannesburg, South Africa recovered https://status.turso.tech/ Thu, 06 Nov 2025 03:41:22 +0000 https://status.turso.tech/#6037b36459f4836da60c6564e78ca7e53577bc35726994ddd0a98b49f09bcdc6 Global recovered https://status.turso.tech/ Thu, 06 Nov 2025 03:38:52 +0000 https://status.turso.tech/#6037b36459f4836da60c6564e78ca7e53577bc35726994ddd0a98b49f09bcdc6 Johannesburg, South Africa went down https://status.turso.tech/ Thu, 06 Nov 2025 03:38:52 +0000 https://status.turso.tech/#6037b36459f4836da60c6564e78ca7e53577bc35726994ddd0a98b49f09bcdc6 Global went down https://status.turso.tech/ Thu, 06 Nov 2025 03:38:42 +0000 https://status.turso.tech/#3b58a3cdfe1cf2b1ed136c4d1cd37e5893ea24d849d3d66d0b409b502b69b9b2 Singapore, Singapore went down https://status.turso.tech/ Thu, 06 Nov 2025 03:38:42 +0000 https://status.turso.tech/#3b58a3cdfe1cf2b1ed136c4d1cd37e5893ea24d849d3d66d0b409b502b69b9b2 Global went down https://status.turso.tech/ Thu, 06 Nov 2025 01:31:35 +0000 https://status.turso.tech/#e20f964b325261f08c8e4eb3b7c57b982120515b25d1c0732d3efd355628fec4 Johannesburg, South Africa recovered https://status.turso.tech/ Thu, 06 Nov 2025 01:31:35 +0000 https://status.turso.tech/#e20f964b325261f08c8e4eb3b7c57b982120515b25d1c0732d3efd355628fec4 Global recovered https://status.turso.tech/ Thu, 06 Nov 2025 01:30:37 +0000 https://status.turso.tech/#013c9864b5e0cf4f7e9411d57467236ef371d519238acbf0937acf7eca42eab0 Singapore, Singapore recovered https://status.turso.tech/ Thu, 06 Nov 2025 01:30:37 +0000 https://status.turso.tech/#013c9864b5e0cf4f7e9411d57467236ef371d519238acbf0937acf7eca42eab0 Global recovered https://status.turso.tech/ Thu, 06 Nov 2025 01:15:03 +0000 https://status.turso.tech/#e20f964b325261f08c8e4eb3b7c57b982120515b25d1c0732d3efd355628fec4 Johannesburg, South Africa went down https://status.turso.tech/ Thu, 06 Nov 2025 01:15:03 +0000 https://status.turso.tech/#e20f964b325261f08c8e4eb3b7c57b982120515b25d1c0732d3efd355628fec4 Global went down https://status.turso.tech/ Thu, 06 Nov 2025 01:14:50 +0000 https://status.turso.tech/#013c9864b5e0cf4f7e9411d57467236ef371d519238acbf0937acf7eca42eab0 Singapore, Singapore went down https://status.turso.tech/ Thu, 06 Nov 2025 01:14:50 +0000 https://status.turso.tech/#013c9864b5e0cf4f7e9411d57467236ef371d519238acbf0937acf7eca42eab0 Global went down https://status.turso.tech/ Fri, 31 Oct 2025 06:53:19 +0000 https://status.turso.tech/#c6e966886374f40bbaaa224631b2bdca3570da27fc3c2014eab2f492f4c9bbd4 Toronto, Canada recovered https://status.turso.tech/ Fri, 31 Oct 2025 06:53:19 +0000 https://status.turso.tech/#c6e966886374f40bbaaa224631b2bdca3570da27fc3c2014eab2f492f4c9bbd4 Global recovered https://status.turso.tech/ Fri, 31 Oct 2025 06:41:37 +0000 https://status.turso.tech/#c6e966886374f40bbaaa224631b2bdca3570da27fc3c2014eab2f492f4c9bbd4 Toronto, Canada went down https://status.turso.tech/ Fri, 31 Oct 2025 06:41:37 +0000 https://status.turso.tech/#c6e966886374f40bbaaa224631b2bdca3570da27fc3c2014eab2f492f4c9bbd4 Global went down https://status.turso.tech/ Mon, 20 Oct 2025 23:29:14 +0000 https://status.turso.tech/#22e2cd6b979613ca1035aeb62c49405f76dff46932b8dcf42e6ec66075e41cb9 Amsterdam, Netherlands recovered https://status.turso.tech/ Mon, 20 Oct 2025 23:29:14 +0000 https://status.turso.tech/#22e2cd6b979613ca1035aeb62c49405f76dff46932b8dcf42e6ec66075e41cb9 Global recovered https://status.turso.tech/ Mon, 20 Oct 2025 23:20:04 +0000 https://status.turso.tech/#22e2cd6b979613ca1035aeb62c49405f76dff46932b8dcf42e6ec66075e41cb9 Amsterdam, Netherlands went down https://status.turso.tech/ Mon, 20 Oct 2025 23:20:04 +0000 https://status.turso.tech/#22e2cd6b979613ca1035aeb62c49405f76dff46932b8dcf42e6ec66075e41cb9 Global went down https://status.turso.tech/ Mon, 20 Oct 2025 21:02:17 +0000 https://status.turso.tech/#d23c6e125f78cc5de81d839e9d18cdac3170b5a1c4ac10345c71a8a4ab59ad52 Turso API recovered https://status.turso.tech/ Mon, 20 Oct 2025 21:02:10 +0000 https://status.turso.tech/#34d3294ec997fb5bf39bf0f7f8668c4f69d66e545173666a6d85f450b23546bd AWS us-east-1 (N. Virginia) recovered https://status.turso.tech/ Mon, 20 Oct 2025 20:32:54 +0000 https://status.turso.tech/#d23c6e125f78cc5de81d839e9d18cdac3170b5a1c4ac10345c71a8a4ab59ad52 Turso API went down https://status.turso.tech/ Mon, 20 Oct 2025 20:29:32 +0000 https://status.turso.tech/#34d3294ec997fb5bf39bf0f7f8668c4f69d66e545173666a6d85f450b23546bd AWS us-east-1 (N. Virginia) went down https://status.turso.tech/ Mon, 20 Oct 2025 20:27:38 +0000 https://status.turso.tech/#851035df2e0a9c75c5c1f66d6751e56ac94676b8d158ec8c497b9847fdab329d AWS us-east-1 (N. Virginia) recovered https://status.turso.tech/ Mon, 20 Oct 2025 19:54:32 +0000 https://status.turso.tech/#131ca2ed4c83f18a77e93193b75c98962a2466ad3661371564b9113a192bc9f4 Turso API recovered https://status.turso.tech/ Mon, 20 Oct 2025 19:48:26 +0000 https://status.turso.tech/#131ca2ed4c83f18a77e93193b75c98962a2466ad3661371564b9113a192bc9f4 Turso API went down https://status.turso.tech/ Mon, 20 Oct 2025 19:46:38 +0000 https://status.turso.tech/#58f294bd6de64c8913f20ee0910b6521e98e86c486507b6d94c9f5a05ead079c Turso API recovered https://status.turso.tech/ Mon, 20 Oct 2025 19:19:51 +0000 https://status.turso.tech/#851035df2e0a9c75c5c1f66d6751e56ac94676b8d158ec8c497b9847fdab329d AWS us-east-1 (N. Virginia) went down https://status.turso.tech/ Mon, 20 Oct 2025 19:15:44 +0000 https://status.turso.tech/#be2fd598a89cc0d7224f37e6a8a712b1c12b72ac6a9571019dbc21942063e463 AWS us-east-1 (N. Virginia) recovered https://status.turso.tech/ Mon, 20 Oct 2025 19:12:37 +0000 https://status.turso.tech/#58f294bd6de64c8913f20ee0910b6521e98e86c486507b6d94c9f5a05ead079c Turso API went down https://status.turso.tech/ Mon, 20 Oct 2025 19:09:34 +0000 https://status.turso.tech/#be2fd598a89cc0d7224f37e6a8a712b1c12b72ac6a9571019dbc21942063e463 AWS us-east-1 (N. Virginia) went down https://status.turso.tech/ Mon, 20 Oct 2025 19:06:49 +0000 https://status.turso.tech/#a5a4bd0d782a7994024c20fbe97739b5457fa71218c97669a232478e8fe46e3c Turso API recovered https://status.turso.tech/ Mon, 20 Oct 2025 19:02:28 +0000 https://status.turso.tech/#0310a42aa8ab477782731bf519b5868073f66acfcfa141b8ab3433fe4cff12d1 AWS us-east-1 (N. Virginia) recovered https://status.turso.tech/ Mon, 20 Oct 2025 19:00:10 +0000 https://status.turso.tech/#a5a4bd0d782a7994024c20fbe97739b5457fa71218c97669a232478e8fe46e3c Turso API went down https://status.turso.tech/ Mon, 20 Oct 2025 18:56:27 +0000 https://status.turso.tech/#fde01117eef2626a031fb1f207400967b14ddedc4d167d09a27bdbb4e1f6b56f Turso API recovered https://status.turso.tech/ Mon, 20 Oct 2025 18:48:59 +0000 https://status.turso.tech/#fde01117eef2626a031fb1f207400967b14ddedc4d167d09a27bdbb4e1f6b56f Turso API went down https://status.turso.tech/ Mon, 20 Oct 2025 18:43:15 +0000 https://status.turso.tech/#129b865b4269693953703d1b8f6c79f880cf5ab947da362480b7a67430b194eb Turso API recovered https://status.turso.tech/ Mon, 20 Oct 2025 18:37:03 +0000 https://status.turso.tech/#129b865b4269693953703d1b8f6c79f880cf5ab947da362480b7a67430b194eb Turso API went down https://status.turso.tech/ Mon, 20 Oct 2025 18:32:21 +0000 https://status.turso.tech/#f4aba8024f87401a99f8df76cd22d1c0e7b02e041578f49a098bd5a1c9388a76 Turso API recovered https://status.turso.tech/ Mon, 20 Oct 2025 18:27:23 +0000 https://status.turso.tech/#0310a42aa8ab477782731bf519b5868073f66acfcfa141b8ab3433fe4cff12d1 AWS us-east-1 (N. Virginia) went down https://status.turso.tech/ Mon, 20 Oct 2025 18:22:45 +0000 https://status.turso.tech/#e4ed49cd317a3fc02532078b6deec0572bd2268f96577597c132bec309b8cbaa AWS us-east-1 (N. Virginia) recovered https://status.turso.tech/ Mon, 20 Oct 2025 18:07:11 +0000 https://status.turso.tech/#e4ed49cd317a3fc02532078b6deec0572bd2268f96577597c132bec309b8cbaa AWS us-east-1 (N. Virginia) went down https://status.turso.tech/ Mon, 20 Oct 2025 18:04:14 +0000 https://status.turso.tech/#0db65fe564cb5eb057619a75a000204dc4182b550b2fcd3e2202e7a7ecef7445 AWS us-east-1 (N. Virginia) recovered https://status.turso.tech/ Mon, 20 Oct 2025 17:53:10 +0000 https://status.turso.tech/#f4aba8024f87401a99f8df76cd22d1c0e7b02e041578f49a098bd5a1c9388a76 Turso API went down https://status.turso.tech/ Mon, 20 Oct 2025 17:50:56 +0000 https://status.turso.tech/#d3944b0c28ec0f2322d36426f5a15edcccff0c0d1e88beef16edd6d151c8ad70 Turso API recovered https://status.turso.tech/ Mon, 20 Oct 2025 17:45:11 +0000 https://status.turso.tech/#0db65fe564cb5eb057619a75a000204dc4182b550b2fcd3e2202e7a7ecef7445 AWS us-east-1 (N. Virginia) went down https://status.turso.tech/ Mon, 20 Oct 2025 17:42:07 +0000 https://status.turso.tech/#40127e4a343f303a2c1b521b2c478c25b83a7bd6a05f759d054305e42b20911d AWS us-east-1 (N. Virginia) recovered https://status.turso.tech/ Mon, 20 Oct 2025 17:41:39 +0000 https://status.turso.tech/#d3944b0c28ec0f2322d36426f5a15edcccff0c0d1e88beef16edd6d151c8ad70 Turso API went down https://status.turso.tech/ Mon, 20 Oct 2025 17:40:23 +0000 https://status.turso.tech/#1962e5bbaf7d31f6e6771be871512f6c5dd9d2bcc5ac80fc3f16f54b02f8d376 Turso API recovered https://status.turso.tech/ Mon, 20 Oct 2025 17:35:29 +0000 https://status.turso.tech/#1962e5bbaf7d31f6e6771be871512f6c5dd9d2bcc5ac80fc3f16f54b02f8d376 Turso API went down https://status.turso.tech/ Mon, 20 Oct 2025 17:33:30 +0000 https://status.turso.tech/#769c7735f46a60fb63d2d4e060b12cd88e3ba1cd2e1048692441627f9455c870 Turso API recovered https://status.turso.tech/ Mon, 20 Oct 2025 16:14:31 +0000 https://status.turso.tech/#769c7735f46a60fb63d2d4e060b12cd88e3ba1cd2e1048692441627f9455c870 Turso API went down https://status.turso.tech/ Mon, 20 Oct 2025 16:00:55 +0000 https://status.turso.tech/#40127e4a343f303a2c1b521b2c478c25b83a7bd6a05f759d054305e42b20911d AWS us-east-1 (N. Virginia) went down https://status.turso.tech/incident/747418 Mon, 20 Oct 2025 15:08:00 -0000 https://status.turso.tech/incident/747418#c71922649198685f3031e1ae6cb9015aed72cfb2195d7a9a4e8e416016e62530 Due to the AWS US-EAST-1 incident, creation of new databases, and other operations that modify status may fail. https://status.turso.tech/ Mon, 20 Oct 2025 15:01:35 +0000 https://status.turso.tech/#cbb94a7f097f5177516c4997769fb4bc99a222216eebe60e19669e1777dcb0ee AWS us-east-1 (N. Virginia) recovered https://status.turso.tech/ Mon, 20 Oct 2025 14:29:07 +0000 https://status.turso.tech/#cbb94a7f097f5177516c4997769fb4bc99a222216eebe60e19669e1777dcb0ee AWS us-east-1 (N. Virginia) went down https://status.turso.tech/ Mon, 20 Oct 2025 09:19:31 +0000 https://status.turso.tech/#db4974270be85dab11ffdea7c3cb2808c1bd289d36b5caf3c4f39dfdf13784a9 AWS us-east-1 (N. Virginia) recovered https://status.turso.tech/ Mon, 20 Oct 2025 07:54:12 +0000 https://status.turso.tech/#db4974270be85dab11ffdea7c3cb2808c1bd289d36b5caf3c4f39dfdf13784a9 AWS us-east-1 (N. Virginia) went down https://status.turso.tech/incident/746819 Mon, 20 Oct 2025 07:52:00 -0000 https://status.turso.tech/incident/746819#5facdb4467f19d24bff47a5190d288bf3a9cc19090ebe85b032ddd808517807f Due to AWS outage in the us-east-1 region writes for databases in that region are unavailable at the moment. Dashboard is also affected due to the us-east-1 incident on AWS side. https://status.turso.tech/incident/746819 Mon, 20 Oct 2025 07:52:00 -0000 https://status.turso.tech/incident/746819#5facdb4467f19d24bff47a5190d288bf3a9cc19090ebe85b032ddd808517807f Due to AWS outage in the us-east-1 region writes for databases in that region are unavailable at the moment. Dashboard is also affected due to the us-east-1 incident on AWS side. https://status.turso.tech/ Wed, 01 Oct 2025 13:49:59 +0000 https://status.turso.tech/#65a51e51338d72023a73c9694722eac2676c96833da1bb5df7139650dd7698c6 Sydney, Australia recovered https://status.turso.tech/ Wed, 01 Oct 2025 13:49:59 +0000 https://status.turso.tech/#65a51e51338d72023a73c9694722eac2676c96833da1bb5df7139650dd7698c6 Global recovered https://status.turso.tech/ Wed, 01 Oct 2025 13:46:16 +0000 https://status.turso.tech/#65a51e51338d72023a73c9694722eac2676c96833da1bb5df7139650dd7698c6 Sydney, Australia went down https://status.turso.tech/ Wed, 01 Oct 2025 13:46:16 +0000 https://status.turso.tech/#65a51e51338d72023a73c9694722eac2676c96833da1bb5df7139650dd7698c6 Global went down https://status.turso.tech/ Sat, 27 Sep 2025 12:12:12 +0000 https://status.turso.tech/#bc854d6617bd5dc071e03cf2c7b5487a0865900891d52e2768b84fda675f65c8 Mumbai, India recovered https://status.turso.tech/ Sat, 27 Sep 2025 12:12:12 +0000 https://status.turso.tech/#bc854d6617bd5dc071e03cf2c7b5487a0865900891d52e2768b84fda675f65c8 Global recovered https://status.turso.tech/ Sat, 27 Sep 2025 12:08:03 +0000 https://status.turso.tech/#bc854d6617bd5dc071e03cf2c7b5487a0865900891d52e2768b84fda675f65c8 Mumbai, India went down https://status.turso.tech/ Sat, 27 Sep 2025 12:08:03 +0000 https://status.turso.tech/#bc854d6617bd5dc071e03cf2c7b5487a0865900891d52e2768b84fda675f65c8 Global went down https://status.turso.tech/ Sat, 27 Sep 2025 11:24:41 +0000 https://status.turso.tech/#1523c558bcd95ded24b7c59b91535d933d5abe13db668abd78676a5f1fcef3f5 Mumbai, India recovered https://status.turso.tech/ Sat, 27 Sep 2025 11:24:41 +0000 https://status.turso.tech/#1523c558bcd95ded24b7c59b91535d933d5abe13db668abd78676a5f1fcef3f5 Global recovered https://status.turso.tech/ Sat, 27 Sep 2025 11:19:34 +0000 https://status.turso.tech/#1523c558bcd95ded24b7c59b91535d933d5abe13db668abd78676a5f1fcef3f5 Mumbai, India went down https://status.turso.tech/ Sat, 27 Sep 2025 11:19:34 +0000 https://status.turso.tech/#1523c558bcd95ded24b7c59b91535d933d5abe13db668abd78676a5f1fcef3f5 Global went down https://status.turso.tech/incident/707994 Mon, 18 Aug 2025 15:59:00 -0000 https://status.turso.tech/incident/707994#67490f6d5a0eec57d21114eff014ba80387a140756be66638cef1ac33f387b3b Tokens generation is back to normal https://status.turso.tech/incident/707994 Mon, 18 Aug 2025 15:34:00 -0000 https://status.turso.tech/incident/707994#6ed0335f2c2393da087bcd742a25ef63163bb12158d2b673311db064284707c8 New tokens for databases and groups cannot be generated at the moment. Our team is working to resolve the issue. https://status.turso.tech/incident/619383 Mon, 14 Jul 2025 15:42:00 -0000 https://status.turso.tech/incident/619383#c41d95a02653f04019967228ccbb1c48060f4fcc924a5f9af5a614eb2398d3a3 S3 availability in the region returned back to normal and so all DBs are back online. There were partial S3 availability issues in the region due to which some DBs was unavailable. https://status.turso.tech/incident/618134 Fri, 11 Jul 2025 19:03:00 -0000 https://status.turso.tech/incident/618134#99755258c7335ae34fe7eaa08e6ade4d694b3e642073f94cacdb2650cf8759d3 Fly provider has networking issues in IAD region at the moment. Connectivity to the Turso databases with primaries/replicas in that region at Fly can be unstable. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555843 Sat, 03 May 2025 07:38:00 -0000 https://status.turso.tech/incident/555843#f923cc0e493efac54470152cf78185f7ddd21e4533e242563ce66dca118cc901 * We had an issue with the proxy layer on Fly.io, that should be now resolved. * Users on AWS using legacy URLs (.turso.io) were also affected because those URLs still go through Fly. But if you had switched to the AWS-specific URLs (.region.aws.turso.io) you were not affected. **A long incident!** The incident took long to resolve because with all proxies coming down everywhere, they all tried to come back at the same time, overloading other servers. Fly.io also started rate limiting us because of the excessive errors, contributing to the duration of the incident. **What have we done?** In the short term, we disable all automation to bring proxies online automatically, and started bringing them up manually. We are doing it one by one. Not all regions are back. You can connect to your database in every region, but if you are coming to a region where the proxy is not yet deployed, latencies will be higher. Eventually we will have the proxy back in all regions. **What will we do next** We will work on ways to prevent this in the future by changing the way proxy startup works, so that if there is a global issue again, all proxies coming back online at the same time won't overload any other service. https://status.turso.tech/incident/555842 Sat, 03 May 2025 06:10:00 -0000 https://status.turso.tech/incident/555842#60b90d2cba8f30676a2ecb07cf0bcd9abb2ce5e816e365c63b93f8a52eda8d61 We have identified the issue and rolled out the fixes. All databases should be functional. https://status.turso.tech/incident/555842 Sat, 03 May 2025 02:38:00 -0000 https://status.turso.tech/incident/555842#ae9a09545df9f0910491016394ad6e088fe5d03ece00de3e9172e991ded1dffa Databases hosted on Fly are unreachable https://status.turso.tech/incident/546344 Wed, 16 Apr 2025 17:34:00 -0000 https://status.turso.tech/incident/546344#323da0235d8021623efe6afb5e869c04f84b40767719ccafacd86d22872e133d We are seeing increasing error rates for writes to S3 Express One Zone in ap-northeast-1 region. Issue partially affects writes to the DBs in that region. We are actively investigating the issue with AWS support team. https://status.turso.tech/incident/545528 Tue, 15 Apr 2025 08:43:00 -0000 https://status.turso.tech/incident/545528#702cea54096d5dd9ff917938570dd4739120eac5d7a58d97df354c7132fea3fe AWS has connectivity issues at ap-northeast-1 AZ at the moment and this incident affects S3 Express One Zone: https://health.aws.amazon.com/health/status https://status.turso.tech/incident/539629 Fri, 04 Apr 2025 01:12:00 -0000 https://status.turso.tech/incident/539629#823cc62fdd802320a555c764dc3e5e057544c07d4e69046ae6f80b20d3eb0035 We have resolved the issue and database creation should work normally now https://status.turso.tech/incident/528278 Fri, 14 Mar 2025 15:32:00 -0000 https://status.turso.tech/incident/528278#68400fdd2d7b883d3c810e0348238abdfb8a468a99cf0d57794b6aa3d0962f96 We are investigating an issue in the API that may be preventing access to databases created in the last 4 hours. Update: a patch has been applied and the situation is resolved. https://status.turso.tech/incident/519844 Thu, 27 Feb 2025 10:30:00 -0000 https://status.turso.tech/incident/519844#75bc2eeedd6a06872d9a6a5b223c548b1e918826569a555785e307683cd01761 The issue has been fixed by downstream infra provider https://status.turso.tech/incident/519844 Thu, 27 Feb 2025 09:11:00 -0000 https://status.turso.tech/incident/519844#666a21679918b3844add4211197289f11a1f8be9e1d8808ef9f1eda42fa86973 Fly cloud provider experiences networking issues with multiple hosts in AMS. Databases (primaries and replicas) in that region can experience unavailability. https://status.turso.tech/incident/513785 Sun, 16 Feb 2025 10:12:00 -0000 https://status.turso.tech/incident/513785#56a67c172d1ee829bf84a300d28e1e5a91a7cca73e2bfc4e73e46502068ab0d0 Connectivity in IAD were recovered on Fly provider side. DB instances in that region and Turso control plane are fully operational. https://status.turso.tech/incident/513785 Sun, 16 Feb 2025 10:12:00 -0000 https://status.turso.tech/incident/513785#56a67c172d1ee829bf84a300d28e1e5a91a7cca73e2bfc4e73e46502068ab0d0 Connectivity in IAD were recovered on Fly provider side. DB instances in that region and Turso control plane are fully operational. https://status.turso.tech/incident/513785 Sun, 16 Feb 2025 10:12:00 -0000 https://status.turso.tech/incident/513785#56a67c172d1ee829bf84a300d28e1e5a91a7cca73e2bfc4e73e46502068ab0d0 Connectivity in IAD were recovered on Fly provider side. DB instances in that region and Turso control plane are fully operational. https://status.turso.tech/incident/467662 Tue, 26 Nov 2024 08:15:00 -0000 https://status.turso.tech/incident/467662#7995e6727c3da2bd37d52505d0273e4d2474ad89518567b1e0d39b350173aefd This incident has been resolved https://status.turso.tech/incident/467662 Tue, 26 Nov 2024 08:15:00 -0000 https://status.turso.tech/incident/467662#7995e6727c3da2bd37d52505d0273e4d2474ad89518567b1e0d39b350173aefd This incident has been resolved https://status.turso.tech/incident/467662 Tue, 26 Nov 2024 04:34:00 -0000 https://status.turso.tech/incident/467662#6dcd62f4bc8e5bcf641c6aeb5acde79a30cd265434cd7993e7a9ad53f1c80c0a Some infrastructure operations might still time out or fail https://status.turso.tech/incident/467662 Tue, 26 Nov 2024 04:34:00 -0000 https://status.turso.tech/incident/467662#6dcd62f4bc8e5bcf641c6aeb5acde79a30cd265434cd7993e7a9ad53f1c80c0a Some infrastructure operations might still time out or fail https://status.turso.tech/incident/467662 Tue, 26 Nov 2024 03:47:00 -0000 https://status.turso.tech/incident/467662#fde92540ff291fd0ee3158492f2d61f424a478ed4c6c6eabf9c4388134f7802f The systems are back to operating normally. We're still monitoring for any instabilities. https://status.turso.tech/incident/467662 Tue, 26 Nov 2024 03:47:00 -0000 https://status.turso.tech/incident/467662#fde92540ff291fd0ee3158492f2d61f424a478ed4c6c6eabf9c4388134f7802f The systems are back to operating normally. We're still monitoring for any instabilities. https://status.turso.tech/incident/467662 Mon, 25 Nov 2024 22:14:00 -0000 https://status.turso.tech/incident/467662#a99d7eaeeb0894b7cec45b31e5eedbc5f1f1059c209a7bcb6639690ef1f66112 Due to an ongoing incident with one of our providers, users may see increased latency and errors when querying databases. Turso API may also be unstable when modifying infrastructure. https://status.turso.tech/incident/467662 Mon, 25 Nov 2024 22:14:00 -0000 https://status.turso.tech/incident/467662#a99d7eaeeb0894b7cec45b31e5eedbc5f1f1059c209a7bcb6639690ef1f66112 Due to an ongoing incident with one of our providers, users may see increased latency and errors when querying databases. Turso API may also be unstable when modifying infrastructure. https://status.turso.tech/incident/464453 Wed, 20 Nov 2024 05:00:00 -0000 https://status.turso.tech/incident/464453#aa7b96639b336a9b415a79ef092cb575ffe6c26790099fa8de801251e5a89eaf Maintenance completed https://status.turso.tech/incident/464453 Wed, 20 Nov 2024 02:00:00 -0000 https://status.turso.tech/incident/464453#2cccfcd9981651b8b470b9cbc36ba0fad9b945f51b7ccc3f2ac89d6b0c6adb88 Our cloud provider is performing an emergency switch replacement during this window. An up to one hour network outage is expected during this maintenance window. We've migrated most of the existing databases out of ARN. New databases should be automatically created in nearby regions. Due to the emergency nature of the maintenance we could not migrate all databases in time, so some customers could still be affected. https://status.turso.tech/incident/448872 Wed, 23 Oct 2024 02:10:00 -0000 https://status.turso.tech/incident/448872#76d0ddb6fc32c2531e4bcc6a3aed1f2ae1663d63fdc2ec256434204090c3256f Issue was resolved by the infra provider https://status.turso.tech/incident/448872 Tue, 22 Oct 2024 18:45:00 -0000 https://status.turso.tech/incident/448872#45bb91526c06ff18053f2b0139e66823146d2e16d306ed00b1a6a08a2c95d2a9 Fly.io updated their incident with the information that applications were also impacted. users might see increasing 502 errors when connecting with their databases https://status.turso.tech/incident/448872 Tue, 22 Oct 2024 18:10:00 -0000 https://status.turso.tech/incident/448872#ef97b6ee93cafff924edc65b1dbca6c1eba5a23befa2b9f3aa9bdd763facec21 due to an incident in fly.io's machines API, db and group creation is degraded https://status.flyio.net/incidents/j3610m921p24 https://status.turso.tech/incident/442972 Fri, 11 Oct 2024 22:41:00 -0000 https://status.turso.tech/incident/442972#e9286595da2f53c3fe3f018d3aa76a160456fbee85c99124116c55476e7d571d The issues have been fixed by our infra provider https://status.turso.tech/incident/442972 Fri, 11 Oct 2024 22:41:00 -0000 https://status.turso.tech/incident/442972#e9286595da2f53c3fe3f018d3aa76a160456fbee85c99124116c55476e7d571d The issues have been fixed by our infra provider https://status.turso.tech/incident/442972 Fri, 11 Oct 2024 10:30:00 -0000 https://status.turso.tech/incident/442972#401bedf12c3bc2cb2947ee1e283872da6b9abd0d23cc8aa6b792903732a963ca Our infra provider is having capacity issues in arn and ams regions. Some of the existing databases also might face some connectivity issues. https://status.turso.tech/incident/442972 Fri, 11 Oct 2024 10:30:00 -0000 https://status.turso.tech/incident/442972#401bedf12c3bc2cb2947ee1e283872da6b9abd0d23cc8aa6b792903732a963ca Our infra provider is having capacity issues in arn and ams regions. Some of the existing databases also might face some connectivity issues. https://status.turso.tech/incident/438244 Wed, 02 Oct 2024 17:33:00 -0000 https://status.turso.tech/incident/438244#de50f0c216249cc50917fe219cda08d49fcbc345e275211b9259e6daf4824c40 Maintenance was performed and workloads from LHR came back online https://status.turso.tech/incident/438244 Wed, 02 Oct 2024 13:10:00 -0000 https://status.turso.tech/incident/438244#601eb6bd9d030f1440764be55c51f43c620769e227df47541dd85e5cc444dd6a The LHR region went through emergency maintenance which resulted in unavailability. In situations like this, we're usually able to migrate workloads to different data centers before the maintenance window. However, due to the short notice, we weren't able to migrate all databases safely before the maintenance. https://status.turso.tech/incident/434836 Thu, 26 Sep 2024 03:30:00 -0000 https://status.turso.tech/incident/434836#4fee0b6ef108b6455407df03fa8de94c94f4990f81d4a0650ff63220d9cd297a Maintenance completed https://status.turso.tech/incident/434836 Thu, 26 Sep 2024 01:00:00 -0000 https://status.turso.tech/incident/434836#e90bb99600717e6f80ee107eb0ff8a519729ce744380074a034c124d36386a88 After networking instability earlier today, our infrastructure provider needed to perform emergency maintenance on their Latin America data centers. Network outages below 15 minutes may be expected. https://status.turso.tech/incident/431815 Thu, 19 Sep 2024 18:04:00 -0000 https://status.turso.tech/incident/431815#58dc99de589627b4d1c3fa2f80b36485a8f4a336219e597f4dee11195b6361e6 The cloud provider has applied mitigations to the issue in the IAD, EWR, and BOS regions. Customers with databases in these regions should not experience any issues at this time. https://status.turso.tech/incident/431815 Thu, 19 Sep 2024 18:04:00 -0000 https://status.turso.tech/incident/431815#58dc99de589627b4d1c3fa2f80b36485a8f4a336219e597f4dee11195b6361e6 The cloud provider has applied mitigations to the issue in the IAD, EWR, and BOS regions. Customers with databases in these regions should not experience any issues at this time. https://status.turso.tech/incident/431815 Thu, 19 Sep 2024 16:47:00 -0000 https://status.turso.tech/incident/431815#3c8f9453c3cfbc3af18bf1f20b5d313e0b2531e3784887db3c547b36f8749fca Our cloud provider is experiencing an issue in the IAD, EWR, and BOS regions (Ashburn, Virginia; Secaucus, New Jersey; and Boston, Massachusetts) that is affecting databases and degrading performance. This issue primarily impacts customers with databases under high load. https://status.turso.tech/incident/431815 Thu, 19 Sep 2024 16:47:00 -0000 https://status.turso.tech/incident/431815#3c8f9453c3cfbc3af18bf1f20b5d313e0b2531e3784887db3c547b36f8749fca Our cloud provider is experiencing an issue in the IAD, EWR, and BOS regions (Ashburn, Virginia; Secaucus, New Jersey; and Boston, Massachusetts) that is affecting databases and degrading performance. This issue primarily impacts customers with databases under high load. https://status.turso.tech/incident/430485 Tue, 17 Sep 2024 11:51:00 -0000 https://status.turso.tech/incident/430485#3970651e5e21e97ab58ebe24d55289fb0a8d874a1d3bd74634aaec0070160310 Maintenance operations were finished successfully. https://status.turso.tech/incident/430485 Tue, 17 Sep 2024 10:40:00 -0000 https://status.turso.tech/incident/430485#49aad25525e676d3d72f54dac36010e83d10ccc12ad18ef8d601419786400965 We are proactively performing maintenance operations with primaries in the ORD region to mitigate the effects of scheduled network maintenance by our cloud provider in the same region. Primaries in the ORD region may experience a few seconds of unavailability during the maintenance operations. https://status.turso.tech/incident/428811 Fri, 13 Sep 2024 18:12:00 -0000 https://status.turso.tech/incident/428811#d4c4bcb18402f8c87ba3d677f5d1352e591b1997234c71694a7031b324d04075 The issue was resolved https://status.turso.tech/incident/428811 Fri, 13 Sep 2024 17:39:00 -0000 https://status.turso.tech/incident/428811#f6aac560ec3a565864d4af3244497c605fde49166a9e65b8a82b87d72ec4e5d7 Operations that require changes in infrastructure were disrupted due to an incident on a cloud provider. This includes group/locations creation and deletion, unarchiving, and scale to one after a group went idle. https://status.turso.tech/incident/426108 Sun, 08 Sep 2024 20:29:00 -0000 https://status.turso.tech/incident/426108#190b743b83a1408367c4e36402c7ac1b658ceb06d5ac7b669a56fed90cff20bd The issue was resolved https://status.turso.tech/incident/422676 Sun, 01 Sep 2024 20:11:00 -0000 https://status.turso.tech/incident/422676#adf0f3aa35c090d71ecb3a96be3ed272b4d5fc1e057e665863c8658c549ee471 network issue was solved https://status.turso.tech/incident/422676 Sun, 01 Sep 2024 19:40:00 -0000 https://status.turso.tech/incident/422676#372b9241dbc5322b33a3cb28331e20ac3ea3ba6531de707fdcfcc9930e47040f usage metrics, CLI and API are degraded due to a network failure in a cloud provider. We are working with them to restablish the system to its normalcy. https://status.turso.tech/incident/421210 Thu, 29 Aug 2024 10:32:00 -0000 https://status.turso.tech/incident/421210#7c53041dfd4ee8c8e1df07867d679f1181824d250448be6f22109c80c0ffceda Server API now working normally https://status.turso.tech/incident/421210 Thu, 29 Aug 2024 10:29:00 -0000 https://status.turso.tech/incident/421210#9a67649386e7f9082fa775d6603629a3d94a1d893c8ab82a4c2251f6510471a4 We are currently experiencing an outage of API server. https://status.turso.tech/incident/418452 Sat, 24 Aug 2024 03:11:00 -0000 https://status.turso.tech/incident/418452#bea0c537f4de380641b5a8944fa58845d974f2ebe7c106f8307850ce62dfde0c Groups of starter plan users that were marked as idle may be unavailable due to an issue with a downstream provider. We're working to mitigate the issue. https://status.turso.tech/incident/416755 Wed, 21 Aug 2024 00:08:00 -0000 https://status.turso.tech/incident/416755#c5095cef46db6609a3134b94121894c3fcc0c2910428e634791ca73542a97bb7 Due to an incident in a provider, operations that involve infrastructure changes may be disrupted. https://status.turso.tech/incident/414326 Thu, 15 Aug 2024 08:09:00 -0000 https://status.turso.tech/incident/414326#481fc6a67a153c94eee3a11607110d243943a1de6ae50d144aa73a5484627c3f Patch has been deployed and analytics service is restored. https://status.turso.tech/incident/413422 Tue, 13 Aug 2024 21:10:00 -0000 https://status.turso.tech/incident/413422#cbedfff20e88a7492c6e4ef63712fcde7df2b39c861b72123e3290c2663fea0d We are still working with our cloud provider to pinpoint the cause of the incident, but traffic is back to normal https://status.turso.tech/incident/413422 Tue, 13 Aug 2024 21:00:00 -0000 https://status.turso.tech/incident/413422#cbf48245d3a6804cd2cbc5a3dd3a798d1d4c96ed7b8499eda02a0506002dc33a Several of our location suffered a drastic reduction of traffic during the time of the incident, the cause is attributed to an ongoing incident of one of our cloud providers. https://status.turso.tech/incident/410440 Wed, 07 Aug 2024 19:26:00 -0000 https://status.turso.tech/incident/410440#aacab030afe3df2f7a86d5f8b387312b8a10b17c514f86569f4b25bf3fd9621b Our website, and some databases are experiencing failures due to incidents in 2 cloud providers we use. https://status.turso.tech/incident/410440 Wed, 07 Aug 2024 19:26:00 -0000 https://status.turso.tech/incident/410440#aacab030afe3df2f7a86d5f8b387312b8a10b17c514f86569f4b25bf3fd9621b Our website, and some databases are experiencing failures due to incidents in 2 cloud providers we use. https://status.turso.tech/incident/410440 Wed, 07 Aug 2024 19:26:00 -0000 https://status.turso.tech/incident/410440#aacab030afe3df2f7a86d5f8b387312b8a10b17c514f86569f4b25bf3fd9621b Our website, and some databases are experiencing failures due to incidents in 2 cloud providers we use. https://status.turso.tech/incident/406921 Wed, 31 Jul 2024 09:47:00 -0000 https://status.turso.tech/incident/406921#82aeec402acbfe57449ceb69f6bec28981e3094426131feb499657d4bdf36021 The partial outage for databases with primaries in the AMS region has been completely resolved. https://status.turso.tech/incident/406921 Tue, 30 Jul 2024 15:00:00 -0000 https://status.turso.tech/incident/406921#ebd702dd7a4857f33576e50513dc4a987b39a9e680fbbe9d26d4b306702129d6 Migration of primaries located in the AMS region was performed to avoid downtime due to a maintenance window of our cloud provider. Due to the misconfiguration of clusters that had at least two locations during maintenance, replicas were not updated, which led to unavailability when requests arrived at replicas. If the request arrived at the primary, no issues were experienced. As soon as we became aware of the issue, a fix was applied, and the clusters returned to normal operation. https://status.turso.tech/incident/405441 Mon, 29 Jul 2024 11:15:00 -0000 https://status.turso.tech/incident/405441#c366fa33af713b4e900e4c911443ade0975d4581b5cc618de315602f46d81342 Resolved by upstream infra provider https://status.turso.tech/incident/405441 Mon, 29 Jul 2024 09:17:00 -0000 https://status.turso.tech/incident/405441#10b377d2980f627d6605eb9d6ec1f68ce55917271247ccd2722107e9e2853470 All commands that require infrastructure change are disrupted due to an incident on our cloud provider. Existing databases are not affected. https://status.turso.tech/incident/403175 Wed, 24 Jul 2024 19:49:00 -0000 https://status.turso.tech/incident/403175#4295d24884de17b5ead7a2a1bfe40677ca4ac1ed1dfce677bf924c478412f126 We have solved the incident https://status.turso.tech/incident/403175 Wed, 24 Jul 2024 19:41:00 -0000 https://status.turso.tech/incident/403175#7a5f48b33f7fd8055c6101fa9b9d71cf9009cc5708569884cbecf2f6cf95fd9b One of our cloud provider is currently having a failure in their APIs, we are working with them to solve the issue https://status.turso.tech/incident/385480 Sun, 16 Jun 2024 02:04:00 -0000 https://status.turso.tech/incident/385480#cce26475335ba8e11cc89a5d8084ad462d05e68e3e25c91fd623088ee1288297 Incident was resolved https://status.turso.tech/incident/381597 Sun, 09 Jun 2024 00:49:00 -0000 https://status.turso.tech/incident/381597#d07e018649896405fbbb3915f005d48771413a746869942ac843993c50a5a7fa The underlying issue was resolved. We're still monitoring the platform for any further problems. https://status.turso.tech/incident/381597 Sat, 08 Jun 2024 23:07:00 -0000 https://status.turso.tech/incident/381597#d38052b8268dc53cc4ff5e65c00590f999b469ffc23c26b11dd98949d1fb3758 Operations that require infrastructure allocation at South America may be disrupted or degraded. We're working with our cloud provider to resolve the issue. https://status.turso.tech/incident/377586 Fri, 31 May 2024 17:27:00 -0000 https://status.turso.tech/incident/377586#071a9ef6e9f825b0c542164b3fab7fbb0cf4d63dc942a2e1a82f337635e0282b They have rolledback the networking change and our services were back to normal https://status.turso.tech/incident/377586 Fri, 31 May 2024 17:15:00 -0000 https://status.turso.tech/incident/377586#9ea1b139bdb4d82c1ce14c1cff146df5496fe88d948a51cb3a5be09aa567b99d Our cloud provider had a network failure that impacted our main API, dashboard and some of our customers databases. https://status.turso.tech/incident/376003 Tue, 28 May 2024 19:11:00 -0000 https://status.turso.tech/incident/376003#e3ef87722a3fb92dac965a7e040b797f90584cc89d19401bd343f97702c5cefd A fix has been implemented and the problem was solved https://status.turso.tech/incident/376003 Tue, 28 May 2024 18:55:00 -0000 https://status.turso.tech/incident/376003#be48f52b5890f5ca33c3ac147029fbf1efe02543d742285cc2362235fb9803ad We have identified the cause and we are working on a solution https://status.turso.tech/incident/376003 Tue, 28 May 2024 18:54:00 -0000 https://status.turso.tech/incident/376003#d12eeb600b905d2bec155204cdbfa48e1a7ad3a6e7a164b09fbd9fff69a6db1c We are currently experiencing a failure in the usage metrics server, and all usage metrics are unavailable https://status.turso.tech/incident/361325 Sat, 27 Apr 2024 02:53:00 -0000 https://status.turso.tech/incident/361325#76183fa87f47190af1da2518956eef7a9411a2ed7f91ec908434bd8a6c4bb9b5 The issue has been resolved by the downstream provider https://status.turso.tech/incident/361325 Fri, 26 Apr 2024 23:44:00 -0000 https://status.turso.tech/incident/361325#07526af8221d31b33ec55866ff2c3a68a433dddc350303741c469775065676d0 We're seeing increased errors and latency on some parts of the platform. We're investigating the cause. https://status.turso.tech/incident/360285 Wed, 24 Apr 2024 18:40:00 -0000 https://status.turso.tech/incident/360285#ef9a09cc8531e84de5e0b1d3cb4d6f8ade9e4ca2c308d495cbe6a14aed63e961 The issue was resolved by our cloud provider. https://status.turso.tech/incident/354297 Fri, 12 Apr 2024 01:20:00 -0000 https://status.turso.tech/incident/354297#fcbb1c026bb90dec88dacc7a62c32d99e5ec8167d7d124e39a99b87b96bacb7d The issue has been fixed. https://status.turso.tech/incident/354297 Fri, 12 Apr 2024 00:23:00 -0000 https://status.turso.tech/incident/354297#e6babf119f0874988fe197a57c15bb5e948b2e19fe43f3ef2700bccbd642a2ed API operations that require the creation and validation of database\group credentials are disrupted. This includes creating new groups since they must be configured with public keys to validate tokens. https://status.turso.tech/incident/343086 Tue, 19 Mar 2024 16:06:00 -0000 https://status.turso.tech/incident/343086#1ddc3bdbc695b4ff4cdbc4c699da8e508c0e3ad12fc1e20b315395fc506f5441 The cloud provider has fixed the issue. https://status.turso.tech/incident/343086 Tue, 19 Mar 2024 15:33:00 -0000 https://status.turso.tech/incident/343086#f03925cc2cd49ae321bc582c80992fd4262a6ba4ca5a104ce81ab9f6aa8c5e2f Infrastructure allocation is disrupted due to a failure on a downstream cloud provider. Group creation and the addition of new locations may be affected. https://status.turso.tech/incident/341289 Fri, 15 Mar 2024 14:47:00 -0000 https://status.turso.tech/incident/341289#53e96c9db1a5d8233d8200355271b5bc3e15e850b43378700ae96f86d3584c28 Problem was fixed https://status.turso.tech/incident/341289 Fri, 15 Mar 2024 14:25:00 -0000 https://status.turso.tech/incident/341289#0dc9decbe0516ef750ee8c3193a25d43b7c75027afe51ea76ea93a544b8fb0f5 Group creation API is being impacted by an issue with our cloud provider. We are in contact with them. https://status.turso.tech/incident/323953 Thu, 08 Feb 2024 07:20:00 -0000 https://status.turso.tech/incident/323953#3d0cfbd2d13d23f7fd0b21ebce4a8df8115bb1659cf65afc2b45255b46e611ff All systems are operating normally now https://status.turso.tech/incident/323953 Thu, 08 Feb 2024 05:11:00 -0000 https://status.turso.tech/incident/323953#b1c272e76eb61c141ed18898c65ef82b88af62794be7e6794e86033016ebeeb8 Due to the issues at cloud provider, group creation and replication are failing. Existing database operations are working as usual https://status.turso.tech/incident/323718 Wed, 07 Feb 2024 21:36:00 -0000 https://status.turso.tech/incident/323718#2ec8fce8d94b1469041e0abca9f21496bc7dbf1649b8c0783c421d84ed82c2c9 All systems are operating normally now https://status.turso.tech/incident/323718 Wed, 07 Feb 2024 20:46:00 -0000 https://status.turso.tech/incident/323718#b46919c9dc0a290ed4d6e77e51d5718d9f2cadde419c702be7cf44ed118cb510 We are not being able to create databases that require new instances. This will affect all users that are creating groups or don't have a group yet. https://status.turso.tech/incident/307873 Wed, 03 Jan 2024 11:30:00 -0000 https://status.turso.tech/incident/307873#ba0086e0c186895829d0f418ed65e2b1979e9566dbabfbc6294e4ceff52d928f fixed by the cloud provider https://status.turso.tech/incident/307873 Wed, 03 Jan 2024 01:30:00 -0000 https://status.turso.tech/incident/307873#eda94533f22c2655fb4f3f41179cd50b1b7264f28dd88480ef549a98ae2a4a8b Due to the issues at cloud provider, group creation and replication are failing. Existing database operations are working as usual https://status.turso.tech/incident/307646 Tue, 02 Jan 2024 21:00:00 -0000 https://status.turso.tech/incident/307646#81a7369012154cbfd7dd3d76621f4d922c640bd0e1800223c49639a0ee3c1357 fixed by the cloud provider https://status.turso.tech/incident/307646 Tue, 02 Jan 2024 20:21:00 -0000 https://status.turso.tech/incident/307646#a0b98a6ac73c5eb912ffa3a4809d799d322801c5e77ca330d9bdbdc5f7876819 Creating new groups and replicating a group in a new location is disrupted due to an incident on our cloud provider. We're in touch with them. https://status.turso.tech/incident/289845 Mon, 20 Nov 2023 15:18:00 -0000 https://status.turso.tech/incident/289845#124b5ec31279b98688e30ebea79d30e02e891f0c84efe26d0926b1a4c06ad278 A fix was deployed and we are working normally https://status.turso.tech/incident/289845 Mon, 20 Nov 2023 15:09:00 -0000 https://status.turso.tech/incident/289845#870c88e8b7c8bdce0a884719c7c956a547b0a52f4540f25737ec8fe764f7afdb We are currently experiencing an outage caused by a bug deployed to production. We've already identified the root cause and we are working on a solution. https://status.turso.tech/incident/287023 Tue, 14 Nov 2023 02:12:00 -0000 https://status.turso.tech/incident/287023#6e393a2e1fd0b7a89d56d02332dc0597b470ec979f6aeedd831f6e0ca411d731 The fix was deployed by our upstream provider and everything is back to normal. https://status.turso.tech/incident/287023 Tue, 14 Nov 2023 01:47:00 -0000 https://status.turso.tech/incident/287023#7ca4fa0efb9d87e79abb7b442c5b42013e2090e88432753c87ca9b03f17f55d4 A disruption in one of our upstream services caused by networking issues made most of our services experience disruption. https://status.turso.tech/incident/285396 Fri, 10 Nov 2023 18:09:00 -0000 https://status.turso.tech/incident/285396#2a1d56904661300cd8cb62f5b1d17acadcb57f2403cc9b9d8183916c1b6870b1 We've deployed a fix and everything is working normally now. https://status.turso.tech/incident/285396 Fri, 10 Nov 2023 17:40:00 -0000 https://status.turso.tech/incident/285396#20a2549ba01f53bfbce2f162e27b456e640f4a42c25c4c105b8cb8a9f891f504 You are currently unable to create or destroy databases because of suspected underlying infrastructure issue. https://status.turso.tech/incident/279682 Mon, 30 Oct 2023 13:40:00 -0000 https://status.turso.tech/incident/279682#f8b5baf49649e45a60fde31f5309ad3680249bd42bf643005a5886eab85d9d94 The issue is resolved. https://status.turso.tech/incident/279682 Mon, 30 Oct 2023 08:19:00 -0000 https://status.turso.tech/incident/279682#bf6befdf313904fc657db6e1011094fbd745d83948de682df6850b1c01407031 Creation of new instances is disrupted. https://status.turso.tech/incident/277137 Tue, 24 Oct 2023 18:47:00 -0000 https://status.turso.tech/incident/277137#8f82e75f27d65939d7c5aae8c7b77af8a75b515e412b053020b1698c355ab54d The incident was resolved. https://status.turso.tech/incident/277137 Tue, 24 Oct 2023 18:26:00 -0000 https://status.turso.tech/incident/277137#751f365015de5b4c413cac4a44c498bf05697b96a8517045a3062c0c9766a7c7 Group creation is failing due to a problem with a downstream infrastructure provider. We're working with them to fix it. https://status.turso.tech/incident/273530 Mon, 16 Oct 2023 17:20:00 -0000 https://status.turso.tech/incident/273530#d9c7df50d2978cc2fca361969b3f79d34c6c6dee45eb2e69e0810eb51377b322 The issue was resolved. https://status.turso.tech/incident/273530 Mon, 16 Oct 2023 17:12:00 -0000 https://status.turso.tech/incident/273530#7586b98695c42789313b2d652c1c607765c3ea253520f975902967f8520af781 We are monitoring the results of the fix that was deployted https://status.turso.tech/incident/273530 Mon, 16 Oct 2023 16:49:00 -0000 https://status.turso.tech/incident/273530#030fb5108813ca6f1d9c3f01a0ac396ac7edecdb283889b98aff45d0f6fb1144 Our cloud provider is working on a fix https://status.turso.tech/incident/273530 Mon, 16 Oct 2023 16:23:00 -0000 https://status.turso.tech/incident/273530#a10ed8b304172511f04d49cc8e74a9bd94b2324c6bfa6a28ebf0ef63ebb34667 Our cloud provider is having issues with provisioning volumes, we are working with them to restore our service back to normal. Databases already created are working normally. https://status.turso.tech/incident/258902 Wed, 13 Sep 2023 21:00:00 -0000 https://status.turso.tech/incident/258902#9e25ceb924b737cd6e09186ca2dbbf83004798597fefdd5f85977ac980fb24d8 The issue has been resolved. https://status.turso.tech/incident/258902 Wed, 13 Sep 2023 20:30:00 -0000 https://status.turso.tech/incident/258902#8a909bc087996365479bcd5959e2b525b8f1b2245cdd876b5eb3d6495f8124c8 Any operations that require us to change infrastructure are disrupted due to an issue with our cloud provider. https://status.turso.tech/incident/258467 Tue, 12 Sep 2023 20:25:00 -0000 https://status.turso.tech/incident/258467#edaee0d4a9f6c0f42ac723428d5a1834f4434bad6359355492b65afebedaa17b The issue has been resolved. https://status.turso.tech/incident/258467 Tue, 12 Sep 2023 18:56:00 -0000 https://status.turso.tech/incident/258467#79e1188fef8acefe9b55544ef247d75d86570577818e954eda62756adf202ebd All commands that require infrastructure change are disrupted due to an incident on our cloud provider. https://status.turso.tech/incident/254740 Mon, 04 Sep 2023 09:16:00 -0000 https://status.turso.tech/incident/254740#d6f4808970d19f118e5847f3ca15fa1c54faf5ea311267e89033d5a3b7b8dd6f Fly is currently having a major outage on the API layer, which is causing Turso database creation to be slow. https://status.turso.tech/incident/190551 Wed, 29 Mar 2023 12:08:00 -0000 https://status.turso.tech/incident/190551#41c11804a825fb1d422684e5033251fc405b232240fc911eb545eb2686587dcf Due to infrastructure provider issues, database creation is slower than usual.