@balancedstatus

status updates for Balanced

 San Francisco, CA
status.balancedpayments.com
Joined May 2012
  • Tweets253
  • Following2
  • Followers84
API-UP: The issue should now be fixed.
API-ISSUE: There are some intermittent issues causing errors in the API. We've identified the issue and working on a fix.
API-UP: The issue was caused by the leap second and is now resolves. Thank you for your patience!
API-ISSUE: There were intermittent issues for refunds since midnight (UTC) on July 1.
API-ISSUES: There are intermittent issues with creating refunds. We're investigating now.
API-UP: We're back and are continuing to monitor.
API-ISSUES: We're experiencing some intermittent issues and working on resolving.
API-UP: Everything is resolved.
API-ISSUE: We're seeing some calls to the API timing out. Investigating
API-UP: A redis node stopped responding in a timely manner which resulted in requests being queued up and processed slowly.
API-DOWN: We're seeing increased latency for some requests via the API
API-UP: The root cause of the problem was traced to a communication issue outside of the Balanced network. Resolved 2 hours ago, monitoring.
API-ISSUE: We're seeing some intermittent network connectivity issues that we're investigating.
API-UP: A redis cluster appeared to experience network latency. The slowness has gone, we will continue to investigate the root cause.
API-ISSUE: We're seeing slow response times from the Balanced API
DASH-UP: We're processing through a larger than average backlog of history. History is expected to be caught up within the hour.
We've released a post-mortem following a partial outage this morning. You can read the details at gist.github.com/mjallday/f07…

Balanced Partial Outage Post Mortem - 2015-03-15

Balanced Partial Outage Post Mortem - 2015-03-15. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com
1
1
API-UP: Everything is A-OK now.
API-ISSUE: We are seeing some slowness in our backend and are investigating now.
API-UP: Everything is A-OK now.
Load more