#qsv — Public Fediverse posts

Wenn du noch bei qsv.ch registrierte Domains hast, erhälst du per Post die Zugangsdaten zum Domain-Panel. Dort findest du zu jeder Domain den Auth-Codes für den Transfer. Domain welche bei uns belassen werden, werden nicht mehr verlängert und werden damit von der Registry gelöscht.
#qsv #qsvsupport #qsvstatus
https://qsv.ch

Wir sind dann mal weg … 👋🏻😊

Nach über 15 Jahren Geschäftstätigkeit hat unsere Firma qsv.ch - Internet-Service am 30.04.2026 die Geschäftstätigkeit und den Betrieb eingestellt.
Was bleibt ist ein grosses „Danke“ an unsere Kunden - an dich: Vielen Dank für dein Vertrauen, ohne dich wäre diese Reise nicht möglich gewesen! Auch nicht zu vergessen sind die vielen entstandenen Kontakte, den Austausch mit Partnern und Kollegen. Vielen Dank!

#qsv #qsvsupport #qsvstatus

Wir bewegen uns unaufhaltsam in den letzten Betriebstagen von qsv.ch. Wenn du jetzt noch keine Nachfolgelösung für dein Webhosting hast, ist es höchste Zeit zu handeln! Gerne übernimmt die Codia GmbH dein Webhosting und deine Domains, so bleibst du ohne Unterbruch online. Melde dich über den Support bei uns!
#qsv #qsvsupport #qsvstatus

Für ein notwendiges Sicherheitsupdate muss der Cloud-Server 01 nach der Aktualisierung neu gestartet werden. Beim Neustart entsteht ein Unterbruch von ca. 2 Minuten für alle Dienste..

Wir empfehlen innerhalb des Wartungsfensters keine Arbeiten in Plesk oder in CMS / LMS vorzunehmen.
Vielen Dank für dein Verständnis!

#qsv #qsvstatus #qsvsupport
https://www.qsv.zone/notices/lw7mv7nom3qbcnvw-sicherheitsupdate-und-neustart

Der Hosting-Server wird heute Abend zwischen 23:00 und 00:00 Uhr neu gestartet. Der Server wird für die Wartung wenige Minuten nach dem Neustart nicht erreichbar sein.
Vielen Dank für dein Verständnis!

#qsvstatus #qsv
https://www.qsv.zone/notices/j3wjkh8src0zpaiy-neustart-des-hostingservers

@niccolove @niccolo_ve

Comment on this video (which us not shown on my Fedi instance, yay federation!)

https://tube.kockatoo.org/w/63cGWTvhzqu2bwMGsh3QcF

I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!

Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.

What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).

As OBS can use your GPU for video capture (encoding), the issue is purely in software support.

I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.

For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.

For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.

#MicrosoftSurface #KDENlive #Shotcut #VideoEditing

@niccolove @niccolo_ve

Comment on this video (which us not shown on my Fedi instance, yay federation!)

https://tube.kockatoo.org/w/63cGWTvhzqu2bwMGsh3QcF

I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!

Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.

What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).

As OBS can use your GPU for video capture (encoding), the issue is purely in software support.

I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.

For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.

For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.

#MicrosoftSurface #KDENlive #Shotcut #VideoEditing

@niccolove @niccolo_ve

Comment on this video (which us not shown on my Fedi instance, yay federation!)

https://tube.kockatoo.org/w/63cGWTvhzqu2bwMGsh3QcF

I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!

Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.

What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).

As OBS can use your GPU for video capture (encoding), the issue is purely in software support.

I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.

For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.

For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.

#MicrosoftSurface #KDENlive #Shotcut #VideoEditing

@niccolove @niccolo_ve

Comment on this video (which us not shown on my Fedi instance, yay federation!)

https://tube.kockatoo.org/w/63cGWTvhzqu2bwMGsh3QcF

I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!

Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.

What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).

As OBS can use your GPU for video capture (encoding), the issue is purely in software support.

I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.

For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.

For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.

#MicrosoftSurface #KDENlive #Shotcut #VideoEditing

Derzeit installieren wir bei allen Kundenwebsites mit Wordpress die neusten Updates. Es kann daher zu kurzen Unterbrüchen oder zur kurzzeitigen Anzeige der Plesk-Wartungsseite anstelle der Website kommen.
Vielen Dank für dein Verständnis!

#qsv #qsvsupport #qsvstatus

https://www.qsv.zone/notices/bjximu30rbgges8z-wordpress-update

Wir haben bei allen Kundenwebsites mit Wordpress die neusten Updates eingespielt. Alle Installationen welche im Wordpress-Toolkit verankert sind, laufen nun auf dem aktuellen Softwarestand Wordpress 6.9. Ebenfalls aktualisiert wurden alle Plugins und Themes.

