Status updates | Filliravaz's Services Incidents and maintenance reported on status page for Filliravaz's Services https://status.filliravaz.me/ en Urgent software update https://status.filliravaz.me/incident/1092938 Sat, 17 Oct 2026 14:29:12 -0000 https://status.filliravaz.me/incident/1092938#2f7009e5a3884f9b3ebb6b513868a0a752036d8d3fa95ea2ec1be486950adcfd Incident The critical software update was completed. No further downtime is expected. Urgent software update https://status.filliravaz.me/incident/1092938 Sat, 17 Oct 2026 14:18:06 -0000 https://status.filliravaz.me/incident/1092938#6e245b4bb7266562ba2e1a2b438827d5b1ebeb2d527b9ceb0dcd56f1fa4f5e14 Incident An emergency rollout is being performed for some of our services, due to a critical security issue upstream of the server software hosted by us. Our service provider has informed us that a kernel vulnerability was found and reported. It's important to note that the kernel vulnerability was found at the host level, and not on our software stacks. We do not believe that user data was extracted, but we will run checks on our systems to validate this. We apologize for the short notice, and for any troubles that this outage may cause. Brief outage of core system https://status.filliravaz.me/incident/784550 Thu, 11 Dec 2025 15:08:00 -0000 https://status.filliravaz.me/incident/784550#73d82287d4d2ab994c3e7c200c305af40309adf74122477b8e4b72539f88f338 Incident After an investigation, we have determined that the reason for this issue was a firewall rule that got triggered after an influx of suspicious requests. This was fixed by revising the rule, and by adding further upstream filtering/ddos protection. Brief outage of core system https://status.filliravaz.me/incident/784550 Thu, 11 Dec 2025 15:07:00 -0000 https://status.filliravaz.me/incident/784550#cbd97d542ebd206fbfb9f9464f3c3bd6afe64698600df06ab56a08e068c00ed9 Incident Our monitoring has detected a short-lived issue about our core processing server. As a result, all services hosted were unavailable briefly, with the exception of the main website, that was still available due to upstream caches. Initial investigation indicates that this was caused by a brief connectivity loss to our server. By our internal monitoring, the loss of connectivity lasted a total of 24 seconds, but it was enough to trigger monitoring alerts. The server connectivity and access to services is now as expected, but we will continue investigating in a root cause.