privy Status - Incident history https://status.privy.io privy Fri, 18 Sep 2026 19:18:00 +0000 Database issues causing API outages Type: Incident Duration: 1 hour and 11 minutes Affected Components: APIs Sep 18, 19:18:00 GMT+0 - Investigating - We are experiencing database issues causing outages across our API endpoints. We're currently investigating. Sep 18, 19:55:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 18, 20:29:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 11 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>19:18:00</var> GMT+0</small><br><strong>Investigating</strong> - We are experiencing database issues causing outages across our API endpoints. We're currently investigating..</p> <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>19:55:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>20:29:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 18 Sep 2026 19:18:00 +0000 https://status.privy.io/incident/cmu7d1k3m0iol1fpc71t9fnww https://status.privy.io/incident/cmu7d1k3m0iol1fpc71t9fnww Wallet actions and transaction finality delayed Type: Incident Duration: 1 hour and 59 minutes Affected Components: APIs Sep 18, 17:52:00 GMT+0 - Identified - Wallet actions and transaction finality delayed due to a repeat issue with an upstream provider. Sep 18, 16:39:00 GMT+0 - Monitoring - We continue to monitor the delay. Partial recovery observed. Sep 18, 16:16:00 GMT+0 - Identified - Wallet actions and transaction finality delayed due to an issue with an upstream provider. Partial recovery observed as of 12:39. Sep 18, 16:50:00 GMT+0 - Resolved - Services have recovered, and this incident is resolved. Sep 18, 18:07:00 GMT+0 - Monitoring - We have partially recovered, and we are continuing to monitor the delay. Sep 18, 18:15:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 59 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>17:52:00</var> GMT+0</small><br><strong>Identified</strong> - Wallet actions and transaction finality delayed due to a repeat issue with an upstream provider..</p> <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>16:39:00</var> GMT+0</small><br><strong>Monitoring</strong> - We continue to monitor the delay. Partial recovery observed..</p> <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>16:16:00</var> GMT+0</small><br><strong>Identified</strong> - Wallet actions and transaction finality delayed due to an issue with an upstream provider. Partial recovery observed as of 12:39..</p> <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>16:50:00</var> GMT+0</small><br><strong>Resolved</strong> - Services have recovered, and this incident is resolved..</p> <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>18:07:00</var> GMT+0</small><br><strong>Monitoring</strong> - We have partially recovered, and we are continuing to monitor the delay. .</p> <p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>18:15:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 18 Sep 2026 16:16:00 +0000 https://status.privy.io/incident/cmu76xy530gyx1fpc677jvu2b https://status.privy.io/incident/cmu76xy530gyx1fpc677jvu2b Solana balance webhooks are delayed Type: Incident Duration: 1 hour and 17 minutes Affected Components: Webhooks Sep 11, 15:35:00 GMT+0 - Investigating - We are currently investigating an incident with Solana webhooks. Sep 11, 16:47:00 GMT+0 - Monitoring - Our upstream provider has implemented a fix and are currently monitoring the result. Sep 11, 16:52:01 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 17 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>15:35:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an incident with Solana webhooks..</p> <p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>16:47:00</var> GMT+0</small><br><strong>Monitoring</strong> - Our upstream provider has implemented a fix and are currently monitoring the result..</p> <p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>16:52:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 11 Sep 2026 15:35:00 +0000 https://status.privy.io/incident/cmtx6sslx05cp13nvcblp9nni https://status.privy.io/incident/cmtx6sslx05cp13nvcblp9nni Delays on webhooks and wallet actions Type: Incident Duration: 56 minutes Affected Components: Webhooks, Wallet transactions Sep 4, 18:13:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 4, 18:49:00 GMT+0 - Monitoring - We are seeing some recovery and monitoring the Inngest status here: <https://status.inngest.com/>. Sep 4, 19:09:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 56 minutes

Affected Components: ,

<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>18:13:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>18:49:00</var> GMT+0</small><br><strong>Monitoring</strong> - We are seeing some recovery and monitoring the Inngest status here: <https://status.inngest.com/>. .</p> <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>19:09:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 4 Sep 2026 18:13:00 +0000 https://status.privy.io/incident/cmtnai4fl0e8z1no5rmv61t8m https://status.privy.io/incident/cmtnai4fl0e8z1no5rmv61t8m Robinhood chain experiencing delays Type: Incident Duration: 2 hours and 35 minutes Affected Components: RPC Service Providers Sep 4, 14:25:00 GMT+0 - Resolved - This incident has been resolved. Sep 4, 11:50:00 GMT+0 - Investigating - We are currently investigating this incident with Alchemy (<https://status.alchemy.com/incidents/vj5fxq0h8sfq>). Sep 4, 12:32:00 GMT+0 - Monitoring - We are monitoring the issues with Robinhood chain. Type: Incident