#qsv #qsvstatus #qsvsupport
https://www.qsv.zone/notices/anbtnradrlu5lky0-wordpress-update

Derzeit installieren wir bei allen Kundenwebsites mit Wordpress die neusten Updates. Es kann daher zu kurzen Unterbrüchen oder zur kurzzeitigen Anzeige der Plesk-Wartungsseite anstelle der Website kommen.

#qsv #wordpress #qsvstatus #qsvsupport
https://www.qsv.zone/notices/6a3wg4nsz4sk5b7d-wordpress-update

Derzeit installieren wir bei allen Kundenwebsites mit Wordpress die neusten Updates. Es kann daher zu kurzen Unterbrüchen oder zur kurzzeitigen Anzeige der Plesk-Wartungsseite anstelle der Website kommen.

#qsv #wordpress #qsvstatus #qsvsupport
https://www.qsv.zone/notices/6a3wg4nsz4sk5b7d-wordpress-update

⚒️ 🧰 Wir nehmen die aktuelle Testinstallation cloud-learning.ch am Montag 03,11,2025 ausser Betrieb und erstellen mehrere Anpassungen für die zukünftige produktive Nutzung der Plattform. Dabei werden auch die neusten Updates, sowohl vom Core-System wie auch der Plugins und des Designs eingesetzt und einige Konfigurationsanpassungen vorgenommen.

Vielen Dank für dein Verständnis!

#qsvsupport #qsvstatus #qsv
https://www.qsv.zone/notices/n6t3538qslepajal-lernplattform-cloud-learning-ch

Wir haben bei allen Kundenwebsites mit Wordpress die neusten Updates und Patches eingespielt. Die Wartungsarbeiten konnten erfolgreich beendet werden. Vielen Dank für deine Geduld.
#qsv #qsvsupport #qsvstatus
https://www.qsv.zone/notices/wbv2pffw8nlsbjrd-wordpress-update

Wir haben bei allen Kundenwebsites mit Wordpress die neusten Updates installiert. Alle Plugins und Themplates sind wieder auf dem aktuellen Stand.
Vielen Dank für dein Verständnis!

#qsv #qsvstatus #qsvstatus
https://www.qsv.zone/notices/rsthlwmb7nf3h7pk-wordpress-update

Erinnerung: Als Grundlage für künftige wichtige Updates wird die Datenbank-Software von Version 10.6 auf die aktuelle LTS-Version 10.11 aktualisiert.

Während des Updates kann es zu einem kurzen Unterbruch der Erreichbarkeit Ihrer Datenbank von maximal 5 bis 10 Minuten kommen. Es wird versucht, die Arbeiten so effizient wie möglich durchzuführen und die Auswirkungen auf deine Dienste minimal zu halten.
Vielen Dank für dein Verständnis!

#qsv #qsvsupport #qsvstatus
https://www.qsv.zone/notices/wslveylew2lu9f8g-update-der-datenbank-software

👍 Alle Cloud-Server konnten erfolgreich neu gestartet werden, alle Dienste sind wieder vollständig erreichbar!

Vielen Dank für dein Verständnis!
#qsv #qsvsupport #qsvstatus

Wir starten aus Wartungsgründen den Cloud-Server 01, 02 und 03 neu. Die Applikationen und Websites werden für ca. 60 Sekunden unterbrochen sein. Wir empfehlen während des Wartungsfensters keine Arbeiten in Plesk oder an Applikationen und Websites vorzunehmen.

Vielen Dank für dein Verständnis!

#qsv #qsvstatus #qsvsupport

https://www.qsv.zone/notices/teo0puotd9xh4ai1-neustart-cloud-server-01-02-und-03

Wir haben bei allen Kundenwebsites mit Wordpress die neusten Updates und Patches eingespielt. Grund für die kurzfristige Wartung waren mehrere veraltete Plugins und Templates. 
Vielen Dank für dein Verständnis!
 
#qsv #qsvstatus #qsvsupport
https://www.qsv.zone/notices/87wbqc7tsdybgag3-wordpress-update

Wir haben bei allen Kundenwebsites mit Wordpress die neusten Updates und Patches eingespielt. Grund für die kurzfristige Wartung waren mehrere Sicherheitslücken in Plugins und Templates.

Vielen Dank für dein Verständnis!

#qsv #qsvstatus #qsvsupport
https://www.qsv.zone/notices/kmkteob3xkmbfniu-wordpress-update

