Incidents | jupiter Incidents reported on status page for jupiter https://status.jup.ag/ https://d1lppblt9t2x15.cloudfront.net/logos/45a1a1d8f060db3f1412313381b31c66.png Incidents | jupiter https://status.jup.ag/ en Tokens API V2 (Deprecated) recovered https://status.jup.ag/ Tue, 21 Oct 2025 03:55:26 +0000 https://status.jup.ag/#0aef089abf0d901a641ef71c06cbe572b39d1fb882bcf29b5010ce34f7cc666a Tokens API V2 (Deprecated) recovered Ultra API recovered https://status.jup.ag/ Tue, 21 Oct 2025 03:54:59 +0000 https://status.jup.ag/#0a0bbd812ff196acaf4740a317a32255e038a9dd60f2c96ea7d2762903b81465 Ultra API recovered Recurring API recovered https://status.jup.ag/ Tue, 21 Oct 2025 03:54:56 +0000 https://status.jup.ag/#b8ab751afd15de807853b1755817b64187347dba593a46f2ecc43f91a803d130 Recurring API recovered Swap API recovered https://status.jup.ag/ Tue, 21 Oct 2025 03:54:38 +0000 https://status.jup.ag/#bbae56dbf5af55d188b03419445ffa7e6dfb84cae85bce872cb4e8dfd6fd54bb Swap API recovered Ultra API went down https://status.jup.ag/ Tue, 21 Oct 2025 03:53:54 +0000 https://status.jup.ag/#0a0bbd812ff196acaf4740a317a32255e038a9dd60f2c96ea7d2762903b81465 Ultra API went down Recurring API went down https://status.jup.ag/ Tue, 21 Oct 2025 03:53:54 +0000 https://status.jup.ag/#b8ab751afd15de807853b1755817b64187347dba593a46f2ecc43f91a803d130 Recurring API went down Tokens API V2 (Deprecated) went down https://status.jup.ag/ Tue, 21 Oct 2025 03:53:54 +0000 https://status.jup.ag/#0aef089abf0d901a641ef71c06cbe572b39d1fb882bcf29b5010ce34f7cc666a Tokens API V2 (Deprecated) went down Swap API went down https://status.jup.ag/ Tue, 21 Oct 2025 03:53:35 +0000 https://status.jup.ag/#bbae56dbf5af55d188b03419445ffa7e6dfb84cae85bce872cb4e8dfd6fd54bb Swap API went down Recurring API recovered https://status.jup.ag/ Mon, 20 Oct 2025 22:30:23 +0000 https://status.jup.ag/#22b1a9a4a7d3aebd51170267a1176312e7829b3c00ae802e53139e4eec95b78a Recurring API recovered Recurring API went down https://status.jup.ag/ Mon, 20 Oct 2025 22:26:25 +0000 https://status.jup.ag/#22b1a9a4a7d3aebd51170267a1176312e7829b3c00ae802e53139e4eec95b78a Recurring API went down Swap Program Events Parsing 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. Swap Program Events Parsing 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. Swap Program Events Parsing 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. Swap Program Events Parsing 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. Swap Program Events Parsing 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. Swap Program Events Parsing 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. Swap Program Events Parsing 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. Swap Program Events Parsing 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. Token API V1 - Slow Response (Timeout) 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. Token API V1 - Slow Response (Timeout) 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. Token API V1 - Slow Response (Timeout) 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. Token API V1 - Slow Response (Timeout) 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. Token API V1 - Slow Response (Timeout) 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. Token API V1 - Slow Response (Timeout) 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. Token API V1 - Slow Response (Timeout) 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. Token API V1 - Slow Response (Timeout) 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. Token API V1 - Slow Response (Timeout) 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. Token API V1 - Slow Response (Timeout) 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. 502 Token API down time or slow to respond 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. 502 Token API down time or slow to respond 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. 502 Token API down time or slow to respond 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. 502 Token API down time or slow to respond 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. Trigger Order temporary downtime due to CloudFlare 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 Trigger Order temporary downtime due to CloudFlare 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 Trigger Order temporary downtime due to CloudFlare 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 Trigger Order temporary downtime due to CloudFlare 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