503 error at forum
-
@flypg
I saw this, too… just reload or wait some seconds. Never saw it twice -
@TELE-HO Thanks, yes, I´m not alone
-
Keep me posted. I checked we are not out of capacity. So wierd
-
@flypg yes i got this too. But not often. A few minutes later it has worked again.
-
@mario_b yes, exactly, is not a permanent behavior. Is some random behavior that sure reflect the load at the server on this moment.
@Dimitrios-Kanellopoulos The most strange is that one of the times that happen to me too frequently to me was yesterday around 4 AM (GMT 0) that I can imagine that on this time not existed heavy load on the server by the users. -
Saw it also a couple of time, just reload the page and it was gone.
-
Same here. Instant reload usually solves it. Weird…
-
Thanks to everyone for the answers. Yes, I know that the 503 is solved with some refresh, because sometimes is only a puntual load peak. More that all was to know if this happen too frequently and to everyone. Have all a great weekend!
-
@flypg good that you wrote it. Maybee some mods did’nt know about it before.
-
Is it me or are those 503 errors more frequent lately? Also the forum suffers from lag once in a while.
-
@surfboomerang said in 503 error at forum:
Is it me or are those 503 errors more frequent lately? Also the forum suffers from lag once in a while.
I have the same frequently for weeks, but most of the time, a single refresh and there it goes again.
-
@surfboomerang
same for me, error sometimes, but mainly forum loading is quite long.
too many users now ? -
@Mff73
@surfboomerang
same here. noticed the slower loading already a while back and it was obvious that with the release of the Suunto Race the 503 error happens significantly more often. I can only guess that we have much more visitors since the Race release@Tieutieu
sometimes I need to refresh multiple times. this wasn’t the case in the past
-
Had this error several times in the last two weeks…
-
I’d be glad to provide (professional) sysadmin services to Suunto to solve this issue
-
A bit late here. 503 is over capacity. We are on a Planx and this can happen sometimes combined with high traffic and bots trying to access this.