Derzeit installieren wir bei allen Kundenwebsites mit Wordpress die neusten Updates. Es kann daher zu kurzen Unterbrüchen oder zur kurzzeitigen Anzeige der Plesk-Wartungsseite anstelle der Website kommen.
Vielen Dank für dein Verständnis!

#qsv #qsvstatus
https://www.qsv.zone/notices/axaytb37pan9mosm-wordpress-update

Die Wartungsarbeiten konnten erfolgreich beendet werden, der Cloud-Server 01 konnte erfolgreich neu gestartet werden und ist wieder verfügbar. Vielen Dank für deine Geduld.

#qsv #qsvstatus
https://www.qsv.zone/notices/cj0mvdijmxtqjxsk-neustart-cloud-server-01

🚀 Neustart Cloud-Server 01!
Wir starten den Cloud-Server 01 aus Wartungsgründen neu. Es kommt daher zu einen kurzen Unterbruch aller Dienste innerhalb des Wartungsfensters.
Wir empfehlen während des Wartungsfensters keine Arbeiten in Plesk und in auf dem Cloud-Server 01 gehosteten Applikationen vorzunehmen.
Vielen Dank für dein Verständnis!

#qsv #qsvstatus
https://www.qsv.zone/notices/cj0mvdijmxtqjxsk-neustart-cloud-server-01

Derzeit installieren wir bei allen Kundenwebsites mit Wordpress die neusten Updates. Es kann daher zu kurzen Unterbrüchen oder zur kurzzeitigen Anzeige der Plesk-Wartungsseite anstelle der Website kommen.

Vielen Dank für dein Verständnis!

#qsv #qsvsupport #qsvstatus

Derzeit installieren wir bei allen Kundenwebsites mit Wordpress die neusten Updates. Es kann daher zu kurzen Unterbrüchen oder zur kurzzeitigen Anzeige der Plesk-Wartungsseite anstelle der Website kommen.
Vielen Dank für dein Verständnis!

#qsvsupport #qsvstatus #qsv
https://www.qsv.zone/notices/k3bnlwgb7nr9lxfz-wordpress-update

Derzeit installieren wir bei allen Kundenwebsites mit Wordpress die neusten Updates. Es kann daher zu kurzen Unterbrüchen oder zur kurzzeitigen Anzeige der Plesk-Wartungsseite anstelle der Website kommen.
Vielen Dank für dein Verständnis!

#qsvstatus #qsv #qsvstatus #qsvsupport

https://www.qsv.zone/notices/gimcqzgeigr9m6y5-wordpress-update

Alle Dienste sind Up and Running! Wir wünschen eine gute Nacht und einen ruhigen Sonntag!

#qsv #qsvstatus #qsvsupport
https://www.qsv.zone

Die Wartungsarbeiten konnten erfolgreich beendet werden. Bei allen Wordpress-Websites wurden Plugins und Designs sind wieder aktualisiert und auf dem aktuellen Softwarestand.
Vielen Dank für deine Geduld.

#qsv #qsvsupport #qsvstatus #wordpress
https://www.qsv.zone/notices/yu1jrowy1lufpfoq-wordpress-update

Done this with the #AMD 5600G's iGPU, now testing #Jellyfin hardware transcoding with my #Intel #ArcA380 GPU - one question though, is it normal for CPU usage to be rather high at least in the early parts of streaming (while transcoding), even with hardware transcoding?

I'm just trying to figure out if it is actually hardware transcoding - I'm assuming it is, bcos on the admin dashboard I'm seeing that it's transcoding as AV1 and I'm sure my Ryzen 7 1700 would not be able to do/handle that, esp considering that I'm testing with 4 streams playing concurrently? but the CPU usage is rather high the first minute or two or more from when the stream starts, it does lower down afterwards - the video playback is perfectly fine, no stuttering or anything like that.

My method of passthrough is the same as I did with the 5600G, that is a simple passthrough to the #LXC container, then to the #Docker container running Jellyfin. I don't think I noticed this high CPU usage when testing the 5600G, and the only minor configuration difference between the two was I'd used #VAAPI with the 5600G and disabled #AV1 encoding (since idt it supports it), while on the Arc A380 GPU I'm using Intel's #QSV and have enabled AV1 encoding.

Am I correct to assume that hardware transcoding is indeed working? Cos again, I'm quite certain my Ryzen 7 1700 would definitely NOT be able to handle this lol esp since I only give the LXC container 2 cores.

Done this with the #AMD 5600G's iGPU, now testing #Jellyfin hardware transcoding with my #Intel #ArcA380 GPU - one question though, is it normal for CPU usage to be rather high at least in the early parts of streaming (while transcoding), even with hardware transcoding?

