Detected Resolved: Impact to Braintree Apple Pay Tokenization (PP-LIVE-109944)
Detected Resolved: We experienced an outage affecting Apple Pay transactions. Our engineers have resolved the issue, and the impact has been mitigated. Affected Regions: North America
The latest update from PayPal.
State
Resolved
Started
40 d ago
2026-09-23 09:08 UTC
Lasted
3 h 2 min
until 2026-09-23 12:10 UTC
Worst impact
Degraded
Timeline
1 updateResolved
3 h 2 min 100%
Updates
Times in UTCAs posted by PayPal
Detected Resolved: We experienced an outage affecting Apple Pay transactions. Our engineers have resolved the issue, and the impact has been mitigated. Affected Regions: North America
Affected components
2Follow PayPal
Your coding agent knows when PayPal is down, and tells you when a failure is theirs, not yours. You can also get PayPal incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "paypal" and tell me if PayPal has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=paypal/feed subscribe https://outages.cc/feed.xml?providers=paypalFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane