Incidents reported on status page for Jit https://status.jit.io/ https://d1lppblt9t2x15.cloudfront.net/logos/594f41e20ebf8935369a527c72290cad.png https://status.jit.io/ en https://status.jit.io/ Tue, 17 Jun 2025 20:15:58 +0000 https://status.jit.io/#14902ec6f5f1004832c128963c36340f63cb17b3ec7e7adbdaf7487b47480195 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 17 Jun 2025 19:55:56 +0000 https://status.jit.io/#14902ec6f5f1004832c128963c36340f63cb17b3ec7e7adbdaf7487b47480195 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 12 Jun 2025 20:31:24 +0000 https://status.jit.io/#f31bc5b994c70e5bcacbfaca8bfe0a8d5b93c9165364dfea403a170b91d3f3ec GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 12 Jun 2025 18:51:09 +0000 https://status.jit.io/#f31bc5b994c70e5bcacbfaca8bfe0a8d5b93c9165364dfea403a170b91d3f3ec GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 05 Jun 2025 19:31:08 +0000 https://status.jit.io/#f577954d1e46e0999e6d4e21fde10a52a194cbd50c4ffab92804850a8d8ab817 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 05 Jun 2025 18:01:08 +0000 https://status.jit.io/#f577954d1e46e0999e6d4e21fde10a52a194cbd50c4ffab92804850a8d8ab817 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 04 Jun 2025 15:56:20 +0000 https://status.jit.io/#64c671893465e29ea42f5130039bbd3c0e9163746a2f461b6b4ad24e5d39861c GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 04 Jun 2025 15:16:20 +0000 https://status.jit.io/#64c671893465e29ea42f5130039bbd3c0e9163746a2f461b6b4ad24e5d39861c GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 28 May 2025 14:46:21 +0000 https://status.jit.io/#3340aa13a50eaa4c61cbf5c828557caabcc84e8037e41bc9f7354c4cc1996ad3 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 28 May 2025 11:51:18 +0000 https://status.jit.io/#3340aa13a50eaa4c61cbf5c828557caabcc84e8037e41bc9f7354c4cc1996ad3 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 27 May 2025 13:36:24 +0000 https://status.jit.io/#1e1815c133d82061087c89fd7596c3f17e45edadb256e742ef4ffcadee8d30ee GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 27 May 2025 12:31:19 +0000 https://status.jit.io/#1e1815c133d82061087c89fd7596c3f17e45edadb256e742ef4ffcadee8d30ee GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 26 May 2025 09:51:12 +0000 https://status.jit.io/#00fb1288c66a39ea3a61f21603d9a09ddfb9d6a7bbd005677e6f91721dab63c3 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 26 May 2025 07:26:11 +0000 https://status.jit.io/#00fb1288c66a39ea3a61f21603d9a09ddfb9d6a7bbd005677e6f91721dab63c3 GitHub Pull Request Scanning Services went down https://status.jit.io/ Fri, 23 May 2025 18:35:51 +0000 https://status.jit.io/#75193791fd72e6b5337b95da18b9c81f8d05dfc83834a54b4b569c4b857a51bc GitHub Pull Request Scanning Services recovered https://status.jit.io/ Fri, 23 May 2025 18:30:51 +0000 https://status.jit.io/#75193791fd72e6b5337b95da18b9c81f8d05dfc83834a54b4b569c4b857a51bc GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 22 May 2025 09:21:04 +0000 https://status.jit.io/#51b464e0cfc5e09c6867c2d10b535eb39d6f7bcb1220170030388f8826f10034 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 22 May 2025 07:45:59 +0000 https://status.jit.io/#51b464e0cfc5e09c6867c2d10b535eb39d6f7bcb1220170030388f8826f10034 GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 28 Apr 2025 11:11:10 +0000 https://status.jit.io/#13ed9eb547cd2b78dd85542fbb43bc52d65838ee6267680facb68521d672e5ed GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 28 Apr 2025 08:06:15 +0000 https://status.jit.io/#13ed9eb547cd2b78dd85542fbb43bc52d65838ee6267680facb68521d672e5ed GitHub Pull Request Scanning Services went down https://status.jit.io/incident/550273 Sat, 26 Apr 2025 09:00:22 +0000 https://status.jit.io/incident/550273#d547f2091097663a48ee2345fd57328e587af6b0acafc5332e2e81a481d21d1e Maintenance completed https://status.jit.io/incident/550273 Sat, 26 Apr 2025 09:00:22 +0000 https://status.jit.io/incident/550273#d547f2091097663a48ee2345fd57328e587af6b0acafc5332e2e81a481d21d1e Maintenance completed https://status.jit.io/incident/550273 Sat, 26 Apr 2025 09:00:22 +0000 https://status.jit.io/incident/550273#d547f2091097663a48ee2345fd57328e587af6b0acafc5332e2e81a481d21d1e Maintenance completed https://status.jit.io/incident/550273 Sat, 26 Apr 2025 07:00:00 -0000 https://status.jit.io/incident/550273#0d000411dcc4de29da3f0d4aa1593bf4c997a3d569212dab3d6fe0d45bde8329 We will be performing scheduled maintenance on Saturday 26th of April 2025 from 08:00 UTC to 10:00 UTC. During this window, there will be a 40-minute period of full downtime on the Jit platform. During this time, no scans will run. No action is required from customers. Once the system is back online, all scans will automatically resume as normal. If you have any questions or concerns, please don’t hesitate to reach out to the Jit team at any time. We appreciate your understanding and patience. — The Jit Team https://status.jit.io/incident/550273 Sat, 26 Apr 2025 07:00:00 -0000 https://status.jit.io/incident/550273#0d000411dcc4de29da3f0d4aa1593bf4c997a3d569212dab3d6fe0d45bde8329 We will be performing scheduled maintenance on Saturday 26th of April 2025 from 08:00 UTC to 10:00 UTC. During this window, there will be a 40-minute period of full downtime on the Jit platform. During this time, no scans will run. No action is required from customers. Once the system is back online, all scans will automatically resume as normal. If you have any questions or concerns, please don’t hesitate to reach out to the Jit team at any time. We appreciate your understanding and patience. — The Jit Team https://status.jit.io/incident/550273 Sat, 26 Apr 2025 07:00:00 -0000 https://status.jit.io/incident/550273#0d000411dcc4de29da3f0d4aa1593bf4c997a3d569212dab3d6fe0d45bde8329 We will be performing scheduled maintenance on Saturday 26th of April 2025 from 08:00 UTC to 10:00 UTC. During this window, there will be a 40-minute period of full downtime on the Jit platform. During this time, no scans will run. No action is required from customers. Once the system is back online, all scans will automatically resume as normal. If you have any questions or concerns, please don’t hesitate to reach out to the Jit team at any time. We appreciate your understanding and patience. — The Jit Team https://status.jit.io/ Wed, 23 Apr 2025 07:46:09 +0000 https://status.jit.io/#08a8dd982292559045b78a9d91f69b9bdba05d4a82cb9f7f6d24c9ba5fa97938 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 23 Apr 2025 07:21:10 +0000 https://status.jit.io/#08a8dd982292559045b78a9d91f69b9bdba05d4a82cb9f7f6d24c9ba5fa97938 GitHub Pull Request Scanning Services went down https://status.jit.io/incident/538675 Sat, 05 Apr 2025 09:00:00 +0000 https://status.jit.io/incident/538675#6ae7ab91a4a4e44bda2aa2abb9b59211864f8cdc235136b9d5ed5d6088854c07 Maintenance completed https://status.jit.io/incident/538675 Sat, 05 Apr 2025 09:00:00 +0000 https://status.jit.io/incident/538675#6ae7ab91a4a4e44bda2aa2abb9b59211864f8cdc235136b9d5ed5d6088854c07 Maintenance completed https://status.jit.io/incident/538675 Sat, 05 Apr 2025 09:00:00 +0000 https://status.jit.io/incident/538675#6ae7ab91a4a4e44bda2aa2abb9b59211864f8cdc235136b9d5ed5d6088854c07 Maintenance completed https://status.jit.io/incident/538675 Sat, 05 Apr 2025 07:00:00 -0000 https://status.jit.io/incident/538675#112c32f923c921f83501d56ff081071c1d6b446f3b1e7c21b10a9bff3a132b54 We will be performing scheduled maintenance on Saturday from 07:00 UTC to 9:00 UTC. During this window, there will be a 40-minute period of full downtime on the Jit platform. During this time, no scans will run. No action is required from customers. Once the system is back online, all scans will automatically resume as normal. If you have any questions or concerns, please don’t hesitate to reach out to the Jit team at any time. We appreciate your understanding and patience. — The Jit Team https://status.jit.io/incident/538675 Sat, 05 Apr 2025 07:00:00 -0000 https://status.jit.io/incident/538675#112c32f923c921f83501d56ff081071c1d6b446f3b1e7c21b10a9bff3a132b54 We will be performing scheduled maintenance on Saturday from 07:00 UTC to 9:00 UTC. During this window, there will be a 40-minute period of full downtime on the Jit platform. During this time, no scans will run. No action is required from customers. Once the system is back online, all scans will automatically resume as normal. If you have any questions or concerns, please don’t hesitate to reach out to the Jit team at any time. We appreciate your understanding and patience. — The Jit Team https://status.jit.io/incident/538675 Sat, 05 Apr 2025 07:00:00 -0000 https://status.jit.io/incident/538675#112c32f923c921f83501d56ff081071c1d6b446f3b1e7c21b10a9bff3a132b54 We will be performing scheduled maintenance on Saturday from 07:00 UTC to 9:00 UTC. During this window, there will be a 40-minute period of full downtime on the Jit platform. During this time, no scans will run. No action is required from customers. Once the system is back online, all scans will automatically resume as normal. If you have any questions or concerns, please don’t hesitate to reach out to the Jit team at any time. We appreciate your understanding and patience. — The Jit Team https://status.jit.io/incident/495658 Tue, 14 Jan 2025 12:31:00 -0000 https://status.jit.io/incident/495658#91862a5f93a21389d3aae10c73829ac24424b0631c08f552a2e4b2191f991bba Start Time: 10:10 UTC Resolved Time: 11:43 UTC A bug was found in production causing full scans and PR's submitted during the incident time to get stuck and not run. The source of the bug was rolled back after our monitoring alerted us of this failure. All suck PR's have been resubmitted on the backend and should not have any issues. If you have a stuck PR please let us know at support@jit.io All services have returned to normal. If you have any questions, you can reach out to support or your AE. https://status.jit.io/incident/449390 Wed, 23 Oct 2024 15:10:00 -0000 https://status.jit.io/incident/449390#2175873ae9b50b2a43d52811a2a125ddebbce571fd736a7b8a0375f013e42283 Scans in GitHub Pull Requests are failing for a small percentage of our users. This issue is related to one of our internal services. We're working on fixing the issue, and it will be available again for all users very soon. https://status.jit.io/incident/402913 Wed, 24 Jul 2024 10:05:00 -0000 https://status.jit.io/incident/402913#8bed41157314ca9c4b8bfc1a0b52dbf7f6cc06242872baaf7856fc6f20fb94c4 An authentication service experienced a disruption due to a third-party vendor issue. The engineering team collaborated with the vendor to resolve the problem. After coordination efforts, the service was fully restored. https://status.jit.io/incident/402913 Wed, 24 Jul 2024 09:01:00 -0000 https://status.jit.io/incident/402913#880e929d175c3f503c677dd5362547cc51fddce17387b9a48e755693aad9a3b0 We are currently experiencing a disruption in our authentication services, stemming from an issue with our third-party authentication vendor. Our engineering team is actively working with the vendor to resolve the problem and restore normal operations as soon as possible. We apologize for any inconvenience this may cause and will provide updates as more information becomes available. https://status.jit.io/incident/350111 Wed, 03 Apr 2024 08:18:00 -0000 https://status.jit.io/incident/350111#dc277b29fdfc653fec0e0e38744494b4ef195933fc527e73bbff955a2c422ed9 We are currently experiencing a disruption in our authentication services, stemming from an issue with our third-party authentication vendor. Our engineering team is actively working with the vendor to resolve the problem and restore normal operations as soon as possible. We apologize for any inconvenience this may cause and will provide updates as more information becomes available. https://status.jit.io/incident/350111 Wed, 03 Apr 2024 08:18:00 -0000 https://status.jit.io/incident/350111#dc277b29fdfc653fec0e0e38744494b4ef195933fc527e73bbff955a2c422ed9 We are currently experiencing a disruption in our authentication services, stemming from an issue with our third-party authentication vendor. Our engineering team is actively working with the vendor to resolve the problem and restore normal operations as soon as possible. We apologize for any inconvenience this may cause and will provide updates as more information becomes available. https://status.jit.io/incident/350111 Wed, 03 Apr 2024 08:18:00 -0000 https://status.jit.io/incident/350111#dc277b29fdfc653fec0e0e38744494b4ef195933fc527e73bbff955a2c422ed9 We are currently experiencing a disruption in our authentication services, stemming from an issue with our third-party authentication vendor. Our engineering team is actively working with the vendor to resolve the problem and restore normal operations as soon as possible. We apologize for any inconvenience this may cause and will provide updates as more information becomes available.