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, 19 Nov 2025 18:10:58 +0000 https://status.jit.io/#4519a9366ca1dce1f1fc94b76a845b1b579a656bd464e5ec6ec502db59626dfa GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 19 Nov 2025 17:50:57 +0000 https://status.jit.io/#4519a9366ca1dce1f1fc94b76a845b1b579a656bd464e5ec6ec502db59626dfa GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 18 Nov 2025 22:01:09 +0000 https://status.jit.io/#71d7c2ce83ad984cd4a3c10f3e74e24803a9b42552a9f727d823feee311bbb89 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 18 Nov 2025 20:41:07 +0000 https://status.jit.io/#71d7c2ce83ad984cd4a3c10f3e74e24803a9b42552a9f727d823feee311bbb89 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 13 Nov 2025 15:15:54 +0000 https://status.jit.io/#44e83ef2c2f3aac42470c9db9068a739cddccf13f7fbf2b95c3692e65856c064 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 13 Nov 2025 15:05:54 +0000 https://status.jit.io/#44e83ef2c2f3aac42470c9db9068a739cddccf13f7fbf2b95c3692e65856c064 GitHub Pull Request Scanning Services went down https://status.jit.io/ Sat, 01 Nov 2025 06:15:53 +0000 https://status.jit.io/#d6a26fe6458628661dedebf7c0c007dde4d9ab3443f08df9fddd10aaa99b2362 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Sat, 01 Nov 2025 04:45:52 +0000 https://status.jit.io/#d6a26fe6458628661dedebf7c0c007dde4d9ab3443f08df9fddd10aaa99b2362 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 29 Oct 2025 21:06:34 +0000 https://status.jit.io/#bbead1c29b75359fb8d214bbef52d43cee00fc25d19e1b4b565cd6655cb20422 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 29 Oct 2025 16:21:09 +0000 https://status.jit.io/#bbead1c29b75359fb8d214bbef52d43cee00fc25d19e1b4b565cd6655cb20422 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 23 Oct 2025 20:31:10 +0000 https://status.jit.io/#b901c2e0e2a1da379442e27d53ee9a8c0b72c1fb97e39369fe95afeea743d100 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 23 Oct 2025 16:41:09 +0000 https://status.jit.io/#b901c2e0e2a1da379442e27d53ee9a8c0b72c1fb97e39369fe95afeea743d100 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 22 Oct 2025 15:56:07 +0000 https://status.jit.io/#1b8097195b97a5cc85568697780d674bff62a10fcac13e7036610fae0bd8b97e GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 22 Oct 2025 14:31:08 +0000 https://status.jit.io/#1b8097195b97a5cc85568697780d674bff62a10fcac13e7036610fae0bd8b97e GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 21 Oct 2025 12:31:07 +0000 https://status.jit.io/#b89cb116d5610b3fb930f900091a4d0248bfa978714b6a6f63d05cb6e763c92a GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 21 Oct 2025 09:16:13 +0000 https://status.jit.io/#b89cb116d5610b3fb930f900091a4d0248bfa978714b6a6f63d05cb6e763c92a GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 20 Oct 2025 18:47:54 +0000 https://status.jit.io/#0b73ed10afeeed56921816908775b410417a3d8877eefe4e1108ff1700856734 GitHub Pull Request Scanning Services recovered https://status.jit.io/incident/747698 Mon, 20 Oct 2025 18:45:00 -0000 https://status.jit.io/incident/747698#53e83f997385a2658c1e5d675b48b612bbeb42d6156198376d3867d66f8270af UPDATE: AWS & Other 3rd part providers outage resolved — Jit services fully restored Last night, some customers experienced product availability issues due to a third-party (AWS and others) outage. We’re happy to report that the issue has now been fully resolved by our third-party providers, and all Jit services are operating normally again. If you temporarily disabled branch protection or bypassed Jit security checks during the outage, please make sure to re-enable them to ensure your branches remain fully protected. If you notice that anything is not working as expected in your environment, please open a support ticket so our team can assist you. Additionally, if you added resources during the outage and do not see them reflected in your Jit account, please open a support ticket and our team will help restore them. Thank you for your patience and understanding during this incident. If you have any other questions or concerns, please reach out to your Jit contact. Best regards, The Jit Team https://status.jit.io/incident/747698 Mon, 20 Oct 2025 18:45:00 -0000 https://status.jit.io/incident/747698#53e83f997385a2658c1e5d675b48b612bbeb42d6156198376d3867d66f8270af UPDATE: AWS & Other 3rd part providers outage resolved — Jit services fully restored Last night, some customers experienced product availability issues due to a third-party (AWS and others) outage. We’re happy to report that the issue has now been fully resolved by our third-party providers, and all Jit services are operating normally again. If you temporarily disabled branch protection or bypassed Jit security checks during the outage, please make sure to re-enable them to ensure your branches remain fully protected. If you notice that anything is not working as expected in your environment, please open a support ticket so our team can assist you. Additionally, if you added resources during the outage and do not see them reflected in your Jit account, please open a support ticket and our team will help restore them. Thank you for your patience and understanding during this incident. If you have any other questions or concerns, please reach out to your Jit contact. Best regards, The Jit Team https://status.jit.io/incident/747698 Mon, 20 Oct 2025 18:45:00 -0000 https://status.jit.io/incident/747698#53e83f997385a2658c1e5d675b48b612bbeb42d6156198376d3867d66f8270af UPDATE: AWS & Other 3rd part providers outage resolved — Jit services fully restored Last night, some customers experienced product availability issues due to a third-party (AWS and others) outage. We’re happy to report that the issue has now been fully resolved by our third-party providers, and all Jit services are operating normally again. If you temporarily disabled branch protection or bypassed Jit security checks during the outage, please make sure to re-enable them to ensure your branches remain fully protected. If you notice that anything is not working as expected in your environment, please open a support ticket so our team can assist you. Additionally, if you added resources during the outage and do not see them reflected in your Jit account, please open a support ticket and our team will help restore them. Thank you for your patience and understanding during this incident. If you have any other questions or concerns, please reach out to your Jit contact. Best regards, The Jit Team https://status.jit.io/ Mon, 20 Oct 2025 18:42:32 +0000 https://status.jit.io/#0b73ed10afeeed56921816908775b410417a3d8877eefe4e1108ff1700856734 GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 20 Oct 2025 09:21:53 +0000 https://status.jit.io/#86dc4bebbdbe5058c6a3ad1a9d35daf5613d84183024b9ca1d5b8c8967d94aca GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 20 Oct 2025 09:21:15 +0000 https://status.jit.io/#8337a8cc49478ebf0a4b944340c02e174fc4cb0a6108b939ff696a171727e13c Jit API recovered https://status.jit.io/ Mon, 20 Oct 2025 06:49:02 +0000 https://status.jit.io/#86dc4bebbdbe5058c6a3ad1a9d35daf5613d84183024b9ca1d5b8c8967d94aca GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 20 Oct 2025 06:49:00 +0000 https://status.jit.io/#8337a8cc49478ebf0a4b944340c02e174fc4cb0a6108b939ff696a171727e13c Jit API went down https://status.jit.io/ Thu, 09 Oct 2025 16:26:15 +0000 https://status.jit.io/#e0b646bc0e1b90c7867eb60501b2dc559e4dd1f03178865797c63c9e79c81399 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 09 Oct 2025 14:51:17 +0000 https://status.jit.io/#e0b646bc0e1b90c7867eb60501b2dc559e4dd1f03178865797c63c9e79c81399 GitHub Pull Request Scanning Services went down 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/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.