Notice history

Jun 2026

Jul 2026

Aug 2026

Jun 2026

Jul 2026

Aug 2026

Jun 2026

Jul 2026

Aug 2026

Jun 2026

Jul 2026

Aug 2026

Jun 2026

Jul 2026

Aug 2026

Jun 2026

Jul 2026

Aug 2026

Jun 2026

Jul 2026

Aug 2026

Jun 2026

Jul 2026

Aug 2026

Jun 2026

Jul 2026

Aug 2026

Resolved
August 12, 2026 at 6:37 PMUTC
Resolved
August 12, 2026 at 6:37 PMUTC
This incident has been resolved.
Monitoring
August 12, 2026 at 6:36 PMUTC
Monitoring
August 12, 2026 at 6:36 PMUTC
We implemented a fix and are currently monitoring the result.
Investigating
August 12, 2026 at 6:07 PMUTC
Investigating
August 12, 2026 at 6:07 PMUTC
We are currently investigating this incident.

Resolved
August 04, 2026 at 1:04 AMUTC
Resolved
August 04, 2026 at 1:04 AMUTC
This incident has been resolved.
Monitoring
August 04, 2026 at 1:02 AMUTC
Monitoring
August 04, 2026 at 1:02 AMUTC
We implemented a fix and are currently monitoring the result.
Investigating
August 03, 2026 at 11:46 PMUTC
Investigating
August 03, 2026 at 11:46 PMUTC
We are observing a portion of of /api/v1/sessions calls failing. Investigation is underway.

Bridge Scheduled Maintenance

Completed
August 02, 2026 at 12:30 AMUTC
Completed
August 02, 2026 at 12:30 AMUTC
Maintenance has completed successfully
In progress
August 02, 2026 at 12:00 AMUTC
In progress
August 02, 2026 at 12:00 AMUTC
Maintenance is now in progress
Planned
July 22, 2026 at 8:48 PMUTC
Planned
July 22, 2026 at 8:48 PMUTC
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 will be unavailable. Non-custodial wallets and all other Privy services are not affected and will remain fully operational.

Resolved
July 29, 2026 at 12:25 PMUTC
Resolved
July 29, 2026 at 12:25 PMUTC
This incident has been resolved.
Investigating
July 29, 2026 at 12:24 PMUTC
Investigating
July 29, 2026 at 12:24 PMUTC
We are currently investigating API request failures due to increased database load.

Resolved
July 16, 2026 at 2:47 PMUTC
Resolved
July 16, 2026 at 2:47 PMUTC
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.

Resolved
July 07, 2026 at 6:39 PMUTC
Resolved
July 07, 2026 at 6:39 PMUTC
This incident has been resolved.
Monitoring
July 07, 2026 at 6:21 PMUTC
Monitoring
July 07, 2026 at 6:21 PMUTC
Our third party providers for Optimism mainnet are functioning again, and we will continue to monitor.
Identified
July 07, 2026 at 6:00 PMUTC
Identified
July 07, 2026 at 6:00 PMUTC
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

Resolved
July 07, 2026 at 12:45 AMUTC
Resolved
July 07, 2026 at 12:45 AMUTC
This incident has been resolved.
Identified
July 07, 2026 at 12:30 AMUTC
Identified
July 07, 2026 at 12:30 AMUTC
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
Investigating
July 07, 2026 at 12:06 AMUTC
Investigating
July 07, 2026 at 12:06 AMUTC
We are currently investigating this incident.

Resolved
July 01, 2026 at 5:25 PMUTC
Resolved
July 01, 2026 at 5:25 PMUTC
This incident has been resolved.
Monitoring
July 01, 2026 at 3:25 PMUTC
Monitoring
July 01, 2026 at 3:25 PMUTC
We implemented a fix and are currently monitoring the result.
Identified
July 01, 2026 at 3:18 PMUTC
Identified
July 01, 2026 at 3:18 PMUTC
We are continuing to work on a fix for this incident.
Investigating
July 01, 2026 at 2:32 PMUTC
Investigating
July 01, 2026 at 2:32 PMUTC
We are currently investigating this incident which is causing all Solana webhooks to be delayed.

Resolved
June 26, 2026 at 2:00 PMUTC
Resolved
June 26, 2026 at 2:00 PMUTC
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.
Monitoring
June 25, 2026 at 6:00 PMUTC
Monitoring
June 25, 2026 at 6:00 PMUTC
Base has implemented a fix and we are currently monitoring the result.
Investigating
June 25, 2026 at 4:03 PMUTC
Investigating
June 25, 2026 at 4:03 PMUTC
Base is experiencing degraded performance: https://status.base.org/incidents/5c4gm1wzbjs4. We are monitoring for the impact on Privy.

Resolved
June 16, 2026 at 4:44 PMUTC
Resolved
June 16, 2026 at 4:44 PMUTC
This incident has been resolved.
Monitoring
June 16, 2026 at 3:24 PMUTC
Monitoring
June 16, 2026 at 3:24 PMUTC
The X API (both OAuth 2.0 and 1.0a) appears to be functional. We are continuing to monitor this service.
Investigating
June 16, 2026 at 7:00 AMUTC
Investigating
June 16, 2026 at 7:00 AMUTC
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 2026 to Aug 2026

privy - Notice history