PayPal Outage History

The PayPal production environment experienced a global issue impacting Webhooks and Notifications, with APAC Braintree Transaction Processing also affected. Customers encountered issues with payments and related workflows, including service unavailability messages and pages failing to load in some cases. The incident affected two primary components: Webhooks/Notifications (global) and APAC Braintree Transaction Processing, and was observed across multiple regions.

Timeline and response: The outage began on Feb 18, 2026 2:28 PM UTC. PayPal issued four official status updates during the event. A partial recovery for Webhooks/Notifications was observed by 11:58 PM UTC, with ongoing mitigations and improvements. The issue progressed to full restoration by 5:08 PM UTC. The incident lasted roughly 1 day, 2 hours, and 40 minutes, with user reports spanning multiple regions including the United States, United Kingdom, Australia, and South Africa indicating broad though incomplete availability during the event.

A brief outage impacted Venmo Crypto services, Venmo Credit Card, and Venmo QRC open-wallet in production, primarily in North America. The incident began with an initial notification at 3:28 AM UTC and lasted about 26 minutes, with services restored by 3:54 AM UTC. PayPal issued two status updates during the incident as engineers worked to resolve the issue, and the affected Venmo components returned to normal after the incident.

PayPal's Partner Reporting service experienced a partial outage that affected TZ6 accounts in APAC, potentially delaying or preventing generation of partner reports. The Reporting component was degraded during the incident, and some users may have been unable to access or generate partner reports while the issue persisted. The outage began with an initial notification at 5:13 AM UTC and then moved to a degraded state at 5:18 AM UTC. The problem was resolved by 2:38 PM UTC, lasting approximately 9 hours and 20 minutes. PayPal posted two status updates during the incident, documenting the progression and resolution.

PayPal reported a disruption in payment tokenization that affected PayPal Production and Braintree environments in North America, potentially impacting checkout tokenization and payment flows. The incident began at Jan 19, 2026 12:38 PM UTC and was resolved by Jan 19, 2026 2:08 PM UTC, lasting about 1 hour 30 minutes. The PayPal Homepage component was among the affected areas, and PayPal issued 2 status updates during the incident.

The PayPal Venmo ecosystem experienced a brief outage in the production environment, impacting Venmo, Venmo Debit Card, and Checkout Pay with Venmo in North America. Users attempting Venmo payments or related features may have encountered errors or intermittent failures. The incident was acknowledged at Jan 14, 2026 3:23 AM UTC and involved two Venmo-related components that went from operating normally to degraded before returning to normal. The outage lasted about 2 hours and 10 minutes, with full recovery by Jan 14, 2026 5:33 AM UTC. The provider issued 2 official status updates during the incident.

The PayPal Payments service in the APAC region experienced transaction errors and disrupted checkout flows due to an external AU processor issue. The incident began at 11:58 PM UTC and affected payments, with two PayPal REST API endpoints (Refunds and Captures) listed as degraded while engineers coordinated with partners to resolve the issue.

APAC was the primary impact region. The issue was resolved by 4:53 AM UTC after approximately 4 hours and 55 minutes, with PayPal publishing two status updates during the incident and the affected components returning to normal operation.

PayPal reported a production system issue affecting Venmo, degrading multiple Venmo functionalities in North America, including Venmo / Checkout Pay with Venmo. The incident began with an initial notification at 12:35 AM UTC and a follow-up at 12:38 AM UTC outlining the impact while engineers investigated. The provider issued two official updates during the incident and worked to mitigate the disruption. By 4:38 AM UTC, Venmo had been restored and PayPal noted the issue was resolved, with the Venmo component returning to normal operation. The outage lasted roughly four hours, and users in North America experienced difficulties with sign-in and making payments.

PayPal reported a global issue affecting PayPal Partner Reporting for TZ7 London timezone accounts, impacting PYT - Payouts Reconciliation Report, FRD - Financial Detail Report, MCR - Marketplaces case reconciliation report, PF - Partner Fee report, and PSR - Partner Settlement Report. Users attempting to generate these partner reports could have experienced delays or failures. The incident affected the Reporting component, with an initial notification posted at Nov 29, 2025 9:34 AM UTC and ongoing updates as PayPal worked to restore the reports.

The outage began at Nov 29, 2025 9:38 AM UTC and was resolved by Nov 29, 2025 10:43 AM UTC, lasting about 1 hour 5 minutes. The provider issued 2 status updates during the incident, moving the status from up to warn and then back to up as work progressed. The impact was global but tied to TZ7 London timezone accounts and affected multiple partner reporting reports.

PayPal Credit in the Production environment experienced a brief disruption impacting North America. Users may have encountered checkout or payment issues during the incident window, with the PayPal Homepage listed as impacted. A small number of user reports began around 7:00 AM UTC.

PayPal reported a reporting issue affecting Merchant Reporting and Partner Reporting for TZ5 (Pacific Timezone) accounts in North America. Users experienced missing data in merchant and partner reports and related errors when accessing PayPal reporting dashboards. The incident began at Nov 2, 2025 5:28 PM UTC and was resolved by Nov 2, 2025 10:23 PM UTC, lasting approximately 5 hours and 55 minutes. PayPal issued two official status updates during the incident, first noting the impact and then confirming restoration of reporting data.

The problem was confined to the Reporting component and primarily affected TZ5 Pacific Timezone reporting, with a regional focus in North America. The user reports during the period showed data gaps and error messages across multiple locations, indicating degraded but not universal access to reporting data in the affected region.