<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.privy.io,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.privy.io"/>
  <link rel="self" type="application/atom+xml" href="https://status.privy.io/history.atom"/>
  <title>privy Status - Incident history</title>
  <updated>2026-09-18T19:18:00.000+00:00</updated>
  <author>
    <name>privy</name>
  </author>
  
<entry>
  <id>tag:status.privy.io,2005:Incident/cmu7d1k3m0iol1fpc71t9fnww</id>
  <published>2026-09-18T19:18:00.000+00:00</published>
  <updated>2026-09-18T19:18:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmu7d1k3m0iol1fpc71t9fnww"/>
  <title>Database issues causing API outages</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 11 minutes</p>
    <p><strong>Affected Components:</strong> APIs</p>
    <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&#039;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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmu76xy530gyx1fpc677jvu2b</id>
  <published>2026-09-18T16:16:00.000+00:00</published>
  <updated>2026-09-18T17:52:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmu76xy530gyx1fpc677jvu2b"/>
  <title>Wallet actions and transaction finality delayed</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 59 minutes</p>
    <p><strong>Affected Components:</strong> APIs</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmtx6sslx05cp13nvcblp9nni</id>
  <published>2026-09-11T15:35:00.000+00:00</published>
  <updated>2026-09-11T15:35:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmtx6sslx05cp13nvcblp9nni"/>
  <title>Solana balance webhooks are delayed</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 17 minutes</p>
    <p><strong>Affected Components:</strong> Webhooks</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmtnai4fl0e8z1no5rmv61t8m</id>
  <published>2026-09-04T18:13:00.000+00:00</published>
  <updated>2026-09-04T18:13:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmtnai4fl0e8z1no5rmv61t8m"/>
  <title>Delays on webhooks and wallet actions</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 56 minutes</p>
    <p><strong>Affected Components:</strong> Webhooks, Wallet transactions</p>
    <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: &lt;https://status.inngest.com/&gt;. .</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmtn5j4430d2d0wqjwtug1twl</id>
  <published>2026-09-04T11:50:00.000+00:00</published>
  <updated>2026-09-04T14:25:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmtn5j4430d2d0wqjwtug1twl"/>
  <title>Robinhood chain experiencing delays </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 35 minutes</p>
    <p><strong>Affected Components:</strong> RPC Service Providers</p>
    <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 (&lt;https://status.alchemy.com/incidents/vj5fxq0h8sfq&gt;)..</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmtlpxwps00n81bo5hv6pqwq4</id>
  <published>2026-09-03T15:27:00.000+00:00</published>
  <updated>2026-09-03T15:27:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmtlpxwps00n81bo5hv6pqwq4"/>
  <title>Solana token balances appearing stale &amp; elevated Solana /transfer error rate</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 42 minutes</p>
    <p><strong>Affected Components:</strong> Wallet transactions</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmtjxjexb00ga0wnwkgp5xl88</id>
  <published>2026-09-02T09:36:00.000+00:00</published>
  <updated>2026-09-02T09:36:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmtjxjexb00ga0wnwkgp5xl88"/>
  <title>Solana balances and transaction statuses are degraded</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 44 minutes</p>
    <p><strong>Affected Components:</strong> 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</p>
    <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.  
  
&lt;https://helius.statuspage.io/&gt;.</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmt5v8mxr1ftv1ameso1nl2am</id>
  <published>2026-08-23T12:59:00.000+00:00</published>
  <updated>2026-08-23T12:59:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmt5v8mxr1ftv1ameso1nl2am"/>
  <title>Instagram OAuth is experiencing issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> OAuth: Google, Twitter, Discord, Github, Apple, Instagram</p>
    <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&#039;ve received reports of &quot;Sorry, this page isn&#039;t available.&quot; 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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmsqflkyh01pv0kqiafmyew32</id>
  <published>2026-08-12T18:07:00.000+00:00</published>
  <updated>2026-08-12T18:36:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmsqflkyh01pv0kqiafmyew32"/>
  <title>Cookies-enabled Apps Experiencing 403s</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> Cookies</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmsdwreuv04y21amruyf093ow</id>
  <published>2026-08-03T23:46:00.000+00:00</published>
  <updated>2026-08-03T23:46:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmsdwreuv04y21amruyf093ow"/>
  <title>Partial API Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 18 minutes</p>
    <p><strong>Affected Components:</strong> APIs</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Maintenance/cmrwk1lrb02w70lmoc6g7sygp</id>
  <published>2026-08-02T00:00:00.000+00:00</published>
  <updated>2026-07-22T20:48:38.006+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/maintenance/cmrwk1lrb02w70lmoc6g7sygp"/>
  <title>Bridge Scheduled Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> Bridge API</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cms62ping02dh0kpagkgqrqti</id>
  <published>2026-07-29T12:24:00.000+00:00</published>
  <updated>2026-07-29T12:24:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cms62ping02dh0kpagkgqrqti"/>
  <title>Partial API outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> APIs</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmrnmjd7300ll0kqli1er41ng</id>
  <published>2026-07-16T14:47:00.000+00:00</published>
  <updated>2026-07-16T14:47:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmrnmjd7300ll0kqli1er41ng"/>
  <title>Degraded wallet actions and webhooks</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Webhooks, Wallet transactions</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmrazdvh709yv1ansiv0satix</id>
  <published>2026-07-07T18:00:00.000+00:00</published>
  <updated>2026-07-07T18:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmrazdvh709yv1ansiv0satix"/>
  <title>Optimism Mainnet is stalled</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 40 minutes</p>
    <p><strong>Affected Components:</strong> RPC Service Providers</p>
    <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.  
  
&lt;https://status.quicknode.com/incidents/2y0090hlszb2&gt;.</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmr9wq27b00t00zpihxaq3dow</id>
  <published>2026-07-07T00:06:00.000+00:00</published>
  <updated>2026-07-07T00:06:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmr9wq27b00t00zpihxaq3dow"/>
  <title>EVM gas sponsored transactions degraded</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 39 minutes</p>
    <p><strong>Affected Components:</strong> Gas Sponsorship</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmr28q6vj00e10rpybeo5lqvx</id>
  <published>2026-07-01T14:32:00.000+00:00</published>
  <updated>2026-07-01T17:25:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmr28q6vj00e10rpybeo5lqvx"/>
  <title>Solana webhooks are delayed</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 53 minutes</p>
    <p><strong>Affected Components:</strong> Webhooks</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmr1cn3jc02m90zpgl8kz5fpw</id>
  <published>2026-07-01T00:00:00.000+00:00</published>
  <updated>2026-07-01T01:30:53.684+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmr1cn3jc02m90zpgl8kz5fpw"/>
  <title>X (fka Twitter) API experiencing outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 6 minutes</p>
    <p><strong>Affected Components:</strong> OAuth: Google, Twitter, Discord, Github, Apple, Instagram</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmqtpkzgl00b72ip6tzbgm6cw</id>
  <published>2026-06-25T16:03:00.000+00:00</published>
  <updated>2026-06-26T14:00:02.775+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmqtpkzgl00b72ip6tzbgm6cw"/>
  <title>Base Mainnet Unsafe Head Stall</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours and 57 minutes</p>
    <p><strong>Affected Components:</strong> Webhooks</p>
    <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 &lt;https://status.base.org/&gt; 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: &lt;https://status.base.org/incidents/5c4gm1wzbjs4&gt;. 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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmqglk3zi02242plg15x4ds9k</id>
  <published>2026-06-16T07:00:00.000+00:00</published>
  <updated>2026-06-16T16:44:55.154+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmqglk3zi02242plg15x4ds9k"/>
  <title>X (fka Twitter) API experiencing outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> OAuth: Google, Twitter, Discord, Github, Apple, Instagram</p>
    <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: &lt;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&gt;.</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmpp2dhad01ugp8moa79mzaet</id>
  <published>2026-05-28T04:50:00.000+00:00</published>
  <updated>2026-05-28T04:50:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmpp2dhad01ugp8moa79mzaet"/>
  <title>Plasma mainnet balance webhooks are delayed</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 58 minutes</p>
    <p><strong>Affected Components:</strong> Webhooks</p>
    <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: &lt;https://status.quicknode.com/&gt;.</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmpfybtgu000jntopym0xbidu</id>
  <published>2026-05-21T04:56:00.000+00:00</published>
  <updated>2026-05-21T04:56:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmpfybtgu000jntopym0xbidu"/>
  <title>Solana Gas Sponsorship</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> Gas Sponsorship</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmoll35st084cjaaic5q3tepf</id>
  <published>2026-04-30T14:11:00.000+00:00</published>
  <updated>2026-04-30T14:11:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmoll35st084cjaaic5q3tepf"/>
  <title>Deposit and Withdrawal Webhooks are delayed</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 minutes</p>
    <p><strong>Affected Components:</strong> Webhooks</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmo8s1g5c0005v8og4m4dcfh6</id>
  <published>2026-04-21T13:07:00.000+00:00</published>
  <updated>2026-04-21T13:07:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmo8s1g5c0005v8og4m4dcfh6"/>
  <title>Gas sponsored transactions failing</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 3 minutes</p>
    <p><strong>Affected Components:</strong> Gas Sponsorship</p>
    <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 &quot;Gas sponsorship is not enabled&quot;..</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmo7y3vni002mwsrc1s8z7nar</id>
  <published>2026-04-21T01:07:00.000+00:00</published>
  <updated>2026-04-21T01:07:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmo7y3vni002mwsrc1s8z7nar"/>
  <title>Solana mainnet webhooks</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 36 minutes</p>
    <p><strong>Affected Components:</strong> Webhooks</p>
    <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.  
  
&lt;https://status.goldsky.com/&gt;.</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmo05y0o30136m655tz2qjvif</id>
  <published>2026-04-15T13:00:00.000+00:00</published>
  <updated>2026-04-15T13:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmo05y0o30136m655tz2qjvif"/>
  <title>Inngest is experiencing degraded performance, which is causing transaction webhooks to be delayed</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 28 minutes</p>
    <p><strong>Affected Components:</strong> Webhooks</p>
    <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 (&lt;https://status.inngest.com/&gt;) 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: &lt;https://status.inngest.com/incidents/01KP8H3NQM34K0RTB0BH7VNNMP&gt;.</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&#039;s status page here: &lt;https://status.inngest.com/incidents/01KP8H3NQM34K0RTB0BH7VNNMP&gt;.</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&#039;s status page: &lt;https://status.inngest.com/incidents/01KP8H3NQM34K0RTB0BH7VNNMP&gt;), we have applied changes on our end so that transaction webhooks are no longer delayed..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Incident/cmnp19wam14gl13jsh051pbg3</id>
  <published>2026-04-07T19:30:00.000+00:00</published>
  <updated>2026-04-07T19:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/incident/cmnp19wam14gl13jsh051pbg3"/>
  <title>Issues with sending EVM sponsored transactions</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 1 hour</p>
    <p><strong>Affected Components:</strong> Gas Sponsorship</p>
    <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.  
  
&lt;https://status.zerodev.app/&gt;.</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&#039;s status can be tracked here: &lt;https://status.zerodev.app/&gt;.</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.privy.io,2005:Maintenance/cmh3o8cmt00gvgl9fn0myzrqf</id>
  <published>2025-10-25T14:00:00.000+00:00</published>
  <updated>2025-10-25T14:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.privy.io/maintenance/cmh3o8cmt00gvgl9fn0myzrqf"/>
  <title>Coinbase Onramp Scheduled Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> Third Party: Coinbase → Coinbase Onramp</p>
    <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>

        ]]>
  </content>
</entry>

</feed>