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/ Wed, 01 Oct 2025 17:00:53 +0000 https://status.jit.io/#e7a731d934bdcba66b02635994b7c2eac3ef4b1d9684f22ddb1e5406533e45b5 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 01 Oct 2025 08:11:10 +0000 https://status.jit.io/#e7a731d934bdcba66b02635994b7c2eac3ef4b1d9684f22ddb1e5406533e45b5 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 23 Sep 2025 17:46:12 +0000 https://status.jit.io/#4ad79a086c1a1a69df593e0c2c63ff3e157cc477b44de463e10e8b95b7141481 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 23 Sep 2025 17:31:09 +0000 https://status.jit.io/#4ad79a086c1a1a69df593e0c2c63ff3e157cc477b44de463e10e8b95b7141481 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 16 Sep 2025 18:31:00 +0000 https://status.jit.io/#517848f28649220b4cd96517e8722c1f9f78d895e7bf1feb4ea430b2473f15ce GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 16 Sep 2025 18:06:00 +0000 https://status.jit.io/#517848f28649220b4cd96517e8722c1f9f78d895e7bf1feb4ea430b2473f15ce GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 10 Sep 2025 14:06:17 +0000 https://status.jit.io/#4a26cbe68f45ab6db783cbf2b4943bdbb3084c3b7211e952adabbb1877392de6 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 10 Sep 2025 13:26:14 +0000 https://status.jit.io/#4a26cbe68f45ab6db783cbf2b4943bdbb3084c3b7211e952adabbb1877392de6 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 04 Sep 2025 20:30:58 +0000 https://status.jit.io/#5ce285f6c49ec36904f4a828760bb33a9ff485fa1062cd61b7ed8b6fb0db5187 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 04 Sep 2025 18:55:55 +0000 https://status.jit.io/#5ce285f6c49ec36904f4a828760bb33a9ff485fa1062cd61b7ed8b6fb0db5187 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 27 Aug 2025 21:31:05 +0000 https://status.jit.io/#acb28f2adf9f69557ed77854567ea7c545be44e7b65f6908b12fa1e32f1f1d2f GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 27 Aug 2025 20:51:23 +0000 https://status.jit.io/#acb28f2adf9f69557ed77854567ea7c545be44e7b65f6908b12fa1e32f1f1d2f GitHub Pull Request Scanning Services went down https://status.jit.io/incident/712922 Tue, 26 Aug 2025 17:03:02 -0000 https://status.jit.io/incident/712922#6e73f8e191edb222f1c30132227a2f461344c22d9b4c98fbfa1b9aaaafd0e963 Maintenance completed https://status.jit.io/incident/712922 Tue, 26 Aug 2025 17:01:38 -0000 https://status.jit.io/incident/712922#c7361fe2ec2bc1576008ed9e890b51dbe3c0910679f02b8c97e1eab162217dbb Loggin in to Jit ui is currently experiencing issues. This is under investigation and more updates will be provided shortly https://status.jit.io/ Thu, 21 Aug 2025 18:16:00 +0000 https://status.jit.io/#da91d5163a717e3fc428f09d994630b59a65846b75a48788c6e1a1572ac986d5 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 21 Aug 2025 15:56:19 +0000 https://status.jit.io/#da91d5163a717e3fc428f09d994630b59a65846b75a48788c6e1a1572ac986d5 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 21 Aug 2025 07:01:18 +0000 https://status.jit.io/#56b19e8f052769fc45278ef3a0093fcdf3e756e710dffe01a66eb53b37bff962 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 21 Aug 2025 06:26:24 +0000 https://status.jit.io/#56b19e8f052769fc45278ef3a0093fcdf3e756e710dffe01a66eb53b37bff962 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 19 Aug 2025 14:51:02 +0000 https://status.jit.io/#7041cf005f4887a1afdef3061aa01b7c132c81d79a1b3fc36d0cb9f2f0dd58b2 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 19 Aug 2025 13:50:54 +0000 https://status.jit.io/#7041cf005f4887a1afdef3061aa01b7c132c81d79a1b3fc36d0cb9f2f0dd58b2 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 14 Aug 2025 06:26:04 +0000 https://status.jit.io/#1b87fff7c0d975b7a329418e570aeb6b2e756551b1c7c16d6b09e53c0bfe5d31 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 14 Aug 2025 05:06:06 +0000 https://status.jit.io/#1b87fff7c0d975b7a329418e570aeb6b2e756551b1c7c16d6b09e53c0bfe5d31 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 12 Aug 2025 18:01:11 +0000 https://status.jit.io/#1a22066b4fafff07ccfcb5a7dd099818d9d89fe206ebf3f6be091fd1ee6f8128 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 12 Aug 2025 14:16:07 +0000 https://status.jit.io/#1a22066b4fafff07ccfcb5a7dd099818d9d89fe206ebf3f6be091fd1ee6f8128 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 05 Aug 2025 16:16:07 +0000 https://status.jit.io/#01aaacabebb018d643da4476e8bd8021d4dc8598cc2bbfaea2a06180550386c8 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 05 Aug 2025 15:45:58 +0000 https://status.jit.io/#01aaacabebb018d643da4476e8bd8021d4dc8598cc2bbfaea2a06180550386c8 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 29 Jul 2025 12:05:53 +0000 https://status.jit.io/#edcbe8daa36fccb746d4eeec9c9acc97a07bedddc22f900ee0d921a05ede932f GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 29 Jul 2025 10:46:06 +0000 https://status.jit.io/#edcbe8daa36fccb746d4eeec9c9acc97a07bedddc22f900ee0d921a05ede932f GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 29 Jul 2025 02:11:11 +0000 https://status.jit.io/#83c5cab1b3a960fde3a6417ed8aca6235f0c957bf3a590aa178843e43f66b7f9 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 28 Jul 2025 17:30:57 +0000 https://status.jit.io/#83c5cab1b3a960fde3a6417ed8aca6235f0c957bf3a590aa178843e43f66b7f9 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 23 Jul 2025 16:31:07 +0000 https://status.jit.io/#e8c235511c6e01bb1ad0c758638d2b4cdaad52435f5c0b3e3902c5594c68b2b1 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 23 Jul 2025 15:36:06 +0000 https://status.jit.io/#e8c235511c6e01bb1ad0c758638d2b4cdaad52435f5c0b3e3902c5594c68b2b1 GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 21 Jul 2025 09:51:05 +0000 https://status.jit.io/#51eaaccc5ac6c259c0b642d2471c8e3017af07e6986577f9f6f84131afc0a266 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 21 Jul 2025 07:16:18 +0000 https://status.jit.io/#51eaaccc5ac6c259c0b642d2471c8e3017af07e6986577f9f6f84131afc0a266 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/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.