3 ms·
Seems to me that a routing / networking issue would have been resolved by now, and application bug would have been rolled back. If I were to speculate, I would
by stingraycharles 5y ago
Seems to me that a routing / networking issue would have been resolved by now, and application bug would have been rolled back.
If I were to speculate, I would say that it must have something to do with databases / storage. Something must have gone wrong and broke some database, and it’s difficult to restore.
- intunderflow 5y agoThey had an incident in the past where they returned nil for all get operations to their database, that caused some chaos at the time so it's not unprecedented: https://devforum.roblox.com/t/update-datastores-incident-data-consistency-checker-api/832679 https://devforum.roblox.com/t/update-datastores-incident-dat...
- polack 5y agoI agree that DB is the prime suspect here. They said the problem was identified over 24h ago, cant imagine it being something other than a data issue that takes that long to resolve.