Incidents reported on status page for Longship https://status.longship.io/ https://d1lppblt9t2x15.cloudfront.net/logos/35090d81bca4230db3930de6f1a36087.png https://status.longship.io/ en https://status.longship.io/ Wed, 25 Jun 2025 13:14:22 +0000 https://status.longship.io/#eea120b771d843e3ecd5ed73410faf3c8eae47ae4e49f10dc804c5e7893fd815 Websockets recovered https://status.longship.io/ Wed, 25 Jun 2025 13:05:10 +0000 https://status.longship.io/#eea120b771d843e3ecd5ed73410faf3c8eae47ae4e49f10dc804c5e7893fd815 Websockets went down https://status.longship.io/ Wed, 18 Jun 2025 12:28:06 +0000 https://status.longship.io/#877a3876c9eb2e165d6eb20bf6df79a38a7759f42f17d1df1fc9db5c8c4a9967 Portal recovered https://status.longship.io/ Wed, 18 Jun 2025 12:26:45 +0000 https://status.longship.io/#877a3876c9eb2e165d6eb20bf6df79a38a7759f42f17d1df1fc9db5c8c4a9967 Portal went down https://status.longship.io/incident/595517 Wed, 28 May 2025 11:40:00 -0000 https://status.longship.io/incident/595517#7fa0d0988f57b8715f1d632c05afeb277291534a9acce4b4f07feb6f5a27695d The Portal has missed one health check. https://status.longship.io/ Wed, 28 May 2025 10:20:00 +0000 https://status.longship.io/#9b3d146094b45c9e758f48e232da4573ccdc9df945e10f44a69e6d7db649a4d5 Portal recovered https://status.longship.io/ Wed, 28 May 2025 10:17:09 +0000 https://status.longship.io/#9b3d146094b45c9e758f48e232da4573ccdc9df945e10f44a69e6d7db649a4d5 Portal went down https://status.longship.io/incident/541953 Tue, 08 Apr 2025 15:16:00 -0000 https://status.longship.io/incident/541953#7c3e8261f17c60758829e919206528f6519ec907eccf93c055985eda12744dd1 After a new release the Portal took some time to be fully up to speed. https://status.longship.io/ Tue, 08 Apr 2025 08:26:57 +0000 https://status.longship.io/#279119eea461211fe847c762bf511ce6a548c443929609c5f3e685078dc4cb77 Portal recovered https://status.longship.io/ Tue, 08 Apr 2025 08:19:23 +0000 https://status.longship.io/#279119eea461211fe847c762bf511ce6a548c443929609c5f3e685078dc4cb77 Portal went down https://status.longship.io/incident/530075 Tue, 18 Mar 2025 09:00:00 -0000 https://status.longship.io/incident/530075#e569ca81dfe67d4fca8757899bfa6d68298fb617f526738865580312b2b0c52e The Hubject health endpoint was broken. The Hubject service was running normally. https://status.longship.io/incident/523166 Wed, 05 Mar 2025 15:16:00 -0000 https://status.longship.io/incident/523166#198e3903c3caba9733e966d0dbb6948f483c9210bc0652f73bf77c96bb60a371 The ssl certificate was renewed by Azure. https://status.longship.io/incident/523136 Tue, 04 Mar 2025 13:57:00 -0000 https://status.longship.io/incident/523136#15221fe027af32c80c0f020b85b76020f6b2fcdeebcf5e7b9c305e5e2d3ff9f1 The Portal was released. Thus we missed a couple of health checks. https://status.longship.io/incident/523171 Mon, 03 Mar 2025 15:20:00 -0000 https://status.longship.io/incident/523171#c728be7541f886481847a23e961be2c9231f108217f1d8e4e5e1323b9ae37004 This was caused by a release but we didn't see any impact. https://status.longship.io/incident/523132 Tue, 18 Feb 2025 13:51:00 -0000 https://status.longship.io/incident/523132#6be2b4e2b5d211c0dcd4e9ddc76012bb9d7b54a26dbbf77b00a53d9e4c44ba44 The Portal was released. Thus we missed one health check. https://status.longship.io/incident/523169 Wed, 05 Feb 2025 15:17:00 -0000 https://status.longship.io/incident/523169#560fba684333c9413a6bbede3fb49cb591d8c6109a7987d9eaed5efbce13ce84 The ssl certificate was renewed by Azure for one of our hostnames. https://status.longship.io/incident/523172 Thu, 16 Jan 2025 15:22:00 -0000 https://status.longship.io/incident/523172#cc8cd967a64b79d584f0c5b88e9dd0043e03a3ab5c98b162a1a4beb80db1bbb1 The ssl certificate was renewed by Azure for one of our hostnames. https://status.longship.io/incident/523165 Thu, 12 Dec 2024 15:13:00 -0000 https://status.longship.io/incident/523165#3f246ee70355f9d63e4bf0e35284d2be457e7c8c18eb9e25450b07918457b1ae During this release we experienced some downtime because one of the instances didn't start properly. https://status.longship.io/incident/461373 Thu, 14 Nov 2024 10:29:00 -0000 https://status.longship.io/incident/461373#da2e0f4969cd8d8649a45d6a3ec03061ad90ea6a150364c9d5a85d60ba2a93d6 We ping a health endpoint on a regular interval and one of the pings was missed. https://status.longship.io/incident/391878 Mon, 01 Jul 2024 10:16:00 -0000 https://status.longship.io/incident/391878#9a0e2552579e8b5eb3aaebfee1cb59950f3d341698ce298a2d0802c4a9f91188 We have identified the root cause of the problem. One of the instances was experiencing latency issues. This resulted in a reset of that instance by our cloud platform provider. We were already aware of this risk. The solution is already under construction by our development team. https://status.longship.io/incident/391878 Mon, 01 Jul 2024 09:29:00 -0000 https://status.longship.io/incident/391878#90a5000db55bace1ec16f5e5750a1fc78e73b07b61169fe13d15c19d3226aeee We are experiencing a degraded performance on our server, it is still working and functional. Investigation is ongoing. https://status.longship.io/incident/391938 Sat, 18 May 2024 11:53:00 -0000 https://status.longship.io/incident/391938#88536bdc5578fe6aadf23d3912ebad9f1916433cedbaa1a524234236785cf0e0 A release with new features caused some unexpected downtime, a new release fixed the issue. https://status.longship.io/incident/391924 Tue, 14 May 2024 11:39:00 -0000 https://status.longship.io/incident/391924#79823b533e1a9427b15a71db63dcbd1fffb1fceda4f1fa0225bc16d0d20b8220 File server upgrade caused delayed responses https://status.longship.io/incident/391933 Wed, 08 May 2024 11:50:00 -0000 https://status.longship.io/incident/391933#f718c4a68b647c8caec9c3f9cdabc378fc2904b5cb9a63b49eaf47de6e037804 The API was slow during a short moment of time and is fixed. https://status.longship.io/incident/391929 Wed, 08 May 2024 11:44:00 -0000 https://status.longship.io/incident/391929#d7dbd2b662698b87f32ecd44b5965d0aefd05014295617a15a67b264b5333f8b A upgrade from our cloud provider caused a degraded performance. The server was online, but response times were unacceptable. Restarting the services fixed the issue eventually. https://status.longship.io/incident/362695 Mon, 29 Apr 2024 08:27:00 -0000 https://status.longship.io/incident/362695#28591433f2b1bd6302a09896639478448266b488e9011884647280e049847de9 There was a misconfiguration in the DNS provider https://status.longship.io/incident/356348 Tue, 16 Apr 2024 16:24:00 -0000 https://status.longship.io/incident/356348#6c2c6a7b5efc3c14921f8172cad1f5e96b556014debbc173cc3e163bbf4cbcf8 The database was busy for a very brief period of time. We are already working on optimizing the database usage to make this more efficient and stable in the future. https://status.longship.io/incident/391932 Thu, 11 Apr 2024 13:49:00 -0000 https://status.longship.io/incident/391932#0a0f62ce9e155986f277dda29f8267c47b077c6643a7c37d31f23e683b0d24a4 The new instance was unstable en needed to be restarted, this resolved the issue. https://status.longship.io/incident/391931 Wed, 10 Apr 2024 09:47:00 -0000 https://status.longship.io/incident/391931#8109374ee3e6f16a71a79b2c67e3bd5cca0477eb80d77be4b626463babb8227c Memory issues are identified on the websocket server, a new instance is added and fixed the issue. https://status.longship.io/incident/349554 Fri, 29 Mar 2024 10:52:00 -0000 https://status.longship.io/incident/349554#579ecceb10f6c85cefc6de37e9f735ab4abe650d8f06445396200d2b39085203 Our cloud platform provider updated the servers on which our websocket application runs. https://status.longship.io/incident/332312 Mon, 26 Feb 2024 21:52:00 -0000 https://status.longship.io/incident/332312#7bc98923188c4982200b3a354b3568caec2ca1ac571327094709a9ece9fc9fb1 This release introduced zero downtime deployments for future Hub releases. https://status.longship.io/incident/344536 Fri, 23 Feb 2024 11:00:00 -0000 https://status.longship.io/incident/344536#8a2fccf5fb23b994a23e7249aa174cfd92a453f302929fbdacd8e6d2d7094570 One of the instances of our portal was broke. It was recovered by our auto-heal functionality but caused a little downtime on this one instance. The other ones were not affected, so most users won't have notified this problem at all. https://status.longship.io/incident/326780 Fri, 09 Feb 2024 16:01:00 -0000 https://status.longship.io/incident/326780#76c329ce0a0e417bf24b35a79621a11187d3752548dcef90231ed894d100705c After releasing the HUB we noticed that a component did not start. That is why we rolled back the previous version of the HUB which resolved the issue of not being able to perform live authorizations. https://status.longship.io/incident/344532 Wed, 31 Jan 2024 10:58:00 -0000 https://status.longship.io/incident/344532#6ca056d5e9997133ac3e536085f507cff56a97385091e0b1f50d4fae2a5aed4b We tried to release a new version of the hub with stability fixes, but we had to roll back the release due to unforeseen issues. We are planning the new release for next month now. https://status.longship.io/incident/344533 Mon, 22 Jan 2024 10:59:00 -0000 https://status.longship.io/incident/344533#9ec9c3b4720c4103856e3d69e38535fdcd094baf64d2bf046bf119ffcb70e3e4 There was a regular maintenance of our cloud provider causing a little downtime. There is a new release coming which will resolve these kind of issues. https://status.longship.io/incident/302008 Mon, 18 Dec 2023 08:40:00 -0000 https://status.longship.io/incident/302008#3a077c53df98d1f73321fb377cf216d468d88b8f5b5c3e685a0c122226a34b11 The Portal was released with a newer version but something went wrong in the release process. https://status.longship.io/incident/297268 Wed, 29 Nov 2023 13:58:00 -0000 https://status.longship.io/incident/297268#c374364f4eac9bf940359ecf2c9dc630006ca158007ff7aee991e6354e986a7e Instance is recycled and working again. https://status.longship.io/incident/297269 Mon, 27 Nov 2023 13:59:00 -0000 https://status.longship.io/incident/297269#94a88cd62384957eba09157b693fcc5ad8e5aa68eb416e233db95586d16126d7 No real downtime, instance is recycled. https://status.longship.io/incident/290711 Mon, 20 Nov 2023 12:48:00 -0000 https://status.longship.io/incident/290711#26adbf74867f8c67bb00549ccbcac01b3f1a5a9293b158f909eed66843a84db7 The connection with Hubject was instable due to a technical issue. Our cloud provider helped investigating the issue and proposed some solutions to prevent this in the future. https://status.longship.io/incident/290708 Thu, 16 Nov 2023 12:44:00 -0000 https://status.longship.io/incident/290708#8cfed270439a568374c70a19b2633b3a155fb4a5adcec950437711770330be03 The service was busy and didn't respond in time, was not a real offline scenario. The delay was caused in a spike of requests. https://status.longship.io/incident/290712 Tue, 07 Nov 2023 12:50:00 -0000 https://status.longship.io/incident/290712#8f115e13fdfbfe4786ccde23e0b94fd4b26011e30433e9eb8f444dca76dc2713 System needed to be restarted by our cloud provider and caused a moment of delay/downtime. https://status.longship.io/incident/283283 Mon, 06 Nov 2023 21:18:00 -0000 https://status.longship.io/incident/283283#f246ee635cffe175d0fdce140a559a5ebf049cc8bbfac860d3e6091085070d9b A release of the hub caused one of the instances to be unstable, disconnected sockets can be a consequence. Issue is resolved. https://status.longship.io/incident/276691 Tue, 17 Oct 2023 07:00:00 -0000 https://status.longship.io/incident/276691#4974999d32e45e25051beef766a90f7b923257a98acadc99994890e48b5f434b The performance was poor for a short period of time which caused this downtime. https://status.longship.io/incident/276693 Sun, 10 Sep 2023 18:00:00 -0000 https://status.longship.io/incident/276693#17612cefdccd38b8e23adc4374493741eed63d73e6edfa7eb6f82d538e4ffdce During a maintenance action, the connect service was not restarted correctly which caused the downtime. https://status.longship.io/incident/276694 Fri, 08 Sep 2023 12:00:00 -0000 https://status.longship.io/incident/276694#54ab065cc93ecd0e71c1a53a51bf7fe16dfbffd1b4f2753f05f9bed65b5e76d8 The status on the dashboard is wrongly depicted. We are in discussion with our status page provider and they acknowledged the error. https://status.longship.io/incident/276689 Tue, 05 Sep 2023 18:29:00 -0000 https://status.longship.io/incident/276689#a2b4954456401264fe7516cb9c3ba8a8ee77a70d300ba5f6d1997efabde22f48 A reboot of one of our Hubject services caused a couple of minutes downtime. https://status.longship.io/incident/231047 Tue, 27 Jun 2023 12:50:00 -0000 https://status.longship.io/incident/231047#307f77e72abef9b5f3bf6f2f46d3f2ad2603999f46664d57194c7eeb4629f0ca The services were restarted and caused a few moments of downtime. https://status.longship.io/incident/219990 Wed, 14 Jun 2023 07:10:00 -0000 https://status.longship.io/incident/219990#58aaaa482eca07028f57cb0170b7916dfb8ba6aec39a62f4e9b41771683be0c6 The service used to show the status has issues, the websocket service was working correctly. https://status.longship.io/incident/231046 Fri, 19 May 2023 21:47:00 -0000 https://status.longship.io/incident/231046#89828b3e28fc934521360e134a95c9ada116e6a303f197b51d45e5e763ede783 As mentioned previously, we experience some downtime during a release. That's why those are scheduled at off-peek moments. This was one of those releases. https://status.longship.io/incident/208554 Tue, 16 May 2023 09:42:00 -0000 https://status.longship.io/incident/208554#feda34c5596e1134a0572a3c73b1b170107cc191a95b546c95e0d85f7b107d2d A service was automatically restarted after health checks, which caused the health check to fail. Chargers were still able to connect due to our failover configuration. https://status.longship.io/incident/207605 Mon, 15 May 2023 08:34:00 -0000 https://status.longship.io/incident/207605#a1803ed8140a7df655fc73b31b3d0987dbeae5cfc2cee27308f2672b28d3b8e3 After the deployment of one of our services that service did not start correctly. After restarting this service it worked again. https://status.longship.io/incident/204741 Mon, 08 May 2023 07:48:00 -0000 https://status.longship.io/incident/204741#f3a57f840476ae7b30d9713dffb1b81a136fe54a73ffe3ff6c7b0a06ccc9b58d Because of the release of another dependent service the API was briefly unavailable. https://status.longship.io/incident/202564 Tue, 02 May 2023 07:57:00 -0000 https://status.longship.io/incident/202564#d4d83dc04a0dcbb52621977580c1c15d66ce04bbfe202d5d34ca8344f19aa430 The OCPI service was down for a brief second. The service was back up immediately after. This was resolved automatically. https://status.longship.io/incident/197215 Wed, 12 Apr 2023 13:41:00 -0000 https://status.longship.io/incident/197215#63ffda175fa72a7bdbec22af47acb88009511135292051d70c581e0bd1023078 A peek load of API calls was received and handled, although the auto-scaling took a few seconds to kick in. In those seconds the health check was performed and received an error. https://status.longship.io/incident/191363 Fri, 31 Mar 2023 01:00:00 -0000 https://status.longship.io/incident/191363#585c867d17b9aad23867c4c3e6d593a41ea1ecfca02c929ff3f5f8c9c9a46b14 The internal health checks of the service discovered an error and restarted the service as a precaution. The underlaying problem is identified and a solution is being worked on. https://status.longship.io/incident/191364 Wed, 08 Feb 2023 11:57:00 -0000 https://status.longship.io/incident/191364#44bb27bf5694384cbf50520960b9cb2f7e938b14b4030008cf118ec4d0f8ed30 The service was released which caused a few seconds of downtime. The new zero-downtime deployments are being introduced which will solve this issue. https://status.longship.io/incident/168056 Wed, 25 Jan 2023 08:02:00 -0000 https://status.longship.io/incident/168056#1a8e129a9c8a4596851e7c5b2ad83d4a7911403f75ff6fc01cbb401f2ff8b5c0 Our cloud infrastructure provider has been upgrading services which causes a restart of services. https://status.longship.io/incident/168056 Wed, 25 Jan 2023 08:02:00 -0000 https://status.longship.io/incident/168056#1a8e129a9c8a4596851e7c5b2ad83d4a7911403f75ff6fc01cbb401f2ff8b5c0 Our cloud infrastructure provider has been upgrading services which causes a restart of services. https://status.longship.io/incident/167973 Tue, 24 Jan 2023 07:02:00 -0000 https://status.longship.io/incident/167973#1f7a9b61f70cbeba1b364ddb49899c21617dc5d5a190b91bcdd331def452acf4 There was an upgrade in the cloud infrastructured which triggered a restart of the service. This caused about 5 minutes of downtime. https://status.longship.io/incident/168016 Fri, 20 Jan 2023 07:08:00 -0000 https://status.longship.io/incident/168016#1d60ee04fd5d90cb24dd9615261daf681b3d173aa67e0dd1cb77ddbdfbb1b55a Our hub service was restarted, which caused websockets to disconnect. The underlying infrastructure was rebooted as part of an upgrade. Failover was working properly and the services was available immediatly after the disconnect. https://status.longship.io/incident/153663 Wed, 11 Jan 2023 01:10:00 -0000 https://status.longship.io/incident/153663#73d650ce2bc603d91e9c1936738562103ce0bcdc22a597ffbc9bb568ccc41674 Our cloud environment experienced a infrastructure update which caused downtime of about 10 seconds. We added a monitor on our dashboard to see if this happens and mitigate when necessary. https://status.longship.io/incident/142797 Tue, 22 Nov 2022 09:22:00 -0000 https://status.longship.io/incident/142797#bbe46bcd5fe1e1e366a9d34c9ceed65c34535cee5727e335790a041886ba8427 A new version of the portal was released. Zero-downtime deployments for the portal are planned. https://status.longship.io/incident/137167 Fri, 18 Nov 2022 10:20:00 -0000 https://status.longship.io/incident/137167#f637fd7bc114f592f12456171cf1224ddc05c55d9ac32034251c1c15414bd1b8 Due to a change of the specific health endpoint of our API service, it was marked as offline which was not the case. We changed the health endpoint and it is showing the correct status again. https://status.longship.io/incident/142795 Mon, 12 Sep 2022 08:20:00 -0000 https://status.longship.io/incident/142795#8b2d9b1d6b62da72c13240733663857e7eaa785a66fd9b290dc5ae49bbd8e4ae Released a new version of the API which led to a small down-time window. The next release will add zero-downtime deployment capabilities to prevent this.