Duration: 2 hours and 35 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>14:25:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>11:50:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident with Alchemy (<https://status.alchemy.com/incidents/vj5fxq0h8sfq>)..</p> <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>12:32:00</var> GMT+0</small><br><strong>Monitoring</strong> - We are monitoring the issues with Robinhood chain. .</p> ]]> Fri, 4 Sep 2026 11:50:00 +0000 https://status.privy.io/incident/cmtn5j4430d2d0wqjwtug1twl https://status.privy.io/incident/cmtn5j4430d2d0wqjwtug1twl Solana token balances appearing stale & elevated Solana /transfer error rate Type: Incident Duration: 42 minutes Affected Components: Wallet transactions Sep 3, 15:27:00 GMT+0 - Investigating - We are currently investigating an incident with an upstream provider. Sep 3, 15:34:48 GMT+0 - Identified - We are working with our provider on a fix. Dashboards may still display stale Solana balances. Some customers may experience 500s on Solana transfers. Sep 3, 16:09:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 42 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>15:27:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an incident with an upstream provider. .</p> <p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>15:34:48</var> GMT+0</small><br><strong>Identified</strong> - We are working with our provider on a fix. Dashboards may still display stale Solana balances. Some customers may experience 500s on Solana transfers..</p> <p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>16:09:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 3 Sep 2026 15:27:00 +0000 https://status.privy.io/incident/cmtlpxwps00n81bo5hv6pqwq4 https://status.privy.io/incident/cmtlpxwps00n81bo5hv6pqwq4 Solana balances and transaction statuses are degraded Type: Incident Duration: 44 minutes Affected Components: Third Party: Coinbase → Coinbase Onramp, Third Party: Google Workspace → Gmail, Third Party: SendGrid → Mail Sending → API v2, Third Party: SendGrid → Mail Sending → SMTP, Third Party: Amazon Web Services – AWS → AWS health, Third Party: SendGrid → Mail Sending → API v3 Sep 2, 09:36:00 GMT+0 - Identified - Solana balances and transaction statuses are degraded due to an upstream provider. <https://helius.statuspage.io/> Sep 2, 10:20:00 GMT+0 - Resolved - Upstream provider back up and systems recovered as of 6:20 AM ET. Type: Incident

Duration: 44 minutes

Affected Components: , , , , ,

<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>09:36:00</var> GMT+0</small><br><strong>Identified</strong> - Solana balances and transaction statuses are degraded due to an upstream provider. <https://helius.statuspage.io/>.</p> <p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>10:20:00</var> GMT+0</small><br><strong>Resolved</strong> - Upstream provider back up and systems recovered as of 6:20 AM ET..</p> ]]> Wed, 2 Sep 2026 09:36:00 +0000 https://status.privy.io/incident/cmtjxjexb00ga0wnwkgp5xl88 https://status.privy.io/incident/cmtjxjexb00ga0wnwkgp5xl88 Instagram OAuth is experiencing issues Type: Incident Duration: 2 hours and 41 minutes Affected Components: OAuth: Google, Twitter, Discord, Github, Apple, Instagram Aug 23, 12:59:00 GMT+0 - Investigating - We've received reports of "Sorry, this page isn't available." when users are attempting to sign in with Instagram or link Instagram accounts. We are currently investigating this incident. Aug 23, 15:40:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 41 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>12:59:00</var> GMT+0</small><br><strong>Investigating</strong> - We've received reports of "Sorry, this page isn't available." when users are attempting to sign in with Instagram or link Instagram accounts. We are currently investigating this incident. .</p> <p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>15:40:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 23 Aug 2026 12:59:00 +0000 https://status.privy.io/incident/cmt5v8mxr1ftv1ameso1nl2am https://status.privy.io/incident/cmt5v8mxr1ftv1ameso1nl2am Cookies-enabled Apps Experiencing 403s Type: Incident Duration: 30 minutes Affected Components: Cookies Aug 12, 18:36:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 12, 18:37:00 GMT+0 - Resolved - This incident has been resolved. Aug 12, 18:07:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 30 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>18:36:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>18:37:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>18:07:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Wed, 12 Aug 2026 18:07:00 +0000 https://status.privy.io/incident/cmsqflkyh01pv0kqiafmyew32 https://status.privy.io/incident/cmsqflkyh01pv0kqiafmyew32 Partial API Outage Type: Incident Duration: 1 hour and 18 minutes Affected Components: APIs Aug 3, 23:46:00 GMT+0 - Investigating - We are observing a portion of of /api/v1/sessions calls failing. Investigation is underway. Aug 4, 01:04:05 GMT+0 - Resolved - This incident has been resolved. Aug 4, 01:02:20 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 1 hour and 18 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>23:46:00</var> GMT+0</small><br><strong>Investigating</strong> - We are observing a portion of of /api/v1/sessions calls failing. Investigation is underway. .</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>01:04:05</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>01:02:20</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Mon, 3 Aug 2026 23:46:00 +0000 https://status.privy.io/incident/cmsdwreuv04y21amruyf093ow https://status.privy.io/incident/cmsdwreuv04y21amruyf093ow Bridge Scheduled Maintenance Type: Maintenance Duration: 30 minutes Affected Components: Bridge API Jul 22, 20:48:38 GMT+0 - Identified - On Saturday, August 1st, Bridge will be undergoing scheduled maintenance, starting at 8:00pm PST for up to 30 minutes. Bridge will be performing maintenance and upgrades on their production database which will improve reliability. During this window no requests can be made to the Bridge API and the Bridge Dashboard. As a result, transfers made by [Privy custodial wallets](https://docs.privy.io/wallets/custodial-wallets/overview) will be unavailable. Non-custodial wallets and all other Privy services are not affected and will remain fully operational. Aug 2, 00:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 2, 00:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 30 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>20:48:38</var> GMT+0</small><br><strong>Identified</strong> - On Saturday, August 1st, Bridge will be undergoing scheduled maintenance, starting at 8:00pm PST for up to 30 minutes. Bridge will be performing maintenance and upgrades on their production database which will improve reliability. During this window no requests can be made to the Bridge API and the Bridge Dashboard. As a result, transfers made by [Privy custodial wallets](https://docs.privy.io/wallets/custodial-wallets/overview) will be unavailable. Non-custodial wallets and all other Privy services are not affected and will remain fully operational..</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>00:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sun, 2 Aug 2026 00:00:00 +0000 https://status.privy.io/maintenance/cmrwk1lrb02w70lmoc6g7sygp https://status.privy.io/maintenance/cmrwk1lrb02w70lmoc6g7sygp Partial API outage Type: Incident Duration: 1 minute Affected Components: APIs Jul 29, 12:24:00 GMT+0 - Investigating - We are currently investigating API request failures due to increased database load. Jul 29, 12:25:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 minute

Affected Components:

<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>12:24:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating API request failures due to increased database load..</p> <p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>12:25:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 29 Jul 2026 12:24:00 +0000 https://status.privy.io/incident/cms62ping02dh0kpagkgqrqti https://status.privy.io/incident/cms62ping02dh0kpagkgqrqti Degraded wallet actions and webhooks Type: Incident Affected Components: Webhooks, Wallet transactions Jul 16, 14:47:00 GMT+0 - Resolved - From approximately 9:29 AM – 12:10 PM UTC today, our third-party orchestration service experienced elevated latency and errors which caused wallets actions and webhooks to fail or be delayed. The issue fully resolved around 12:10 PM UTC. Type: Incident

Affected Components: ,

<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>14:47:00</var> GMT+0</small><br><strong>Resolved</strong> - From approximately 9:29 AM – 12:10 PM UTC today, our third-party orchestration service experienced elevated latency and errors which caused wallets actions and webhooks to fail or be delayed. The issue fully resolved around 12:10 PM UTC..</p> ]]> Thu, 16 Jul 2026 14:47:00 +0000 https://status.privy.io/incident/cmrnmjd7300ll0kqli1er41ng https://status.privy.io/incident/cmrnmjd7300ll0kqli1er41ng Optimism Mainnet is stalled Type: Incident Duration: 40 minutes Affected Components: RPC Service Providers Jul 7, 18:00:00 GMT+0 - Identified - The Optimism Mainnet is stalled, and therefore Privy services on Optimism will not process or be degraded. We are monitoring the situation and will update when the chain is back online. <https://status.quicknode.com/incidents/2y0090hlszb2> Jul 7, 18:21:00 GMT+0 - Monitoring - Our third party providers for Optimism mainnet are functioning again, and we will continue to monitor. Jul 7, 18:39:33 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 40 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Identified</strong> - The Optimism Mainnet is stalled, and therefore Privy services on Optimism will not process or be degraded. We are monitoring the situation and will update when the chain is back online. <https://status.quicknode.com/incidents/2y0090hlszb2>.</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>18:21:00</var> GMT+0</small><br><strong>Monitoring</strong> - Our third party providers for Optimism mainnet are functioning again, and we will continue to monitor..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>18:39:33</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 7 Jul 2026 18:00:00 +0000 https://status.privy.io/incident/cmrazdvh709yv1ansiv0satix https://status.privy.io/incident/cmrazdvh709yv1ansiv0satix EVM gas sponsored transactions degraded Type: Incident Duration: 39 minutes Affected Components: Gas Sponsorship Jul 7, 00:06:00 GMT+0 - Investigating - We are currently investigating this incident. Jul 7, 00:30:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. We have determined that the remaining impacted chains are: * 988 - Stable * 2201 - Stable Testnet * 4663 — Robinhood Mainnet * 46630 — Robinhood Testnet * 11011 — Shape Sepolia Jul 7, 00:45:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 39 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>00:06:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>00:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. We have determined that the remaining impacted chains are: * 988 - Stable * 2201 - Stable Testnet * 4663 — Robinhood Mainnet * 46630 — Robinhood Testnet * 11011 — Shape Sepolia.</p> <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>00:45:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 7 Jul 2026 00:06:00 +0000 https://status.privy.io/incident/cmr9wq27b00t00zpihxaq3dow https://status.privy.io/incident/cmr9wq27b00t00zpihxaq3dow Solana webhooks are delayed Type: Incident Duration: 2 hours and 53 minutes Affected Components: Webhooks Jul 1, 17:25:00 GMT+0 - Resolved - This incident has been resolved. Jul 1, 14:32:00 GMT+0 - Investigating - We are currently investigating this incident which is causing all Solana webhooks to be delayed. Jul 1, 15:18:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jul 1, 15:25:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 2 hours and 53 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>17:25:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>14:32:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident which is causing all Solana webhooks to be delayed..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>15:18:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>15:25:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> ]]> Wed, 1 Jul 2026 14:32:00 +0000 https://status.privy.io/incident/cmr28q6vj00e10rpybeo5lqvx https://status.privy.io/incident/cmr28q6vj00e10rpybeo5lqvx X (fka Twitter) API experiencing outage Type: Incident Duration: 2 hours and 6 minutes Affected Components: OAuth: Google, Twitter, Discord, Github, Apple, Instagram Jul 1, 01:30:53 GMT+0 - Monitoring - The X API appears to be functional. We are continuing to monitor this service. Jul 1, 02:06:26 GMT+0 - Resolved - This incident has been resolved. Jul 1, 00:00:00 GMT+0 - Investigating - The X (formerly Twitter) API is experiencing issues. Users attempting to sign in with X may see an `Unable to fetch user details from provider.` error. Type: Incident