I'm just trying to figure out if it is actually hardware transcoding - I'm assuming it is, bcos on the admin dashboard I'm seeing that it's transcoding as AV1 and I'm sure my Ryzen 7 1700 would not be able to do/handle that, esp considering that I'm testing with 4 streams playing concurrently? but the CPU usage is rather high the first minute or two or more from when the stream starts, it does lower down afterwards - the video playback is perfectly fine, no stuttering or anything like that.

My method of passthrough is the same as I did with the 5600G, that is a simple passthrough to the #LXC container, then to the #Docker container running Jellyfin. I don't think I noticed this high CPU usage when testing the 5600G, and the only minor configuration difference between the two was I'd used #VAAPI with the 5600G and disabled #AV1 encoding (since idt it supports it), while on the Arc A380 GPU I'm using Intel's #QSV and have enabled AV1 encoding.

Am I correct to assume that hardware transcoding is indeed working? Cos again, I'm quite certain my Ryzen 7 1700 would definitely NOT be able to handle this lol esp since I only give the LXC container 2 cores.

Bah. Looks like have hit the limits of the P400’s NVENC transcoder; hit rates below 1.00x for first time... it's put in a few years.

The P400 RAM usage is about 1 gb with 4 streams, but 100% on encode/decode. The P400 has 1 Pascal (6th gen) nvenc block and 2gb RAM.

Have an Arc A380 coming in now.

A380 should be able to handle quite a bit more, has two MFX engines (quicksync) & 6gb RAM.

Time will tell.

[ #P400 #A380 #nvenc #qsv #IntelArc #transcoding ]

Bah. Looks like have hit the limits of the P400’s NVENC transcoder; hit rates below 1.00x for first time... it's put in a few years.

The P400 RAM usage is about 1 gb with 4 streams, but 100% on encode/decode. The P400 has 1 Pascal (6th gen) nvenc block and 2gb RAM.

Have an Arc A380 coming in now.

A380 should be able to handle quite a bit more, has two MFX engines (quicksync) & 6gb RAM.

Time will tell.

[ #P400 #A380 #nvenc #qsv #IntelArc #transcoding ]

Bah. Looks like have hit the limits of the P400’s NVENC transcoder; hit rates below 1.00x for first time... it's put in a few years.

The P400 RAM usage is about 1 gb with 4 streams, but 100% on encode/decode. The P400 has 1 Pascal (6th gen) nvenc block and 2gb RAM.

Have an Arc A380 coming in now.

A380 should be able to handle quite a bit more, has two MFX engines (quicksync) & 6gb RAM.

Time will tell.

[ #P400 #A380 #nvenc #qsv #IntelArc #transcoding ]

Bah. Looks like have hit the limits of the P400’s NVENC transcoder; hit rates below 1.00x for first time... it's put in a few years.

The P400 RAM usage is about 1 gb with 4 streams, but 100% on encode/decode. The P400 has 1 Pascal (6th gen) nvenc block and 2gb RAM.

Have an Arc A380 coming in now.

A380 should be able to handle quite a bit more, has two MFX engines (quicksync) & 6gb RAM.

Time will tell.

[ #P400 #A380 #nvenc #qsv #IntelArc #transcoding ]

Der Jahresausklang ist eine spannende Zeit: Das Vergangene Revue passieren lassen und mit Neugier auf das Kommende blicken.

#qsv #qsvsupport #qsvstatus #mastodon #bluesky #newsletter

https://qsv.ch/frohe-festtage/

Der Jahresausklang ist eine spannende Zeit: Das Vergangene Revue passieren lassen und mit Neugier auf das Kommende blicken.

#qsv #qsvsupport #qsvstatus #mastodon #bluesky #newsletter

https://qsv.ch/frohe-festtage/

Der Jahresausklang ist eine spannende Zeit: Das Vergangene Revue passieren lassen und mit Neugier auf das Kommende blicken.

#qsv #qsvsupport #qsvstatus #mastodon #bluesky #newsletter

https://qsv.ch/frohe-festtage/

Der Jahresausklang ist eine spannende Zeit: Das Vergangene Revue passieren lassen und mit Neugier auf das Kommende blicken.

#qsv #qsvsupport #qsvstatus #mastodon #bluesky #newsletter

https://qsv.ch/frohe-festtage/

Wir installieren derzeit bei allen Websites mit Wordpress die aktuellen Updates. Es kann kurzzeitig zur Anzeige der Wartungsseite kommen.
#qsv #qsvstatus #wordpress

https://www.qsv.zone

Das Domain-Controlpanel ist derzeit nicht erreichbar. Weitere Informationen dazu auf unserer Status-Seite: https://status.qsv.zone
#qsv #qsvstatus