Incidents reported on status page for jupiter https://status.jup.ag/ https://d1lppblt9t2x15.cloudfront.net/logos/45a1a1d8f060db3f1412313381b31c66.png https://status.jup.ag/ en https://status.jup.ag/ Sun, 08 Feb 2026 14:23:08 +0000 https://status.jup.ag/#e7692aeb5a3f9fb52ff32cb3a4eb67bb3086b16ad600855b553cfc742ffb0d55 Trigger API recovered https://status.jup.ag/ Sun, 08 Feb 2026 14:23:07 +0000 https://status.jup.ag/#a42839fc785b282ec83248543e123170d67ea8a6a4c36be1d68e3b0d2cca8450 Trigger API recovered https://status.jup.ag/ Sun, 08 Feb 2026 14:22:03 +0000 https://status.jup.ag/#a42839fc785b282ec83248543e123170d67ea8a6a4c36be1d68e3b0d2cca8450 Trigger API went down https://status.jup.ag/ Sun, 08 Feb 2026 14:22:03 +0000 https://status.jup.ag/#e7692aeb5a3f9fb52ff32cb3a4eb67bb3086b16ad600855b553cfc742ffb0d55 Trigger API went down https://status.jup.ag/ Wed, 04 Feb 2026 10:11:32 +0000 https://status.jup.ag/#0206652c05f1e93f8bcfbedc2b5d8dc2a940a17daeb7360adfeae086cbfcc546 Trigger API recovered https://status.jup.ag/ Wed, 04 Feb 2026 10:09:58 +0000 https://status.jup.ag/#824800b78e41f687613ab93a54e3e617e043501546408e991d17f5eee3758f2c Trigger API recovered https://status.jup.ag/ Wed, 04 Feb 2026 10:09:02 +0000 https://status.jup.ag/#f59c14b935c046c1b1d91bfe7ad6b5785454f22877d2c0e003d7430de03dbeb2 Ultra API recovered https://status.jup.ag/ Wed, 04 Feb 2026 10:08:52 +0000 https://status.jup.ag/#8872f5f54faef2038073bfd66a96430c94550cc80e576614709fe1e95dde4e6d Ultra API recovered https://status.jup.ag/ Wed, 04 Feb 2026 09:52:34 +0000 https://status.jup.ag/#f59c14b935c046c1b1d91bfe7ad6b5785454f22877d2c0e003d7430de03dbeb2 Ultra API went down https://status.jup.ag/ Wed, 04 Feb 2026 09:52:17 +0000 https://status.jup.ag/#8872f5f54faef2038073bfd66a96430c94550cc80e576614709fe1e95dde4e6d Ultra API went down https://status.jup.ag/ Wed, 04 Feb 2026 09:52:01 +0000 https://status.jup.ag/#0206652c05f1e93f8bcfbedc2b5d8dc2a940a17daeb7360adfeae086cbfcc546 Trigger API went down https://status.jup.ag/ Wed, 04 Feb 2026 09:51:05 +0000 https://status.jup.ag/#824800b78e41f687613ab93a54e3e617e043501546408e991d17f5eee3758f2c Trigger API went down https://status.jup.ag/ Fri, 09 Jan 2026 12:03:56 +0000 https://status.jup.ag/#d877a0e0c69d00bd6ee70af33e6c6bb774bea110f14805019fd71451010cbd6e Trigger API recovered https://status.jup.ag/ Fri, 09 Jan 2026 12:03:46 +0000 https://status.jup.ag/#b3d242dcf9473633cce55188aa6fd01631ec6f7dd787e482ed1f4cdf7c8534a8 Trigger API recovered https://status.jup.ag/ Fri, 09 Jan 2026 11:45:46 +0000 https://status.jup.ag/#d877a0e0c69d00bd6ee70af33e6c6bb774bea110f14805019fd71451010cbd6e Trigger API went down https://status.jup.ag/ Fri, 09 Jan 2026 11:45:20 +0000 https://status.jup.ag/#b3d242dcf9473633cce55188aa6fd01631ec6f7dd787e482ed1f4cdf7c8534a8 Trigger API went down https://status.jup.ag/incident/725203 Tue, 16 Sep 2025 13:09:00 -0000 https://status.jup.ag/incident/725203#a167e093315baea47c451e22c87a2b00e4fc6945fcccabbdcacb1f156a8fb5eb This issue has been fixed, please check. Apologies. Please reach out to us if you have any questions. https://status.jup.ag/incident/725203 Tue, 16 Sep 2025 13:09:00 -0000 https://status.jup.ag/incident/725203#a167e093315baea47c451e22c87a2b00e4fc6945fcccabbdcacb1f156a8fb5eb This issue has been fixed, please check. Apologies. Please reach out to us if you have any questions. https://status.jup.ag/incident/725203 Tue, 16 Sep 2025 13:09:00 -0000 https://status.jup.ag/incident/725203#a167e093315baea47c451e22c87a2b00e4fc6945fcccabbdcacb1f156a8fb5eb This issue has been fixed, please check. Apologies. Please reach out to us if you have any questions. https://status.jup.ag/incident/725203 Tue, 16 Sep 2025 13:09:00 -0000 https://status.jup.ag/incident/725203#a167e093315baea47c451e22c87a2b00e4fc6945fcccabbdcacb1f156a8fb5eb This issue has been fixed, please check. Apologies. Please reach out to us if you have any questions. https://status.jup.ag/incident/725203 Tue, 16 Sep 2025 12:19:00 -0000 https://status.jup.ag/incident/725203#1ad931bef611d0818d6c0bf147e9a42d5ec3a14a409463f363425bfd69d8dc8e There has been a bad deployment that affects swap events parsing. It will affect the swap events you see in the transaction, showing wrong mints or affects your parsing mechanism for other usages. The transaction should execute as expected, only the swap event parsing has issues. You can check the source/destination token accounts in the instruction to verify what mints were swapped. We are working on a fix and will update. https://status.jup.ag/incident/725203 Tue, 16 Sep 2025 12:19:00 -0000 https://status.jup.ag/incident/725203#1ad931bef611d0818d6c0bf147e9a42d5ec3a14a409463f363425bfd69d8dc8e There has been a bad deployment that affects swap events parsing. It will affect the swap events you see in the transaction, showing wrong mints or affects your parsing mechanism for other usages. The transaction should execute as expected, only the swap event parsing has issues. You can check the source/destination token accounts in the instruction to verify what mints were swapped. We are working on a fix and will update. https://status.jup.ag/incident/725203 Tue, 16 Sep 2025 12:19:00 -0000 https://status.jup.ag/incident/725203#1ad931bef611d0818d6c0bf147e9a42d5ec3a14a409463f363425bfd69d8dc8e There has been a bad deployment that affects swap events parsing. It will affect the swap events you see in the transaction, showing wrong mints or affects your parsing mechanism for other usages. The transaction should execute as expected, only the swap event parsing has issues. You can check the source/destination token accounts in the instruction to verify what mints were swapped. We are working on a fix and will update. https://status.jup.ag/incident/725203 Tue, 16 Sep 2025 12:19:00 -0000 https://status.jup.ag/incident/725203#1ad931bef611d0818d6c0bf147e9a42d5ec3a14a409463f363425bfd69d8dc8e There has been a bad deployment that affects swap events parsing. It will affect the swap events you see in the transaction, showing wrong mints or affects your parsing mechanism for other usages. The transaction should execute as expected, only the swap event parsing has issues. You can check the source/destination token accounts in the instruction to verify what mints were swapped. We are working on a fix and will update. https://status.jup.ag/incident/620056 Tue, 15 Jul 2025 18:30:00 -0000 https://status.jup.ag/incident/620056#990493fb2b8dd252aa69a8c2109fa5b30ef5ed0c53b2280841c9619c9baa6529 Token API V1 issues have been temporarily resolved. Do note that, responses now are more cached to help with the issue. Please migrate to Token API V2 as soon as possible, we will be deprecating V1 soon. https://status.jup.ag/incident/620056 Tue, 15 Jul 2025 18:30:00 -0000 https://status.jup.ag/incident/620056#990493fb2b8dd252aa69a8c2109fa5b30ef5ed0c53b2280841c9619c9baa6529 Token API V1 issues have been temporarily resolved. Do note that, responses now are more cached to help with the issue. Please migrate to Token API V2 as soon as possible, we will be deprecating V1 soon. https://status.jup.ag/incident/620056 Tue, 15 Jul 2025 14:30:00 -0000 https://status.jup.ag/incident/620056#f3cb924328e2ecc4e76cbb810bf2000f9c424271472e1b334c46066d5b61fbbe The Token API V1 will face temporary downtime as we attempt a fix. If you need urgent token information, please migrate to Token API V2. https://status.jup.ag/incident/620056 Tue, 15 Jul 2025 14:30:00 -0000 https://status.jup.ag/incident/620056#f3cb924328e2ecc4e76cbb810bf2000f9c424271472e1b334c46066d5b61fbbe The Token API V1 will face temporary downtime as we attempt a fix. If you need urgent token information, please migrate to Token API V2. https://status.jup.ag/incident/620056 Tue, 15 Jul 2025 12:15:00 -0000 https://status.jup.ag/incident/620056#da3505c79923e6ae479624861b5c371b8e93ab315637d018769eb0eceb74a23c We're looking into the issue with Token API V1 that is causing the slow response which can lead to timeout. If you need token data urgently, you can migrate to Token API V2. https://status.jup.ag/incident/620056 Tue, 15 Jul 2025 12:15:00 -0000 https://status.jup.ag/incident/620056#da3505c79923e6ae479624861b5c371b8e93ab315637d018769eb0eceb74a23c We're looking into the issue with Token API V1 that is causing the slow response which can lead to timeout. If you need token data urgently, you can migrate to Token API V2. https://status.jup.ag/incident/617010 Wed, 09 Jul 2025 23:45:00 -0000 https://status.jup.ag/incident/617010#ecb59cc86ed4dfea947db5888df6e12b09d9154d09af788173378ec13dd29478 We have resolved the issue temporarily and response times should return to normal now. We'll continue to monitor and work on the root cause. https://status.jup.ag/incident/617010 Wed, 09 Jul 2025 23:45:00 -0000 https://status.jup.ag/incident/617010#ecb59cc86ed4dfea947db5888df6e12b09d9154d09af788173378ec13dd29478 We have resolved the issue temporarily and response times should return to normal now. We'll continue to monitor and work on the root cause. https://status.jup.ag/incident/617010 Wed, 09 Jul 2025 22:42:00 -0000 https://status.jup.ag/incident/617010#7f92fadd0c7b2fc42f835e00085d9bd92019961884e6a0cf5d43b8a4b1e69545 We're looking into the issue with Token API V1 that is causing the slow response which can lead to timeout. If you need token data urgently, you can migrate to Token API V2. https://status.jup.ag/incident/617010 Wed, 09 Jul 2025 22:42:00 -0000 https://status.jup.ag/incident/617010#7f92fadd0c7b2fc42f835e00085d9bd92019961884e6a0cf5d43b8a4b1e69545 We're looking into the issue with Token API V1 that is causing the slow response which can lead to timeout. If you need token data urgently, you can migrate to Token API V2. https://status.jup.ag/incident/602914 Sat, 14 Jun 2025 09:12:00 -0000 https://status.jup.ag/incident/602914#46e8260d2e1ff2a9108ed9e6e67a8d3ba3d5124d0d83ef21507b78fd9b8cfb04 Jun 14, 2025 at 0912 UTC - We have scaled up the infrastructure to temporarily handle the spike in connections while we investigate the root cause. The Token API should be back to normal. https://status.jup.ag/incident/602914 Sat, 14 Jun 2025 09:12:00 -0000 https://status.jup.ag/incident/602914#46e8260d2e1ff2a9108ed9e6e67a8d3ba3d5124d0d83ef21507b78fd9b8cfb04 Jun 14, 2025 at 0912 UTC - We have scaled up the infrastructure to temporarily handle the spike in connections while we investigate the root cause. The Token API should be back to normal. https://status.jup.ag/incident/602914 Sat, 14 Jun 2025 08:33:00 -0000 https://status.jup.ag/incident/602914#aa7259c223453cbd7e56b4f71c7881c0f22d0ef17c089ae456ae594658f0c1a5 Jun 14, 2025 at 0802 UTC - Acknowledged the incident. Observed that there is a spike in DB connections. Jun 14, 2025 at 0839 UTC - Created status report, as we are still looking for the root cause and solution. https://status.jup.ag/incident/602914 Sat, 14 Jun 2025 08:33:00 -0000 https://status.jup.ag/incident/602914#aa7259c223453cbd7e56b4f71c7881c0f22d0ef17c089ae456ae594658f0c1a5 Jun 14, 2025 at 0802 UTC - Acknowledged the incident. Observed that there is a spike in DB connections. Jun 14, 2025 at 0839 UTC - Created status report, as we are still looking for the root cause and solution. https://status.jup.ag/incident/601876 Thu, 12 Jun 2025 18:46:00 -0000 https://status.jup.ag/incident/601876#b94961f5c9b0b8498f21953c3889b4fb969caa7688cf1564bb3419dbf928ddc1 We acknowledged the issue at Jun 12, 2025 - 18:04 UTC We then figured the root cause and implemented a workaround at Jun 12, 2025 - 18:35 UTC https://status.jup.ag/incident/601876 Thu, 12 Jun 2025 18:46:00 -0000 https://status.jup.ag/incident/601876#b94961f5c9b0b8498f21953c3889b4fb969caa7688cf1564bb3419dbf928ddc1 We acknowledged the issue at Jun 12, 2025 - 18:04 UTC We then figured the root cause and implemented a workaround at Jun 12, 2025 - 18:35 UTC https://status.jup.ag/incident/601876 Thu, 12 Jun 2025 18:41:00 -0000 https://status.jup.ag/incident/601876#ea3d6086aee2c23042ba646e5a08140fdeffdc120d99142faa43196249993ac3 We acknowledged the issue at Jun 12, 2025 - 18:04 UTC We then figured the root cause and implemented a workaround at Jun 12, 2025 - 18:35 UTC If you need help please reach out to us in Discord's Developer Support channel at https://discord.gg/jup --- This is from CloudFlare --- Update - We are continuing to investigate this issue. Jun 12, 2025 - 18:31 UTC Update - We are seeing a number of services suffer intermittent failures. We are continuing to investigate this and we will update this list as we assess the impact on a per-service level. Jun 12, 2025 - 18:30 UTC Update - We are continuing to investigate this issue. Jun 12, 2025 - 18:20 UTC Investigating - Cloudflare engineering is investigating an issue causing Access authentication to fail. Cloudflare Zero Trust WARP connectivity is also impacted. Jun 12, 2025 - 18:19 UTC https://status.jup.ag/incident/601876 Thu, 12 Jun 2025 18:41:00 -0000 https://status.jup.ag/incident/601876#ea3d6086aee2c23042ba646e5a08140fdeffdc120d99142faa43196249993ac3 We acknowledged the issue at Jun 12, 2025 - 18:04 UTC We then figured the root cause and implemented a workaround at Jun 12, 2025 - 18:35 UTC If you need help please reach out to us in Discord's Developer Support channel at https://discord.gg/jup --- This is from CloudFlare --- Update - We are continuing to investigate this issue. Jun 12, 2025 - 18:31 UTC Update - We are seeing a number of services suffer intermittent failures. We are continuing to investigate this and we will update this list as we assess the impact on a per-service level. Jun 12, 2025 - 18:30 UTC Update - We are continuing to investigate this issue. Jun 12, 2025 - 18:20 UTC Investigating - Cloudflare engineering is investigating an issue causing Access authentication to fail. Cloudflare Zero Trust WARP connectivity is also impacted. Jun 12, 2025 - 18:19 UTC