Duration: 2 hours and 6 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>01:30:53</var> GMT+0</small><br><strong>Monitoring</strong> - The X API appears to be functional. We are continuing to monitor this service..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>02:06:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Investigating</strong> - The X (formerly Twitter) API is experiencing issues. Users attempting to sign in with X may see an `Unable to fetch user details from provider.` error..</p> ]]> Wed, 1 Jul 2026 00:00:00 +0000 https://status.privy.io/incident/cmr1cn3jc02m90zpgl8kz5fpw https://status.privy.io/incident/cmr1cn3jc02m90zpgl8kz5fpw Base Mainnet Unsafe Head Stall Type: Incident Duration: 21 hours and 57 minutes Affected Components: Webhooks Jun 26, 14:00:02 GMT+0 - Resolved - Base sequencer and supporting systems remain stable, blocks are being produced normally, and we have verified widespread recovery in the ecosystem. Refer to <https://status.base.org/> for more specifics on the Base outage. Jun 25, 16:03:00 GMT+0 - Investigating - Base is experiencing degraded performance: <https://status.base.org/incidents/5c4gm1wzbjs4>. We are monitoring for the impact on Privy. Jun 25, 18:00:00 GMT+0 - Monitoring - Base has implemented a fix and we are currently monitoring the result. Type: Incident

