All Systems Operational

About This Site

Braintree Status

API
Control Panel
Sandbox
United States Processing
Canadian Processing
European Processing
Australian Processing
Past Incidents
Apr 23, 2014
Resolved - This incident has been resolved.
Apr 23, 11:26 UTC
Update - The datacenter hosting our legacy gateway platform ("Orange") is currently performing maintenance to address the ongoing issues from yesterday and today. Elevated processing issues relative to the current baseline for a subset of merchants using our legacy gateway platform are expected until 4AM Central time.
Apr 23, 05:56 UTC
Monitoring - We've identified an upstream networking issue that affects a small subset of our merchants using our legacy gateway platform (Orange). Affected merchants will have difficulty connecting to our legacy API and Control Panel during this time.
Apr 22, 13:56 UTC
Completed - The scheduled maintenance has been completed.
Apr 23, 06:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 23, 02:00 UTC
Scheduled - AIB recently made us aware that one of their partners is performing emergency maintenance on a upstream core networking switch tomorrow morning on Wednesday 23rd April 2014 between 02:00am and 06:00am GMT. During this time, you may experience issues processing transactions successfully for a total of 20 minutes during the specified window of 02:00hrs to 06:00hrs. AIB has noted that retries of any failed transactions during that period will be successful after the maintenance window.
Apr 22, 22:04 UTC
Apr 22, 2014
Resolved - This incident has been resolved.
Apr 22, 18:44 UTC
Identified - The issue has been identified, and we are working with our upstream providers.
Apr 22, 16:16 UTC
Investigating - An issue upstream of our gateway is causing some transactions on the Adyen network to fail. Transactions that fail may return a response code of 3000 (Processor Network Unavailable).

Scope: This issue will only affect US merchants on the Adyen network. The Braintree gateway is currently up and accepting requests at this time.
Apr 22, 16:16 UTC
Resolved - This incident has been resolved.
Apr 22, 00:38 UTC
Identified - An issue upstream of our gateway is causing some transactions on the AmEx Direct network to fail. Transactions that fail may return a response code of 3000 (Processor Network Unavailable).

Scope: This issue will only affect merchants on the AmEx Direct network. The Braintree gateway is currently up and accepting requests at this time.
Apr 21, 21:54 UTC
Apr 20, 2014

No incidents reported.

Apr 19, 2014
Resolved - An issue upstream of our gateway caused transactions processed via Orange from 10:28-13:04 UTC to fail with a processor response code of "3000 - Processor network unavailable - Try again."
Apr 19, 13:23 UTC
Monitoring - We are currently seeing issues with one of our U.S. processors (Orange). During this time requests for merchants using this processor will return with a response code of "3000 - Processor network unavailable - Try again." All other services and the majority of U.S. processing is unaffected.
Apr 19, 11:10 UTC
Apr 18, 2014

No incidents reported.

Apr 17, 2014
Resolved - A subset of American Express transactions across multiple processors failed with a response code of 3000 (Processor Network Unavailable) between 03:30 - 04:05 UTC.
Apr 17, 05:21 UTC
Investigating - We are investigating intermittent issues processing transactions for American Express cards across multiple processors.
Apr 17, 04:46 UTC
Apr 16, 2014
Merchants running transactions with vaulted cards in a specific case may find that the transaction failed due to AVS/CVV validation errors. The cause has been identified and fixed.
Apr 16, 19:36 UTC
Apr 15, 2014

No incidents reported.

Apr 14, 2014

No incidents reported.

Apr 13, 2014

No incidents reported.

Apr 12, 2014

No incidents reported.

Apr 11, 2014
Merchants processing with Adyen would have encountered failing requests when trying to download settlement details reports from 8:08 UTC to 10:39 UTC. These errors were caused by a SSL certificate rotation that caused SSL verification to incorrectly fail.
Apr 11, 17:42 UTC
Apr 10, 2014

No incidents reported.

Apr 9, 2014

No incidents reported.