Server Antwortzeiten 27.2.24 schlecht

[Nick Carthew]

@Hubert-Thoring Sometimes you just need to be a little patient. Tagging Corjan in every post does not help solve your problem any quicker. This is a community forum not a personal hotline to the developers. We are incredibly lucky that Corjan finds the time to occasionally answer some of our questions.

[Hubert Thoring]

@Nick-Carthew : wer ist denn verantwortlich für den Server und dessen Verfügbarkeiten …

Bitte sagt mal, gibt es denn einen Grund dafür das die Webseite jetzt mehrmals nicht direkt zur Verfügung stand, war in der Vergangenheit nicht so, ich denke mit Beginn der Saison wird noch sehr viel mehr drauf zugegriffen.

Zum Beispiel „Morgens direkt vor einer Tour“ wäre eine nicht Verfügbarkeit sehr verwirrend und gäbe sicherlich kaum Begeisterung.

VG aus dem Münsterland

[Nick Carthew]

@Hubert-Thoring The forum is owned and maintained by a third party. MRA have no direct control of the forum. The 503 message shows that there was a temporary problem.

[Drabslab]

@Nick-Carthew said in Server Antwortzeiten 27.2.24 schlecht:

The forum is owned and maintained by a third party.

that is no excuse for poor quality that reflects on MRA as a company

MRA have no direct control of the forum.

which sounds very sad for an IT oriented company.
and I hear the same about the battery issue, MRA can't control HERE which is true but also in this case it devalues the products of MRA.

The 503 message shows t HD at there was a temporary problem

the 503 meassage appears very regularly. I got such a 503 message several times the past weeks. and clearly this is not because of the massive amount of traffic on the forum.

[Jack van Tilburg]

@Nick-Carthew said in Server Antwortzeiten 27.2.24 schlecht:

The forum is owned and maintained by a third party

Technically I hope. And for a fee with agreed availability. So a comment about this on the forum helps MRA to provide the supplier with the agreed service.
Not the content I'm sure

[Nick Carthew]

@Drabslab @Jack-van-Tilburg I too have encountered the 503 message but in my experience it is very temporary and normally when I try to connect the second time the forum opens.
The developers time is very precious and I think that their time is better spent on developing the app and rather than chasing a temporary issue with the forum. Of course, if the issue was to develop into a more regular problem then we would expect MRA to intervene.

[Jack van Tilburg]

@Nick-Carthew
If I understand correctly, there are two developers in the MRA organization, but there are more employees.
If no attention can be paid to matters other than the development of the App, I will be seriously concerned.
And I didn't recommend contacting the developers in my response.

[Drabslab]

@Nick-Carthew

This has nothing to do with the two MRA developers that are hopefully NOT involved in running this forum, I hope that other people in MRA are responsible for this.

This 503 message signals a shortcoming and like any other issue it should not be belittled (it is only temporary) but solved.

Remind that it is very visible for any user (including those who do not consider themselves hard core fans) and it needs to be adddressed urgently.

[RetiredWingMan]

I have only seen the 503 error message a couple of times and hitting retry always fixed it. I think people need to cool down and relax a bit. What's wrong with assuming it's being investigated and resolved in due course. Get on with live.

[Jack van Tilburg]

@RetiredWingMan said in Server Antwortzeiten 27.2.24 schlecht:

Get on with live.

involvement should not be patronized

[Jack van Tilburg]

To be honest, I am increasingly bothered by the increasingly common "503" message.