Duration: 21 hours and 57 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>14:00:02</var> GMT+0</small><br><strong>Resolved</strong> - Base sequencer and supporting systems remain stable, blocks are being produced normally, and we have verified widespread recovery in the ecosystem. Refer to <https://status.base.org/> for more specifics on the Base outage..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>16:03:00</var> GMT+0</small><br><strong>Investigating</strong> - Base is experiencing degraded performance: <https://status.base.org/incidents/5c4gm1wzbjs4>. We are monitoring for the impact on Privy..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - Base has implemented a fix and we are currently monitoring the result..</p> ]]> Thu, 25 Jun 2026 16:03:00 +0000 https://status.privy.io/incident/cmqtpkzgl00b72ip6tzbgm6cw https://status.privy.io/incident/cmqtpkzgl00b72ip6tzbgm6cw X (fka Twitter) API experiencing outage Type: Incident Duration: 9 hours and 45 minutes Affected Components: OAuth: Google, Twitter, Discord, Github, Apple, Instagram Jun 16, 16:44:55 GMT+0 - Resolved - This incident has been resolved. Jun 16, 07:00:00 GMT+0 - Investigating - The X (formerly Twitter) API is experiencing issues. Users attempting to sign in with X may see an ERR\_TOO\_MANY\_REDIRECTS error. This appears to be an undocumented X API outage affecting OAuth 2.0\. X developers report that OAuth 1.0a is still functional. As a workaround, you can set up OAuth 1.0a by creating an X Developer account and adding your X API OAuth 1.0a credentials to the Privy dashboard. Detailed instructions are available here: <https://docs.privy.io/basics/get-started/dashboard/configure-login-methods#oauth-login-methods-google-twitter-etc:x-formerly-known-as-twitter:oauth-1-0a-for-twitter> Jun 16, 15:24:33 GMT+0 - Monitoring - The X API (both OAuth 2.0 and 1.0a) appears to be functional. We are continuing to monitor this service. Type: Incident

