I’m also getting the exact same issue as of a few hours ago.
The message will not disappear.
Edit:
Seems to have fixed its self for me.
Same here
1 Like
I’ve had this issue since Friday evening. I need my wiki references, it’s even broken in the content tab in studio. Does anyone know what’s going on?
1 Like
I’ve noticed that I can access it at school via all my devices, but not at home. Weird… any ROBLOX staff that could help?
We are looking into it.
1 Like
It looks like the DOSArrest service you’re using is blocking Akamai. As some of the previous screenshots and reports have shown, the IP address displayed on the page is not actually the IP address of the person requesting the wiki pages, it is in fact, an IP address which belongs to Akamai.
Looking at my DNS results and other data, it seems that the chain is User => Akamai => Actual wiki server. Where akamai in this case is blocked.
I’d just like to note that having both Akamai and DOSArrest guarding the way to the wiki seems a bit odd to me. Not only because Akamai offers both caching services and DDoS protection, as DOSArrest provides those services too.
Alright we think we found the issue. Let us know if you are still encountering this.
6 Likes
The wiki works properly again. For anyone still getting the 403 page, clearing the cookies for wiki.roblox.com seems to fix it.
1 Like
This is currently happening to me again, clearing cookies did nothing.
It is really hindering me in looking up a ton of API info. Is this a unique issue for certain IP-ranges or anything?
I also have been experiencing this error for some days now and its really starting to annoy me. I also had this problem back in November.
Same problem here - however, it seemed to work briefly earlier today (after being unavailable), but is now back to throwing 403 errors.
Just started occurring again for me.
Marked as unsolved. I’ve tagged the intern that worked on this before but that hasn’t helped
1 Like
Same here
1 Like
Refreshing a few times has worked for me, but I sure do get this sometimes.
I’m getting it too. A simple refresh fixes it, but with each link to another page, I get this error again
1 Like
A refresh doesn’t fix it for me, I keep getting it even tried other devices like my phone but I also get it on there.
4 Likes