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/ Thu, 28 May 2026 01:30:54 +0000 https://status.jit.io/#c95ab2080f0238058a67100250132609485df27b92ad89c9935f8c879f8b5d7b GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 28 May 2026 01:15:58 +0000 https://status.jit.io/#c95ab2080f0238058a67100250132609485df27b92ad89c9935f8c879f8b5d7b GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 27 May 2026 13:20:57 +0000 https://status.jit.io/#ed0afecaeba1c8ae43aa35b327dd58271f3a55486c994e7a45e045ecfeb17f9c GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 27 May 2026 12:11:12 +0000 https://status.jit.io/#ed0afecaeba1c8ae43aa35b327dd58271f3a55486c994e7a45e045ecfeb17f9c GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 26 May 2026 13:06:08 +0000 https://status.jit.io/#d38a5f0b6d75f6cdca63784ef3f37d5e4807fa28e0a92d19d4e87da69de70b1b GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 26 May 2026 11:00:55 +0000 https://status.jit.io/#d38a5f0b6d75f6cdca63784ef3f37d5e4807fa28e0a92d19d4e87da69de70b1b GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 20 May 2026 17:56:22 +0000 https://status.jit.io/#9dfb64cbcbdaefd37c8862b953834c69ee071a75cf59a1bd8f8179e04142931e GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 20 May 2026 17:00:58 +0000 https://status.jit.io/#9dfb64cbcbdaefd37c8862b953834c69ee071a75cf59a1bd8f8179e04142931e GitHub Pull Request Scanning Services went down https://status.jit.io/ Fri, 15 May 2026 08:30:59 +0000 https://status.jit.io/#8dd758f77b3bdeb42a16ebc67c239658569709b997e13ddc6d4bdf54fe1ab9c5 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Fri, 15 May 2026 08:16:19 +0000 https://status.jit.io/#8dd758f77b3bdeb42a16ebc67c239658569709b997e13ddc6d4bdf54fe1ab9c5 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 12 May 2026 16:30:54 +0000 https://status.jit.io/#142b1e5c03c808f58d957f24c9f542a4177b78943b9e66114b1dbdc816ef4bbf GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 12 May 2026 15:46:06 +0000 https://status.jit.io/#142b1e5c03c808f58d957f24c9f542a4177b78943b9e66114b1dbdc816ef4bbf GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 11 May 2026 14:36:08 +0000 https://status.jit.io/#f0e3e9788144a0bfe4e3af555ae775008c688e1124451c2cbb0319db642dc001 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 11 May 2026 14:26:22 +0000 https://status.jit.io/#f0e3e9788144a0bfe4e3af555ae775008c688e1124451c2cbb0319db642dc001 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 06 May 2026 09:21:00 +0000 https://status.jit.io/#b5fca541ede2d0f9e7f741ffdf9441ed8a24f4acbb3a032c1350d4ffbf17c4a2 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 06 May 2026 07:21:06 +0000 https://status.jit.io/#b5fca541ede2d0f9e7f741ffdf9441ed8a24f4acbb3a032c1350d4ffbf17c4a2 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 05 May 2026 18:31:03 +0000 https://status.jit.io/#5baac133d008d9cbd9c871f36b3763897ab0a4d0e04015d4af58cd42c98e5406 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 05 May 2026 13:41:13 +0000 https://status.jit.io/#5baac133d008d9cbd9c871f36b3763897ab0a4d0e04015d4af58cd42c98e5406 GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 04 May 2026 16:41:10 +0000 https://status.jit.io/#4e4200f7aca8a8fafaf1ebb8ac72bf6926b135f4d6df2dda69cf341d998c3c36 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 04 May 2026 15:46:04 +0000 https://status.jit.io/#4e4200f7aca8a8fafaf1ebb8ac72bf6926b135f4d6df2dda69cf341d998c3c36 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 28 Apr 2026 17:11:00 +0000 https://status.jit.io/#c336907d1a103db16ce90d21bce55b8cddcaa1901918bb271449a3cdc5305380 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 28 Apr 2026 14:06:05 +0000 https://status.jit.io/#c336907d1a103db16ce90d21bce55b8cddcaa1901918bb271449a3cdc5305380 GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 27 Apr 2026 21:36:06 +0000 https://status.jit.io/#4e0e50b53d060268a8f0de0117cc7bad4260377f6d79bce4d15f4fc3f89360af GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 27 Apr 2026 16:30:57 +0000 https://status.jit.io/#4e0e50b53d060268a8f0de0117cc7bad4260377f6d79bce4d15f4fc3f89360af GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 23 Apr 2026 17:11:07 +0000 https://status.jit.io/#03eeea3ca232eb5f1c7ae18d225f684b013ac2ab9ef2af86844d5f8c3c8b1c60 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 23 Apr 2026 16:16:05 +0000 https://status.jit.io/#03eeea3ca232eb5f1c7ae18d225f684b013ac2ab9ef2af86844d5f8c3c8b1c60 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 23 Apr 2026 15:06:05 +0000 https://status.jit.io/#34f9c2b73b01de1ff046796a897ece482ad72ea64b538dd12b7aa0a7135518ed GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 23 Apr 2026 14:41:12 +0000 https://status.jit.io/#34f9c2b73b01de1ff046796a897ece482ad72ea64b538dd12b7aa0a7135518ed GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 30 Mar 2026 13:21:02 +0000 https://status.jit.io/#9467b433968a1f6223b082b0c1032f1489fc90d9597c1315aa2c208ccf736de5 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 30 Mar 2026 13:05:57 +0000 https://status.jit.io/#9467b433968a1f6223b082b0c1032f1489fc90d9597c1315aa2c208ccf736de5 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 24 Mar 2026 21:00:57 +0000 https://status.jit.io/#ff1a094f33c43ba1904d71f45356972da9218c15feb523a71214f77f8a954407 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 24 Mar 2026 20:20:55 +0000 https://status.jit.io/#ff1a094f33c43ba1904d71f45356972da9218c15feb523a71214f77f8a954407 GitHub Pull Request Scanning Services went down https://status.jit.io/ Fri, 20 Mar 2026 00:05:57 +0000 https://status.jit.io/#8b398f2aea0bcc2f04817b82870375ec2f5bde003105961c570149a4c1b86d5e GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 19 Mar 2026 16:25:57 +0000 https://status.jit.io/#8b398f2aea0bcc2f04817b82870375ec2f5bde003105961c570149a4c1b86d5e GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 19 Mar 2026 01:45:57 +0000 https://status.jit.io/#bd514c6e953afa68682ce3574e4890c95398ac36bc2d64e104e042837583bb45 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 18 Mar 2026 22:41:00 +0000 https://status.jit.io/#bd514c6e953afa68682ce3574e4890c95398ac36bc2d64e104e042837583bb45 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 18 Mar 2026 19:51:04 +0000 https://status.jit.io/#915da733c11f63469a6095da9bad471e69cbecbb9700aefecd26ac210d8c5cbb GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 18 Mar 2026 18:55:51 +0000 https://status.jit.io/#915da733c11f63469a6095da9bad471e69cbecbb9700aefecd26ac210d8c5cbb GitHub Pull Request Scanning Services went down https://status.jit.io/ Fri, 13 Mar 2026 16:16:03 +0000 https://status.jit.io/#19e9ec0c3684865ba908a71d90d4474e65366685723f18010d4520725bc96a03 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Fri, 13 Mar 2026 15:15:57 +0000 https://status.jit.io/#19e9ec0c3684865ba908a71d90d4474e65366685723f18010d4520725bc96a03 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 12 Mar 2026 06:06:00 +0000 https://status.jit.io/#1de60f1acce1d9e78cbb169a292087dbc364a7cab847c902a762f420b8318462 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 12 Mar 2026 04:50:57 +0000 https://status.jit.io/#1de60f1acce1d9e78cbb169a292087dbc364a7cab847c902a762f420b8318462 GitHub Pull Request Scanning Services went down https://status.jit.io/ Wed, 11 Mar 2026 15:05:59 +0000 https://status.jit.io/#67a27aaf781d31cb877c10530a62e3fc348beb6d09e68b6495f3f1b1f9950f10 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Wed, 11 Mar 2026 14:41:01 +0000 https://status.jit.io/#67a27aaf781d31cb877c10530a62e3fc348beb6d09e68b6495f3f1b1f9950f10 GitHub Pull Request Scanning Services went down https://status.jit.io/ Mon, 09 Mar 2026 17:06:03 +0000 https://status.jit.io/#397b0e04bf8b184f532f3a551283bafb4fbd7ac2e1443f7f8f97f04c2d80fd33 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Mon, 09 Mar 2026 15:50:55 +0000 https://status.jit.io/#397b0e04bf8b184f532f3a551283bafb4fbd7ac2e1443f7f8f97f04c2d80fd33 GitHub Pull Request Scanning Services went down https://status.jit.io/ Fri, 06 Mar 2026 23:31:26 +0000 https://status.jit.io/#21300572fd806cdeb9a6588f05a83115d65a438755e46b961a5143114fd62823 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Fri, 06 Mar 2026 17:01:25 +0000 https://status.jit.io/#21300572fd806cdeb9a6588f05a83115d65a438755e46b961a5143114fd62823 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 05 Mar 2026 23:56:31 +0000 https://status.jit.io/#b0eaf5ebcf94027f01fb103b8dc85357f68b3c442a7a3bd89fb39effad020373 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 05 Mar 2026 22:56:27 +0000 https://status.jit.io/#b0eaf5ebcf94027f01fb103b8dc85357f68b3c442a7a3bd89fb39effad020373 GitHub Pull Request Scanning Services went down https://status.jit.io/ Thu, 05 Mar 2026 19:21:01 +0000 https://status.jit.io/#71c7af59535219b614ae9980bf741c9ba8e4da4180c4cd50e671783edbc58fa4 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Thu, 05 Mar 2026 16:36:02 +0000 https://status.jit.io/#71c7af59535219b614ae9980bf741c9ba8e4da4180c4cd50e671783edbc58fa4 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 03 Mar 2026 20:06:04 +0000 https://status.jit.io/#afb81004af7005b22423b430269fc524b63ca3a5e0aa33369224de8798d56bb7 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 03 Mar 2026 20:01:00 +0000 https://status.jit.io/#afb81004af7005b22423b430269fc524b63ca3a5e0aa33369224de8798d56bb7 GitHub Pull Request Scanning Services went down https://status.jit.io/ Tue, 03 Mar 2026 19:56:00 +0000 https://status.jit.io/#6aa9b03d5b92a049a705fb1ab5947fa4c5cab3943d22bb89dc6b790508fe1667 GitHub Pull Request Scanning Services recovered https://status.jit.io/ Tue, 03 Mar 2026 19:01:00 +0000 https://status.jit.io/#6aa9b03d5b92a049a705fb1ab5947fa4c5cab3943d22bb89dc6b790508fe1667 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/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: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 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 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.