Frontiers Servers down?

replicate-prediction-ws2cbp7bwsrga0ch5s8vztgw00.jpeg
 
...

More likely is that this is an accumulation of whatever has been leading to the large carrier jump times, and the slow hyperspace times. What's particularly interesting from my point of view is that kicked off during a period of low load (i.e. early sunday AM GMT) following what would have probably been peak time (Sat EMEA evening with AMRS afternoon). It's more likely to be something cumulative, like a failure to release memory or to defer a process off thread (maybe the new Power play system summaries?).

Without the code or load information, we are just guessing. It's not clear at all.
Then they were guilty
2024-11-02_20-08-44_HIP_117029_HIP_117029_5.jpg
 
I don't think your assumption is right here, your scenario would lead to connection and disconnection at random (i.e. if you got a connection to AWS or not). It might be a symptom of the problem, but AWS is supposed to scale, you choose what you think is your expected load and get the optimal price at that load, but if need more you just pay more per instance.

More likely is that this is an accumulation of whatever has been leading to the large carrier jump times, and the slow hyperspace times. What's particularly interesting from my point of view is that kicked off during a period of low load (i.e. early sunday AM GMT) following what would have probably been peak time (Sat EMEA evening with AMRS afternoon). It's more likely to be something cumulative, like a failure to release memory or to defer a process off thread (maybe the new Power play system summaries?).

Without the code or load information, we are just guessing. It's not clear at all.

Also, here are the people who really know explaining how it really works

Source: https://www.youtube.com/watch?v=7II4Q0jXeIs
 
Back
Top Bottom