DataAPI Down Again?

[pftq]

Looks like queries to Ripple's Data API (including XRPCharts) are not working again:

https://xrpcharts.ripple.com/#/markets/XRP/USD:rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B?interval=5m&range=1d&type=line

 

[jargoman]

Same problem. And also orders entered into gatehub being left in limbo where they may or may not been submitted successfully. 

[Coinseeker]

This problem has literally been going on for years. Charts and wallets.  What is the technical answer in how to solve this?  What's causing it? 

[Roborovskii]

23 minutes ago, Coinseeker said:

This problem has literally been going on for years. Charts and wallets.  What is the technical answer in how to solve this?  What's causing it? 

Not years. Only recently after the major uptick in price. Perhaps DDOS on the public APIs and charts. 

"First they ignore you, then they laugh at you, then they fight you, then you win."

[Coinseeker]

6 minutes ago, Roborovskii said:

Not years. Only recently after the major uptick in price. Perhaps DDOS on the public APIs and charts. 

"First they ignore you, then they laugh at you, then they fight you, then you win."

As long as I've been using Ripple...pretty much since the beginning, the wallet always had this connection issue.  It was really bad at first but even now, failed payments and unable to submit or cancel orders, are still a regular occurrence.  I hear if you run your own instance, it will solve the issue.  I'd still like to know what that issue is and how running one's own instance solves it.

Edited June 11, 2017 by Coinseeker

[Roborovskii]

15 minutes ago, Coinseeker said:

As long as I've been using Ripple...pretty much since the beginning, the wallet always had this connection issue.  It was really bad at first but even now, failed payments and unable to submit or cancel orders, are still a regular occurrence.  I hear if you run your own instance, it will solve the issue.  I'd still like to know what that issue is and how running one's own instance solves it.

Some questions to clarify, with no offense intended - When is "the beginning"? Since you're registered here only on May 20th 2017, which does not match up to "for years".

Running your own Rippled basically bypasses the issues faced at the public Rippled servers, and connects you directly to RCL. So yea the public APIs are the issue, not RCL.

What the issue is remains unknown to us, but likely known to Ripple. I am guessing if it is really DDOS, then they are working on it from the technical and legal perspective. Ripple has the strategy of not making information public as they work in the background, only to make official announcements when the time is right.

**Add**  If you are looking for a work around, Gatehub seems to have improved alot regarding this issue. Their orderbooks depth is much better now too.

Edited June 11, 2017 by Roborovskii
Additional Gatehub info

[Coinseeker]

Thank you.  Makes sense on the public API's.  Given rippled is open-source, shouldn't there be a way to go in and correct this issue or am I not understanding API's.  The reason I ask, is if I wanted someone to download the "public" wallet, how can we make it as stable as running one's own instance.  I don't mind doing such, but I realize this isn't feasible for most.

BTW-This forum wasn't around in the beginning, so I've been around at least long enough to know that checking the register date wouldn't confirm such for anyone registered here.   

 

Edited June 11, 2017 by Coinseeker