Board Thread:General Discussion/@comment-32944249-20171115215205/@comment-31661832-20171115233041

NebRanger wrote: Actually, chance is probably higher than that.

It's still possible to overload a load balancer (and, therefore, the servers behind it) and cause it to spit out garbage data. It could also be data loss coming down the pipes. Like a lot of apps, responses are probably served as a JSON array, which makes it easy for the receiving end to filter out bad data. What likely happened is that some parts of the response got corrupted somewhere, and overwrote earlier versions of the pool table in memory. The app then noticed this and chucked only the bad data, keeping the overall still valid current version.

This is pretty easy to implement, and a lot of apps, regardless of platform, do actually ignore bad response data. Considering their server likely has data for multiple banners (possibly even the older ones lying around), and each banner can have hundreds of entries, the memory issue could be with whatever program they use to manage those lists. That's way too many entries to put in a database by hand, so whatever tool they made to likely help designers input available characters and rates may have had the bug.

Or, the app itself may have been messing up it's requests to the server, and thus receiving incorrect data.

I doubt it's packet loss. It would've been an issue before now if that was the case.