Duration: 9 hours and 45 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>16:44:55</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Investigating</strong> - The X (formerly Twitter) API is experiencing issues. Users attempting to sign in with X may see an ERR\_TOO\_MANY\_REDIRECTS error. This appears to be an undocumented X API outage affecting OAuth 2.0\. X developers report that OAuth 1.0a is still functional. As a workaround, you can set up OAuth 1.0a by creating an X Developer account and adding your X API OAuth 1.0a credentials to the Privy dashboard. Detailed instructions are available here: <https://docs.privy.io/basics/get-started/dashboard/configure-login-methods#oauth-login-methods-google-twitter-etc:x-formerly-known-as-twitter:oauth-1-0a-for-twitter>.</p> <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>15:24:33</var> GMT+0</small><br><strong>Monitoring</strong> - The X API (both OAuth 2.0 and 1.0a) appears to be functional. We are continuing to monitor this service..</p> ]]> Tue, 16 Jun 2026 07:00:00 +0000 https://status.privy.io/incident/cmqglk3zi02242plg15x4ds9k https://status.privy.io/incident/cmqglk3zi02242plg15x4ds9k Plasma mainnet balance webhooks are delayed Type: Incident Duration: 58 minutes Affected Components: Webhooks May 28, 04:50:00 GMT+0 - Identified - Currently Plasma mainnet deposit and withdrawal webhooks are delayed due to an upstream issue with Quicknode: <https://status.quicknode.com/> May 28, 05:48:00 GMT+0 - Resolved - This incident has been resolved. All events have been backfilled. Type: Incident

Duration: 58 minutes

Affected Components:

