Incidents reported on status page for Portkey https://status.portkey.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/543a439f8e85b6c7346558461a111630.png https://status.portkey.ai/ en https://status.portkey.ai/ Mon, 30 Mar 2026 05:21:00 +0000 https://status.portkey.ai/#1755c687c4d985e571963944edbc05dbf97bff408443beacbee8d9ffd4505560 API recovered https://status.portkey.ai/ Mon, 30 Mar 2026 05:18:25 +0000 https://status.portkey.ai/#1755c687c4d985e571963944edbc05dbf97bff408443beacbee8d9ffd4505560 API went down https://status.portkey.ai/ Tue, 10 Mar 2026 13:37:17 +0000 https://status.portkey.ai/#be1f1b85f97262e7741bf8bbf8b77aed195f8c4376f9e14f37af422118227a78 API recovered https://status.portkey.ai/ Tue, 10 Mar 2026 13:35:24 +0000 https://status.portkey.ai/#be1f1b85f97262e7741bf8bbf8b77aed195f8c4376f9e14f37af422118227a78 API went down https://status.portkey.ai/ Tue, 10 Mar 2026 13:31:17 +0000 https://status.portkey.ai/#0ba56128b94c5626523034e9f3f5a40cf2cb55a9799d7b02104ecd0dcdbf7222 API recovered https://status.portkey.ai/ Tue, 10 Mar 2026 13:28:23 +0000 https://status.portkey.ai/#0ba56128b94c5626523034e9f3f5a40cf2cb55a9799d7b02104ecd0dcdbf7222 API went down https://status.portkey.ai/ Tue, 10 Mar 2026 12:09:49 +0000 https://status.portkey.ai/#371c2de4408e83a329501421fb7da844da8e58f361f3ba99120ff82e56e57cfc API recovered https://status.portkey.ai/ Tue, 10 Mar 2026 12:08:28 +0000 https://status.portkey.ai/#371c2de4408e83a329501421fb7da844da8e58f361f3ba99120ff82e56e57cfc API went down https://status.portkey.ai/incident/841211 Thu, 05 Mar 2026 10:45:00 -0000 https://status.portkey.ai/incident/841211#326ae1e913614f1e7c59944e0c55ef7938145d4dba41b7e550fbcf9a0b72694a Current status: Fully resolved. Email/password auth and signups are working as expected. https://status.portkey.ai/incident/841211 Thu, 05 Mar 2026 09:51:00 -0000 https://status.portkey.ai/incident/841211#bc26bf0ace9f826083e21e1422588747e8a7c160be2d32b708d2f8db401b3db8 We had a brief authentication issue on the control plane today. What happened: Between 9:50 AM - 10:45 AM UTC users who had signed out couldn't sign back in using email + password. New signups were also affected during this window. SSO and other auth methods continued to work normally. https://status.portkey.ai/ Thu, 22 Jan 2026 15:48:20 +0000 https://status.portkey.ai/#057b26ad16e99fde8fec5131575469c6f52e07d8ffd8e55933c5948484c83ab6 API recovered https://status.portkey.ai/ Thu, 22 Jan 2026 15:47:06 +0000 https://status.portkey.ai/#057b26ad16e99fde8fec5131575469c6f52e07d8ffd8e55933c5948484c83ab6 API went down https://status.portkey.ai/incident/809494 Tue, 20 Jan 2026 22:08:00 -0000 https://status.portkey.ai/incident/809494#146fed69a12f124b416c0c9f510bd496bcccad454d3b6bd25247b58a88b752ec Dashboard and /prompt/render APIs are up now. Root cause: An unusually high volume of SCIM provisioning updates created unexpected load on our control plane database. Resolution: The issue has been resolved and all services are operating normally. We are implementing additional rate limiting and scaling measures to prevent similar occurrences. https://status.portkey.ai/incident/809494 Tue, 20 Jan 2026 20:53:00 -0000 https://status.portkey.ai/incident/809494#40a9c684d8a2c837ade761aeb1bbac0e8daa5724f103311ddba426f7d835d406 We experienced degraded performance affecting the Portkey Dashboard and Prompt Render API between 2:23 AM - 3:38 AM IST on January 22, 2026. Impact: Dashboard timeouts and slow loading for some users. The Prompt Render API experienced intermittent failures. What is NOT affected: The AI Gateway remained fully operational throughout. All inference requests and model calls continued to work normally with no failures. https://status.portkey.ai/incident/809489 Fri, 16 Jan 2026 08:30:00 -0000 https://status.portkey.ai/incident/809489#bbce9a08213e67834287cb6ece0331b5a7341946984dce007cf367776a11d6fb Logs are working as expected now. https://status.portkey.ai/incident/809489 Thu, 15 Jan 2026 08:54:00 -0000 https://status.portkey.ai/incident/809489#c19743c54f20da325f82f49a72f4726234cd521241054649eb500e1fd47127c0 A code update introduced a new metric that occasionally resulted in failed Clickhouse inserts, causing logs to not appear in the UI. https://status.portkey.ai/incident/770019 Tue, 18 Nov 2025 14:00:00 -0000 https://status.portkey.ai/incident/770019#05001d117f4357ef421ba4eae42622a447a37694a9f06378e8c5a2795b459a15 Service is back up now. https://status.portkey.ai/incident/770019 Tue, 18 Nov 2025 11:29:00 -0000 https://status.portkey.ai/incident/770019#16ef71d0c791a8551428a159c7122e01131951a30139035478df02f1be5a4358 Portkey is impacted by the global Cloudflare outage. SaaS Gateway and the control plane are facing intermittent failures. We are actively investigating the issue and working to get the system back up. https://status.portkey.ai/incident/624446 Tue, 22 Jul 2025 23:32:00 -0000 https://status.portkey.ai/incident/624446#f8b70885cd1f5b36475a56e2bd8ad5c6cdbd8f53e1a352ef5c54d2cd039429d1 While working to fix some caching issues yesterday, we inadvertently introduced a bug that caused erroneous cache collisions. This issue may have affected your requests that had cache enabled. If you were using different metadata or cache namespaces, your requests were properly isolated and unaffected from this bug. Please Note: - The collisions did not happen between cache partitions - The collisions did not happen across accounts The issue has been fully reverted as of Jul 23, 2025 3:23 UTC. Our team is actively monitoring the system to ensure stability. We are sorry for this! https://status.portkey.ai/incident/601885 Thu, 12 Jun 2025 20:34:00 -0000 https://status.portkey.ai/incident/601885#65ed2e26202dae5d8812153f7d73ca5160deeaaf3f710f4df0632cee26d0a459 Latencies have reduced significantly and services seem up. We're continuing to monitor services and requests. Please reach out on Discord or support@portkey.ai if you're facing issues. https://status.portkey.ai/incident/601885 Thu, 12 Jun 2025 20:24:00 -0000 https://status.portkey.ai/incident/601885#b451ed7a072f99701cdb2642daf62921a9cabc3f37dbdf7babcaac7215a69b2d Services are starting to come back now. Latencies are going down as well. We're constantly monitoring the systems. https://status.portkey.ai/incident/601885 Thu, 12 Jun 2025 18:58:00 -0000 https://status.portkey.ai/incident/601885#6c5da8663b137d2eb8f668ced6a19c5e8455bf35fd5bc710f1d9eafd18bc8c0e You should be able to login to the Portkey UI again. Gateway requests are still experiencing higher latencies due to the Cloudflare Workers KV outage. https://www.cloudflarestatus.com/incidents/25r9t0vz99rp https://status.portkey.ai/incident/601885 Thu, 12 Jun 2025 18:20:00 -0000 https://status.portkey.ai/incident/601885#773aed96b13114c48f7ee8a95b35cf500a5b51912865235c461d6aea2a7d5c1e We wish it was April 1st, but the internet is just not feeling it today. We're experiencing an outage on the UI due to an ongoing outage with GCE and Firebase. The AI gateway requests are also experiencing increased latencies due to cloudflare outages. We're continuously monitoring our services and working to get them back soon. https://status.portkey.ai/incident/527845 Thu, 13 Mar 2025 20:10:51 -0000 https://status.portkey.ai/incident/527845#e7083b5de9c4b5b833c5754771e3da85a7cb44b060c42a4b860345e1682f57ac API recovered. https://status.portkey.ai/incident/527845 Thu, 13 Mar 2025 20:10:29 -0000 https://status.portkey.ai/incident/527845#0bfea73f6c3e7759d1800c943e1be626f16e83e2c59fc856b25700a7a3c4d95c API went down. https://status.portkey.ai/incident/509609 Sat, 08 Feb 2025 20:00:46 -0000 https://status.portkey.ai/incident/509609#b9d5417ca30506e2484c8e4326937d8a6f74fc292ac4ade3a7b2f38e4323d027 API recovered. https://status.portkey.ai/incident/509609 Sat, 08 Feb 2025 19:59:41 -0000 https://status.portkey.ai/incident/509609#71e070218fae54e90a933196b38750b5d028e0024bbdc2b90b31dff49dfdc95f API went down. https://status.portkey.ai/incident/451121 Sat, 26 Oct 2024 22:49:00 -0000 https://status.portkey.ai/incident/451121#82aaa08fcceeb63970f5a56cd66717853cdf9bd83fa700b77714337365b01b5a API recovered. https://status.portkey.ai/incident/451121 Sat, 26 Oct 2024 22:48:34 -0000 https://status.portkey.ai/incident/451121#83d03dc425b838200b50831556b579be03f349e82207aff891b9946a3d4fbd79 API went down. https://status.portkey.ai/incident/443725 Sun, 13 Oct 2024 06:37:07 -0000 https://status.portkey.ai/incident/443725#f56cbd2203e9ac31c4c6b8b4f0dd48c126289eb45d06a3496e121a651d049c9d API recovered. https://status.portkey.ai/incident/443725 Sun, 13 Oct 2024 06:32:23 -0000 https://status.portkey.ai/incident/443725#88c540d7ea6793726141f66cb1fb7972974820a9fd4c03560ef08260f1c81a6b API went down. https://status.portkey.ai/incident/400503 Fri, 19 Jul 2024 06:18:00 -0000 https://status.portkey.ai/incident/400503#82bc34cd392031bf1040519d4e45f8ed1d7531aec24ab49c50173ce0c3f452d0 We deployed an authorization layer update to Portkey which caused our APIs to return 401 to a majority requests. The service came back after 2 minutes of downtime. https://status.portkey.ai/incident/388917 Tue, 25 Jun 2024 01:38:45 -0000 https://status.portkey.ai/incident/388917#0d0cb9108af7315fb0ee3422b273eecb66be8cbcb36c6ec662980311acb1d33a API recovered. https://status.portkey.ai/incident/388917 Tue, 25 Jun 2024 01:30:48 -0000 https://status.portkey.ai/incident/388917#8f52eca32158924ac3d0bf0497b24191f23c6aec6594c88fb0403213d062d758 API went down. https://status.portkey.ai/incident/374081 Fri, 24 May 2024 09:44:00 -0000 https://status.portkey.ai/incident/374081#93e19912c7a30b3b7c6bf450963682b1b36aba175e2a61b195302b8ca240e805 We have fixed the logs for now and are looking at the dropped logs. We'll replay them within the next 4 hours. https://status.portkey.ai/incident/374081 Fri, 24 May 2024 09:34:00 -0000 https://status.portkey.ai/incident/374081#8a2b693930a5e020b8d3265f6d75735e46abb61551184580876fe6d5e90f8d58 Writes to our metrics cluster are delayed and the logs screen is intermittently failing. We're investigating the issue. https://status.portkey.ai/incident/335407 Mon, 04 Mar 2024 06:53:58 -0000 https://status.portkey.ai/incident/335407#fbce6b26831bac4d961e37d5f781e6c946063f21417b5e50e6dd71108f41818c API recovered. https://status.portkey.ai/incident/335407 Mon, 04 Mar 2024 06:48:05 -0000 https://status.portkey.ai/incident/335407#034eaaa583c8d2d05a348e68b4e4f8b161253eeb9a0d1d8f8dacb279d040f304 API went down. https://status.portkey.ai/incident/328818 Mon, 19 Feb 2024 05:39:00 -0000 https://status.portkey.ai/incident/328818#8b57fb721e16fc46498cb788bfacce18c32c4e2c2d2aaf91d8569042d6dee548 API recovered. https://status.portkey.ai/incident/328818 Mon, 19 Feb 2024 05:38:10 -0000 https://status.portkey.ai/incident/328818#88f862855fb7cbf0c8f8613793e4bdd8a8e2ff9695ed0cd018afd6e08b38a358 API went down. https://status.portkey.ai/incident/241739 Mon, 07 Aug 2023 14:47:00 -0000 https://status.portkey.ai/incident/241739#8c5852bdc903827211824d0f0a886375a6dbe693e2e117d184afaa87cf37d8cb We've replayed all the log events. The data should be up to date now. Please reach out to support@portkey.ai in case you face any issues. https://status.portkey.ai/incident/241739 Sat, 05 Aug 2023 11:18:00 -0000 https://status.portkey.ai/incident/241739#56ae0ccebc91d6d6b2e8ca1e6e1e47c3b30298f0be538819240f61f650fe3413 The logs service has been restored and you should start to see incoming logs in realtime. We're working to replay the logs data for the hours when the logging service was impacted. https://status.portkey.ai/incident/241739 Sat, 05 Aug 2023 10:57:00 -0000 https://status.portkey.ai/incident/241739#4529b7eff57ae6acec4bb78bc06099457d5c8ea78ee536d92ab3bb2448ec0e15 We're facing issues propogating logs to our internal analytics store. Users might not be able to see logs & analytics update in real-time at the moment. Please be assured that this does not affect requests & responses to the LLMs you may be using and there will be no data loss. None of your services are affected due to this.