PayPal Outage History

PayPal Payflow services briefly degraded in North America, affecting TSYS merchants processing payments with Payflow. Merchants attempting to process transactions on TSYS may encounter the error RESULT 12 RE ENTER during the incident. The outage affected Payflow, Payflow Processors, and Payflow APIs. The incident began at Jun 24, 2025 6:24 PM UTC and lasted until Jun 24, 2025 6:28 PM UTC, spanning about 4 minutes.

PayPal published 2 status updates during the incident: an initial notification at Jun 24, 2025 6:24 PM UTC describing the TSYS error and affected regions, followed by a resolution update at Jun 24, 2025 6:28 PM UTC confirming Payflow components had returned to normal.

On 6:04 PM UTC, PayPal's Braintree APAC services experienced an outage that affected NAB Transact merchants in Australia and New Zealand. Merchants attempting to process transactions may have encountered the error 3000: Processor Network Unavailable - Try Again, impacting PayPal APAC Transaction Processing and Braintree APAC Transaction Processing.

The outage lasted from 6:04 PM UTC to 8:18 PM UTC, approximately 2 hours and 14 minutes. The provider issued four official status updates during the incident as teams worked to restore services. By the end of the window, the affected components were returned to normal for APAC NAB Transact merchants. A small number of user reports described payment difficulties during the outage.

PayPal reported a production incident affecting the Account component, with potential impact to new account creation. The initial notification identified APAC as affected and noted engineers were actively working to resolve the issue. The outage began at 5:33 PM UTC and the Account component moved to degraded at 5:38 PM UTC, with the incident lasting about 4 hours and 20 minutes before being resolved by 9:58 PM UTC. The status page posted two updates during the incident to communicate impact and restoration.

User reports described login problems and debit-related issues across various locations, including Des Moines, Iowa; Edgerton, Wisconsin; and Pontypool, Wales, United Kingdom, indicating a broader impact on account workflows beyond initial APAC notice.

PayPal experienced a brief degradation in its Production environment impacting Online Checkout and Retail Checkout services, with Braintree noted in the incident. The issue began at 4:48 PM UTC and was resolved by 5:18 PM UTC, lasting about 30 minutes and affecting users globally. PayPal's status page provided two updates as engineers worked to restore services.

An outage disrupted PayPal sign-in due to two-factor authentication issues, blocking access to PayPal accounts via web and mobile apps. Users reported problems with the 2FA flow, including a blank authentication window and general sign-in failures, across multiple regions. The incident began at 11:58 AM UTC and was resolved by 12:23 PM UTC, lasting about 25 minutes. The event appeared to affect the PayPal sign-in workflow and 2FA authentication for both consumer and merchant access.

StatusGator detected the issue at Jun 18, 2025 11:58 AM UTC, indicating an early warning ahead of any official PayPal acknowledgment. PayPal's status page did not publish updates during the incident, and the event involved the sign-in flow and two-factor authentication components, with users reporting login problems across multiple regions.

PayPal reported a system issue impacting Venmo in production with global reach. The incident began at 5:48 PM UTC and Venmo was listed as degraded (warn). Technical teams worked to restore services and Venmo returned to normal by 6:58 PM UTC. The outage lasted roughly 1 hour and 10 minutes. PayPal issued two status updates during the incident detailing the impact and progress toward resolution, with Venmo returning to full operation by the end of the incident.

PayPal's Chargehound integration in PayPal Production experienced an intermittent disruption that affected users globally. Affected Regions: Global. The outage led to checkout and payment flow issues, login challenges, and related errors for users across the globe. The incident began at Jun 10, 2025 4:33 PM UTC and was resolved by Jun 11, 2025 7:03 AM UTC, lasting about 14 hours and 30 minutes. The Chargehound component moved from normal to degraded status during the incident and returned to normal after the issue was resolved. PayPal's status page issued an initial notification and a follow-up update as the vendor worked to resolve the disruption, with two official status updates issued in total.

The PayPal Production environment experienced a global issue on Jun 2, 2025 5:58 PM UTC, impacting multiple products. Users reported login problems, pages not loading (including checkout flows), and Payflow API calls failing, indicating a broad impact across PayPal accounts, Venmo, Payflow, Xoom, and Enterprise Solutions (Braintree). Global regions were affected as PayPal’s technical teams investigated and worked toward a fix.

PayPal issued four status updates during the incident. The first alert came at Jun 2, 2025 5:58 PM UTC with further updates at Jun 2, 2025 6:18 PM UTC and Jun 2, 2025 6:53 PM UTC. Mitigation was observed by Jun 2, 2025 6:33 PM UTC, and a final update at Jun 2, 2025 7:49 PM UTC confirmed recovery. The outage lasted roughly 1 hour and 51 minutes, with affected components including Account, Venmo, Payflow, Payflow APIs, Xoom, and Enterprise Solutions (Braintree).

PayPal reported a global issue on the PayPal and Braintree platform, with Online Checkout and Retail Checkout experiencing degraded performance. Users attempting to complete purchases may have encountered slower checkout experiences or intermittent failures during the outage window. The disruption affected both checkout channels and likely impacted transaction flows across regions.

PayPal's Payflow settlement processing on the FISERV North platform experienced an outage that delayed settlement files and caused funding to be posted one day late. The issue affected Payflow and Payflow Processors in North America. The outage began on May 2, 2025 4:28 PM UTC and persisted through May 16, 2025 11:28 PM UTC, spanning roughly 14 days and 7 hours.