<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>04:50:00</var> GMT+0</small><br><strong>Identified</strong> - Currently Plasma mainnet deposit and withdrawal webhooks are delayed due to an upstream issue with Quicknode: <https://status.quicknode.com/>.</p> <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>05:48:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. All events have been backfilled..</p> ]]> Thu, 28 May 2026 04:50:00 +0000 https://status.privy.io/incident/cmpp2dhad01ugp8moa79mzaet https://status.privy.io/incident/cmpp2dhad01ugp8moa79mzaet Solana Gas Sponsorship Type: Incident Duration: 2 hours and 5 minutes Affected Components: Gas Sponsorship May 21, 04:56:00 GMT+0 - Investigating - We are currently investigating this incident affecting \~1018 gas sponsorship transactions due to an upstream provider error. May 21, 07:01:00 GMT+0 - Resolved - We identified that the upstream provider error was inadvertently caused by increased usage on endpoints. This incident has been resolved. Type: Incident

Duration: 2 hours and 5 minutes

Affected Components:

<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>04:56:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident affecting \~1018 gas sponsorship transactions due to an upstream provider error. .</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>07:01:00</var> GMT+0</small><br><strong>Resolved</strong> - We identified that the upstream provider error was inadvertently caused by increased usage on endpoints. This incident has been resolved..</p> ]]> Thu, 21 May 2026 04:56:00 +0000 https://status.privy.io/incident/cmpfybtgu000jntopym0xbidu https://status.privy.io/incident/cmpfybtgu000jntopym0xbidu Deposit and Withdrawal Webhooks are delayed Type: Incident Duration: 21 minutes Affected Components: Webhooks Apr 30, 14:11:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 30, 14:28:00 GMT+0 - Monitoring - Delayed webhooks are now sending. We are backfilling. Apr 30, 14:32:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 21 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>14:11:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>14:28:00</var> GMT+0</small><br><strong>Monitoring</strong> - Delayed webhooks are now sending. We are backfilling. .</p> <p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>14:32:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 30 Apr 2026 14:11:00 +0000 https://status.privy.io/incident/cmoll35st084cjaaic5q3tepf https://status.privy.io/incident/cmoll35st084cjaaic5q3tepf Gas sponsored transactions failing Type: Incident Duration: 2 hours and 3 minutes Affected Components: Gas Sponsorship Apr 21, 13:07:00 GMT+0 - Investigating - A subset of gas sponsored transactions are failing with error message "Gas sponsorship is not enabled". Apr 21, 15:10:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 21, 15:10:01 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 3 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>13:07:00</var> GMT+0</small><br><strong>Investigating</strong> - A subset of gas sponsored transactions are failing with error message "Gas sponsorship is not enabled"..</p> <p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>15:10:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>15:10:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 21 Apr 2026 13:07:00 +0000 https://status.privy.io/incident/cmo8s1g5c0005v8og4m4dcfh6 https://status.privy.io/incident/cmo8s1g5c0005v8og4m4dcfh6 Solana mainnet webhooks Type: Incident Duration: 1 hour and 36 minutes Affected Components: Webhooks Apr 21, 01:07:00 GMT+0 - Identified - Our upstream provider Goldsky is having issues with Solana mainnet. They are aware and investigating. <https://status.goldsky.com/> Apr 21, 02:42:43 GMT+0 - Resolved - This issue has been resolved. Type: Incident

Duration: 1 hour and 36 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>01:07:00</var> GMT+0</small><br><strong>Identified</strong> - Our upstream provider Goldsky is having issues with Solana mainnet. They are aware and investigating. <https://status.goldsky.com/>.</p> <p><small>Apr <var data-var='date'> 21</var>, <var data-var='time'>02:42:43</var> GMT+0</small><br><strong>Resolved</strong> - This issue has been resolved..</p> ]]> Tue, 21 Apr 2026 01:07:00 +0000 https://status.privy.io/incident/cmo7y3vni002mwsrc1s8z7nar https://status.privy.io/incident/cmo7y3vni002mwsrc1s8z7nar Inngest is experiencing degraded performance, which is causing transaction webhooks to be delayed Type: Incident Duration: 4 hours and 28 minutes Affected Components: Webhooks Apr 15, 13:00:00 GMT+0 - Investigating - There is an issue with our third party async job provider Inngest (<https://status.inngest.com/>) that is causing transaction webhooks to be delayed. Additional impacted services include: gas sponsorship credit usage Apr 15, 14:23:00 GMT+0 - Identified - Inngest has scaled up systems and is continuing to work on a fix for this incident: <https://status.inngest.com/incidents/01KP8H3NQM34K0RTB0BH7VNNMP> Apr 15, 15:23:00 GMT+0 - Identified - Inngest has reported that their changes have increased throughput, but not yet to typical levels. Track Inngest's status page here: <https://status.inngest.com/incidents/01KP8H3NQM34K0RTB0BH7VNNMP> Apr 15, 17:28:00 GMT+0 - Resolved - While Inngest continues to catch up (see Inngest's status page: <https://status.inngest.com/incidents/01KP8H3NQM34K0RTB0BH7VNNMP>), we have applied changes on our end so that transaction webhooks are no longer delayed. Type: Incident

