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/ Mon, 23 Feb 2026 17:05:59 +0000 https://status.jit.io/#f0b338ee117c585465ba80491f2c3ace06d04fe491d8605d0fc8dc1311140307 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 23 Feb 2026 16:20:57 +0000 https://status.jit.io/#f0b338ee117c585465ba80491f2c3ace06d04fe491d8605d0fc8dc1311140307 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 17 Feb 2026 19:11:01 +0000 https://status.jit.io/#72350912551ca5db3deda38f048cee9c0aae2fe0d01ca1faff05acd43bbb5348 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 17 Feb 2026 17:51:01 +0000 https://status.jit.io/#72350912551ca5db3deda38f048cee9c0aae2fe0d01ca1faff05acd43bbb5348 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 11 Feb 2026 17:16:22 +0000 https://status.jit.io/#4ce7c1d40e81e3484ecaa1b6453ce8932f2f2ace9288fbb6c306ac4bbc1cf766 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 11 Feb 2026 15:30:56 +0000 https://status.jit.io/#4ce7c1d40e81e3484ecaa1b6453ce8932f2f2ace9288fbb6c306ac4bbc1cf766 GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 09 Feb 2026 20:10:57 +0000 https://status.jit.io/#4519d3a1ef068885649d3d49bd68c21650ed83f104ed40ca480305421633dcd0 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 09 Feb 2026 19:05:58 +0000 https://status.jit.io/#4519d3a1ef068885649d3d49bd68c21650ed83f104ed40ca480305421633dcd0 GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 09 Feb 2026 17:41:03 +0000 https://status.jit.io/#0f059381b2f758278da6b1d898e031ccdec6c676ef765885e5d122f6af4f799c GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 09 Feb 2026 16:25:59 +0000 https://status.jit.io/#0f059381b2f758278da6b1d898e031ccdec6c676ef765885e5d122f6af4f799c GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 09 Feb 2026 15:51:03 +0000 https://status.jit.io/#edc715e7b2aec1b0075a818236217877cd8878d37e2689b03769341a4ddfd6f4 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 09 Feb 2026 14:21:01 +0000 https://status.jit.io/#edc715e7b2aec1b0075a818236217877cd8878d37e2689b03769341a4ddfd6f4 GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 09 Feb 2026 11:30:53 +0000 https://status.jit.io/#ca1595f212bfbc221638f3ddfee4b836cf9af26f3c617482e1f02b4b9d1bff9e GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 09 Feb 2026 08:15:53 +0000 https://status.jit.io/#ca1595f212bfbc221638f3ddfee4b836cf9af26f3c617482e1f02b4b9d1bff9e GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 03 Feb 2026 19:30:55 +0000 https://status.jit.io/#33ffae9c48225bc17cb2de184d52975d9ba67e2cb4f94e1e090909910510df74 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 03 Feb 2026 16:11:03 +0000 https://status.jit.io/#33ffae9c48225bc17cb2de184d52975d9ba67e2cb4f94e1e090909910510df74 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 03 Feb 2026 01:00:56 +0000 https://status.jit.io/#6d8c39f8feeaae16259146d99acc235e79bd5b226cb33711541b4e00fe6c8bac GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 02 Feb 2026 19:06:10 +0000 https://status.jit.io/#6d8c39f8feeaae16259146d99acc235e79bd5b226cb33711541b4e00fe6c8bac GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 02 Feb 2026 17:46:25 +0000 https://status.jit.io/#c73b96a6e218e6b5c375162dc2a3ffe9209487d3f3bcc797999996074a8ac6d9 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 02 Feb 2026 17:36:36 +0000 https://status.jit.io/#c73b96a6e218e6b5c375162dc2a3ffe9209487d3f3bcc797999996074a8ac6d9 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 28 Jan 2026 15:55:55 +0000 https://status.jit.io/#e93c9ffd011205bb412ee176f1ba95ebc7a7f2a23c1e19ef0eb5ba3d7a05b1c4 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 28 Jan 2026 15:16:31 +0000 https://status.jit.io/#e93c9ffd011205bb412ee176f1ba95ebc7a7f2a23c1e19ef0eb5ba3d7a05b1c4 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 20 Jan 2026 20:16:01 +0000 https://status.jit.io/#c129d49857e1d6e93430eaa4c65e23b72811a9fb5445adfbf4ccccd4be3750e2 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 20 Jan 2026 19:50:54 +0000 https://status.jit.io/#c129d49857e1d6e93430eaa4c65e23b72811a9fb5445adfbf4ccccd4be3750e2 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 20 Jan 2026 16:26:02 +0000 https://status.jit.io/#3baad353d2d62f6a1220a35a730b3272a225f07f8bb33c9454deeb5c19692cb6 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 20 Jan 2026 16:06:26 +0000 https://status.jit.io/#3baad353d2d62f6a1220a35a730b3272a225f07f8bb33c9454deeb5c19692cb6 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 15 Jan 2026 17:55:56 +0000 https://status.jit.io/#28abace5d0e3d475081eaad2a0067a0b227dc4af80a275a6ff56c215eafa5ef8 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 15 Jan 2026 17:01:22 +0000 https://status.jit.io/#28abace5d0e3d475081eaad2a0067a0b227dc4af80a275a6ff56c215eafa5ef8 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 15 Jan 2026 15:30:58 +0000 https://status.jit.io/#1b7acc31179d0bafcf72b15c420b595899e50c35194550fa5ab1d401c27adb26 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 15 Jan 2026 14:25:55 +0000 https://status.jit.io/#1b7acc31179d0bafcf72b15c420b595899e50c35194550fa5ab1d401c27adb26 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 14 Jan 2026 21:41:27 +0000 https://status.jit.io/#8819e90ca2444b8d9e95e6146c22b027cb333bb2f20685b09c1ee2d03d7fbed5 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 14 Jan 2026 20:25:55 +0000 https://status.jit.io/#8819e90ca2444b8d9e95e6146c22b027cb333bb2f20685b09c1ee2d03d7fbed5 GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 12 Jan 2026 10:21:25 +0000 https://status.jit.io/#07f0eb5bebd6316c83c35e92b2ae50ed20782fea25d5b4cc26b0371e7c08c5bb GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 12 Jan 2026 10:11:25 +0000 https://status.jit.io/#07f0eb5bebd6316c83c35e92b2ae50ed20782fea25d5b4cc26b0371e7c08c5bb GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 06 Jan 2026 17:11:25 +0000 https://status.jit.io/#83d8586ebdce1da15552208a3202c3aeb9a06df4078f9cf882b1f146ae4a17fc GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 06 Jan 2026 16:46:19 +0000 https://status.jit.io/#83d8586ebdce1da15552208a3202c3aeb9a06df4078f9cf882b1f146ae4a17fc GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 18 Dec 2025 17:46:03 +0000 https://status.jit.io/#003a46baa27923794ffd1575530725a4894ea119b9396eebfb5182af5397e7dd GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 18 Dec 2025 16:45:55 +0000 https://status.jit.io/#003a46baa27923794ffd1575530725a4894ea119b9396eebfb5182af5397e7dd GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 11 Dec 2025 17:56:18 +0000 https://status.jit.io/#cc81d341737d5c5f5ef563f31a8ae99031b6dcdeb7784f92a16675411e68660e GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 11 Dec 2025 16:06:08 +0000 https://status.jit.io/#cc81d341737d5c5f5ef563f31a8ae99031b6dcdeb7784f92a16675411e68660e GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 10 Dec 2025 14:56:18 +0000 https://status.jit.io/#d9a6102091e00be7200436b4fabefd3e8eec1962348528401749e59508bf62c3 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 10 Dec 2025 13:50:48 +0000 https://status.jit.io/#d9a6102091e00be7200436b4fabefd3e8eec1962348528401749e59508bf62c3 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 10 Dec 2025 13:50:31 +0000 https://status.jit.io/#32ba3f444595601d949724d3a0c00e87531d98c61f2c7b660bf15d7306f6ef3f GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 10 Dec 2025 13:47:48 +0000 https://status.jit.io/#32ba3f444595601d949724d3a0c00e87531d98c61f2c7b660bf15d7306f6ef3f GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 10 Dec 2025 11:06:17 +0000 https://status.jit.io/#85e298dd65f78c202a5dad3e2dce6ebfeb623eeba7b4b9e417ee68ff5fb67303 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 10 Dec 2025 09:16:30 +0000 https://status.jit.io/#85e298dd65f78c202a5dad3e2dce6ebfeb623eeba7b4b9e417ee68ff5fb67303 GitHub Pull Request Scanning Services went down https://status.jit.io/incident/774737 Wed, 26 Nov 2025 14:38:00 -0000 https://status.jit.io/incident/774737#35c2eaf88bc3f62e0181fbaaad596af35184f5202931c1cba2f1d40a2a372806 We’re currently experiencing a service disruption. Our team has identified the root cause and is actively working to resolve the issue. During this time: Full scans and PR checks are unavailable Users may encounter errors We recommend temporarily disabling the Jit Security Check We’ll provide updates as we make progress. Thank you for your patience. https://status.jit.io/incident/774737 Wed, 26 Nov 2025 14:38:00 -0000 https://status.jit.io/incident/774737#35c2eaf88bc3f62e0181fbaaad596af35184f5202931c1cba2f1d40a2a372806 We’re currently experiencing a service disruption. Our team has identified the root cause and is actively working to resolve the issue. During this time: Full scans and PR checks are unavailable Users may encounter errors We recommend temporarily disabling the Jit Security Check We’ll provide updates as we make progress. Thank you for your patience. 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/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.