WHY ROBLOX WHY, I WAS GOING TO RELEASE IT TODAY!!! What should I do now? 
Oh and [spoiler]
[/spoiler]
EDIT: Datastore seems to be coming back but very slowly due to the long wait to authenticate the server. The problem occurs with the loadfile(“”)(“”, -1, 0) in http://www.roblox.com/game/join.ashx (line 426)
What’s the game?
Rocket Royale it’s about to rekt first page. 
Reason 2 Die is also experiencing the same problem.
Very very very slow for me. Still seems to work though, but it takes 15s to fetch a small table. Although the flow of dislikes suggest something is terribly wrong. 
Mine is slower than usual but is working.
cri
If DS has issues I might as well start using DP again (it’s easier to use anyway)
[quote] cri
If DS has issues I might as well start using DP again (it’s easier to use anyway) [/quote]
Whatever issues may be going on, they are definitely not permanent. Plan on continuing to use data stores instead of data persistence.
The DP issue wasn’t permanent either.
tbh, I think having to do all of these work-arounds for the DS is ridiculous. If I want to store data, I’m going to store it – I don’t need some data limit per key making me use separate keys for things like reasons someone got kicked. The DS needs to be reworked on how it’s set up, because it was obviously left unfinished.
I like DP more than DS, so I will continue to use DP
[quote] The DP issue wasn’t permanent either.
tbh, I think having to do all of these work-arounds for the DS is ridiculous. If I want to store data, I’m going to store it – I don’t need some data limit per key making me use separate keys for things like reasons someone got kicked. The DS needs to be reworked on how it’s set up, because it was obviously left unfinished. [/quote]
No real world scenario would give you infinite access to your databases. It is fairly easy to use DS and not overdo the limit. The limit is there so we don’t destroy Roblox’s database with thousands of unnecessary queries.
Also, the DS system doesn’t need reworked? It does exactly what it needs to do in a logical, straight-forward way. Using keys to store information in a sectionalized database makes perfect sense.
Other than the service unavailable error that seems to happen every now and then, DS does it’s job pretty well…
@OP
This showed up in my Google Analytics: https://api.roblox.com/persistence/getV2?placeId=152166169&type=standard&scope=global: WinHttpReceiveResponse, err=0x2EE2 | ServerScriptService.PlayerDataScript, line 37
I must say that DS should be 100% online. Or when the issue exist, that it should be fixes asap
Well, if/when a server shuts down, your players can say goodbye to their Data.
DP is definitely poor practice to use now for new projects.
I am not very satisfied with DS uptime and the service unavailable stuff… 
I use both DP and DS to be safe.
Do you still see the issue?
We had some availability problems with Amazon DynamoDB (storage behind datastores), but they’re resolved now.
[quote] Do you still see the issue?
We had some availability problems with Amazon DynamoDB (storage behind datastores), but they’re resolved now. [/quote]
Simon, do you have backups of DataStores ? Since it seems that DataStores have this kind of behavoir quite often.
Stahp it you’re scaring me