Duration: 4 hours and 28 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Investigating</strong> - There is an issue with our third party async job provider Inngest (<https://status.inngest.com/>) that is causing transaction webhooks to be delayed. Additional impacted services include: gas sponsorship credit usage.</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>14:23:00</var> GMT+0</small><br><strong>Identified</strong> - Inngest has scaled up systems and is continuing to work on a fix for this incident: <https://status.inngest.com/incidents/01KP8H3NQM34K0RTB0BH7VNNMP>.</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>15:23:00</var> GMT+0</small><br><strong>Identified</strong> - Inngest has reported that their changes have increased throughput, but not yet to typical levels. Track Inngest's status page here: <https://status.inngest.com/incidents/01KP8H3NQM34K0RTB0BH7VNNMP>.</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>17:28:00</var> GMT+0</small><br><strong>Resolved</strong> - While Inngest continues to catch up (see Inngest's status page: <https://status.inngest.com/incidents/01KP8H3NQM34K0RTB0BH7VNNMP>), we have applied changes on our end so that transaction webhooks are no longer delayed..</p> ]]> Wed, 15 Apr 2026 13:00:00 +0000 https://status.privy.io/incident/cmo05y0o30136m655tz2qjvif https://status.privy.io/incident/cmo05y0o30136m655tz2qjvif Issues with sending EVM sponsored transactions Type: Incident Duration: 1 day and 1 hour Affected Components: Gas Sponsorship Apr 7, 19:30:00 GMT+0 - Investigating - We are experiencing issues with our downstream provider and are currently investigating this incident. <https://status.zerodev.app/> Apr 7, 19:41:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Our downstream provider's status can be tracked here: <https://status.zerodev.app/> Apr 7, 19:55:00 GMT+0 - Resolved - We continue to monitor as our third party service provider has recovered. Type: Incident

Duration: 1 day and 1 hour

Affected Components:

<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are experiencing issues with our downstream provider and are currently investigating this incident. <https://status.zerodev.app/>.</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>19:41:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. Our downstream provider's status can be tracked here: <https://status.zerodev.app/>.</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>19:55:00</var> GMT+0</small><br><strong>Resolved</strong> - We continue to monitor as our third party service provider has recovered..</p> ]]> Tue, 7 Apr 2026 19:30:00 +0000 https://status.privy.io/incident/cmnp19wam14gl13jsh051pbg3 https://status.privy.io/incident/cmnp19wam14gl13jsh051pbg3 Coinbase Onramp Scheduled Maintenance Type: Maintenance Duration: 4 hours Affected Components: Third Party: Coinbase → Coinbase Onramp Oct 25, 14:00:00 GMT+0 - Identified - On Saturday, October 25th, Coinbase will be undergoing scheduled maintenance, starting at 7:00am PST. Coinbase expects this to take up to 4 hours, however this estimated time is subject to change. Please monitor the [CDP Status Page](https://cdpstatus.coinbase.com/) for updates. During this time, Coinbase Onramp and Offramp services will not be available, and all transactions will be prohibited. Users will get errors on session creation from the API flow, and the UI will showcase an error message indicating that onramp/offramp is currently unavailable. Oct 25, 14:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 25, 18:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 4 hours

Affected Components:

<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> - On Saturday, October 25th, Coinbase will be undergoing scheduled maintenance, starting at 7:00am PST. Coinbase expects this to take up to 4 hours, however this estimated time is subject to change. Please monitor the [CDP Status Page](https://cdpstatus.coinbase.com/) for updates. During this time, Coinbase Onramp and Offramp services will not be available, and all transactions will be prohibited. Users will get errors on session creation from the API flow, and the UI will showcase an error message indicating that onramp/offramp is currently unavailable..</p> <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>14:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sat, 25 Oct 2025 14:00:00 +0000 https://status.privy.io/maintenance/cmh3o8cmt00gvgl9fn0myzrqf https://status.privy.io/maintenance/cmh3o8cmt00gvgl9fn0myzrqf