Still long carrier jump times on Saturday, Aug 8. First time was 54 minutes. Canceled and tried again and it's 1 hour and 4 minutes.
Regardless of whether there is some bug or not; what you describe here is literally getting out of line in a queue and then being surprised that you have to go to the back of the line. I have no idea why anyone would think cancelling and trying again would do anything positive. For the sake of the server, please stop doing this.
At this point, with all the people in this thread saying they keep cancelling and trying again to get a better spot, I'm like 75% sure the problem is people that don't understand a queue are accidentally DDoS'ing the FC server by constantly cancelling and rescheduling.
I just think it's odd that this doesn't affect me almost at all, and the main difference is that I play at least populated global time slot. Like, if you look at steamcharts for Elite, just to get an idea of peak times and such, I usually log on right before it bottoms out, and log off as soon as it starts to pick up again, Midnight to 4-5am Central US time. That seems to me to
prove that the queue is working as intended, but there is too much traffic during peak hours.(or apparently, anytime that isn't "dead" hours)
BUT, it could be possible, however conspiratorial or unlikely, that Frontier "downgraded" to a cheaper server for processing FC jumps, as
@yianniv postulated.
Only other "bug" I can think of is that the number of simultaneous jumps the server is allowed to process before activating the queue was erroneously lowered, ie. 256 to 8. (I have no idea what the real number is, I don't believe it's been stated) But you think that would be obvious and would have been fixed by now if that was the case.
Also, I don't think it's "White Knight-ing" to try and educate people who seem to be unaware of what a queue is or how it works. Like, stop cancelling and rescheduling, it's insanity to think that will do anything but further bog down the server. The only thing new about this, is that it has indeed lasted longer than previous Update slowdowns, which is why FDev are looking into it. Just don't be surprised when their "fix" is to raise the jump timer to 30 minutes with a 15 minute cancellation cooldown.