Things can happen for a variety of factors

[4Rsercom]

The weekly battle pass Challenges go every Tuesday in the early morning Eastern Time: when there is no server downtime, they appear at 4:00 a.m.. If there's downtime for a new update, developer Epic Games announces it daily before and it starts at 4:00 a.m., using the new content and challenges going live once the downtime is completed. There is even a little countdown on the battle page which suggests as much. For Week 5, but there appears to be some thing wrong.

If you go to inspect the Week 5 challenges in Fortnite materials at this time, all you see is a little message that says"unlocks in 0 minutes" with seven vacant spots below it, just like for any weeks to which the challenges have yet to unlock. It's been like that because 4:00 a.m.. At the time of the writing, that means the challenges have been stuck in this limbo for nearly an hour.

There doesn't appear to be anything else wrong with the match: I loaded up a game and fell in no problem.

First off, it is important to not fear: games are large, unwieldy beasts, and odd things can happen for a variety of factors. But in this specific case, things have appeared strange since yesterday. Epic usually declares the new update the day before it goes live, if that upgrade will need downtime or never. Epic's competitive content schedule means that has happened every week for quite a while now, but we didn't hear anything yesterday. What seemed like an oversight today appears somehow connected to whatever is the reason for the Week 5 challenges to hang at 0 seconds.

Again, this type of matter is far from unheard of at games-as-service: weekly content updates are a large job for any developer, and it's not surprising that Fortnite materials could be the occasional hiccup from a programmer with Epic's technical proficiency. The eyes of the world are on Fortnite at the moment, however: it's the present craze, and that includes a degree of scrutiny. We have contacted the programmer for comment and will update with any new information. Hopefully, it's fixed soon.