<![CDATA[can we please fix this first?]]>the infamous ''this feature is unavailable'' error still heavily affects switch users, dates are still messed up, and the lag on chat makes it very hard to use (though that last one might just be a me problem) and i know we're focusing our efforts on growing our site and advertising it to others, but might we try to fix these issues first? image if a bunch of new switch users were just about to join and they got that error, didn't know it was temporary (for me it usually lasts roughly 10 hours) and thought it was a scam or something and didn't use it again. i know @VgMoose is a busy man, but i just kinda wanted to make this point as its very annoying to get this error and miss a meeting because of it and stuff like that.

]]>https://browsedns.net/topic/15666/can-we-please-fix-this-firstRSS for NodeSat, 02 May 2026 16:15:46 GMTTue, 03 Feb 2026 08:46:24 GMT60<![CDATA[Reply to can we please fix this first? on Wed, 04 Feb 2026 00:37:25 GMT]]>@VGMoose ok

]]>https://browsedns.net/post/177781https://browsedns.net/post/177781Wed, 04 Feb 2026 00:37:25 GMT<![CDATA[Reply to can we please fix this first? on Tue, 03 Feb 2026 23:20:14 GMT]]>If you do try changing the time, I also suggest trying to change the timezone, as the Switch always keeps track of "true network time".

]]>https://browsedns.net/post/177701https://browsedns.net/post/177701Tue, 03 Feb 2026 23:20:14 GMT<![CDATA[Reply to can we please fix this first? on Tue, 03 Feb 2026 22:07:41 GMT]]>this error has pervented me from continuing my sfw yaoi called bloxed bc i get eepy and go to be b4 the browser comes back >:c

]]>https://browsedns.net/post/177683https://browsedns.net/post/177683Tue, 03 Feb 2026 22:07:41 GMT<![CDATA[Reply to can we please fix this first? on Tue, 03 Feb 2026 22:01:21 GMT]]>@VGMoose ok, i'll personally start keeping a log, i do wonder if it might be an issue of too many users on dns but i tried the uk dns for example that doesn't usually have a lot of users but still got the exact same thing. i Can't acces it for about 10 hours each time so i wonder if it's timed like the twenty minute browser time-out Is. its been an issue for me for months and it usually seems to happen during the day, but in the wee hours of the morning seem to never get this to happen. i don't think changing my switches time will help but i might try it out

]]>https://browsedns.net/post/177680https://browsedns.net/post/177680Tue, 03 Feb 2026 22:01:21 GMT<![CDATA[Reply to can we please fix this first? on Tue, 03 Feb 2026 18:10:52 GMT]]>As far as I know, this is some kind of recent (new-ish as of the Switch 2) check that blocks out the browser. I have had it appear before, but not often.

If you could start keeping a log of when it happens, that might be helpful to figuring out how it works. The DNS service was ran for a few years before even realizing the browser timeout was exactly 20 minutes, just due to a lack of research.

In theory, the "Feature is not available" notice is similar to what the console says when the browser is outdated, or hasn't been online regularly (as in, connects to Nintendo's servers) in a while. That's why I typically recommend trying to connect normally, using Google DNS, or updating.

If it's always happening around the same time, that might even point to a "quiet hours" kind of functionality, but I think that would be unlikely. The intended purpose of the Switch browser is to allow the user to connect to the Internet after all. If you have access to a PC, it'd be interesting to see if CaptiveDNS works during the timeout: https://github.com/browseDNS/CaptiveDNS

]]>https://browsedns.net/post/177625https://browsedns.net/post/177625Tue, 03 Feb 2026 18:10:52 GMT<![CDATA[Reply to can we please fix this first? on Tue, 03 Feb 2026 08:48:17 GMT]]>i have updated my switch, tried different dns's, restarting it ect and none of that works

]]>https://browsedns.net/post/177545https://browsedns.net/post/177545Tue, 03 Feb 2026 08:48:17 GMT