Profile_bird

Hey there! usaepay is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving usaepay's tweets.

Already using Twitter
from your phone? Click here.

usaepay

  1. The majority of issues affecting merchant custom reports should now be fixed. Please contact support if you are still experiencing trouble. 11:44 AM Dec 17th from web
  2. Logging issues with merchant custom reports. ETA of 1 hour for a fix 9:40 AM Dec 17th from mobile web
  3. Traffic routed back to primary dc. Telco resolution: packet loss attributed to socal fiber cut caused by "squirrel damage". 3:52 PM Nov 22nd from web
  4. Issue has been escalated to upstream telco. Routing to backup datacenter will remain in effect while testing takes place. 3:12 PM Nov 22nd from web
  5. Intermittent internet connectivity issues in primary datacenter. Traffic routed to backup while we research the issue. 2:58 PM Nov 22nd from web
  6. Currently experiencing lag issue with auto batch closures. Expect to have the system back up to speed in 30m. 7:13 AM Nov 19th from web
  7. 9m outage in primary server pool at 2:32am PST. Merchants may have received "Server temporarily unavailable." Issue has been resolved. 1:50 AM Oct 26th from web
  8. New ssl cert for www.usaepay.com in production from now until 11pm PST. Please report any issues with new cert to devsupport@usaepay.com 8:29 PM Oct 4th from web
  9. SSL Cert for www.usaepay.com will expire on Oct 10th. Please see http://bit.ly/UXLL8 for more info on testing your app with the new cert. 4:55 PM Sep 25th from TweetDeck
  10. Network issues at backup datacenter resolved. www-02.usaepay.com back online 2:16 PM Sep 25th from web
  11. Network issues reported on backup datacenter (www-02.usaepay.com) Primary datacenter unaffected. 12:12 PM Sep 25th from TweetDeck
  12. FDMS circuit in LA has been repaired and tested clean for 12 hours, adding back into the pool. 9:07 AM Sep 10th from web
  13. Lost connectivity to FDMS from LA at 10:24. Only customers in middle of processing where affected. No processing impact for all others. 11:03 AM Sep 9th from web
  14. We are currently experiencing issues with our FDMS backend links in LA. Traffic has been routed through alternate DC while we troubleshoot. 10:57 AM Sep 9th from web
  15. Need to integrate using Java & Netbeans? Here's a how to: http://tinyurl.com/kv2p9k 5:42 PM Aug 25th from web
  16. Network stability testing complete, routing traffic back to primary DC scheduled for 3:00pm PST 2:31 PM Aug 17th from web
  17. Faulty wiring in telco nap replaced, primary DC back online. Traffic will route to the backup DC until connection testing complete 2:08 PM Aug 17th from web
  18. Currently still troubleshooting networking issues in primary DC. No ETA from upstream telco yet. Traffic will continue to route to backup. 12:35 PM Aug 17th from web
  19. @mattsilv Yes we will 12:32 PM Aug 17th from web in reply to mattsilv
  20. use http://www-02.usaepay.com/ to access secondary DC directly 10:52 AM Aug 17th from web
0 Following 66 Followers 3 Listed