Incidents | Flolon Server Incidents reported on status page for Flolon Server https://uptime.flolon.cc/ https://d1lppblt9t2x15.cloudfront.net/logos/4f74d6008592e67c68623cfd0a7ed8d0.png Incidents | Flolon Server https://uptime.flolon.cc/ en Fenserv1 went down https://uptime.flolon.cc/ Fri, 13 Mar 2026 19:21:57 +0000 https://uptime.flolon.cc/#9d34cc0b35b3748f69316ec50f462279099d68bdab02f30e25c814b0de77e9c3 Fenserv1 went down flolon.cc recovered https://uptime.flolon.cc/ Wed, 11 Mar 2026 13:29:44 +0000 https://uptime.flolon.cc/#5635791e0e1900caeb2c01008b3cc8b73c6bed67050145d658fb03ba260ee324 flolon.cc recovered flolon.cc went down https://uptime.flolon.cc/ Wed, 11 Mar 2026 06:39:37 +0000 https://uptime.flolon.cc/#5635791e0e1900caeb2c01008b3cc8b73c6bed67050145d658fb03ba260ee324 flolon.cc went down flolon.cc recovered https://uptime.flolon.cc/ Tue, 10 Mar 2026 17:21:18 +0000 https://uptime.flolon.cc/#f3beb75604d1d9a397c560a925dbb50dc34e9d02fe958bae06f21b6c31134593 flolon.cc recovered flolon.cc went down https://uptime.flolon.cc/ Tue, 10 Mar 2026 17:12:44 +0000 https://uptime.flolon.cc/#f3beb75604d1d9a397c560a925dbb50dc34e9d02fe958bae06f21b6c31134593 flolon.cc went down flolon.cc recovered https://uptime.flolon.cc/ Tue, 27 Jan 2026 20:47:42 +0000 https://uptime.flolon.cc/#ceae2332d3aff8bc1409d2d715f2d9f583515456ddf9ff0f6418fa3f4656f1e8 flolon.cc recovered flolon.cc went down https://uptime.flolon.cc/ Tue, 27 Jan 2026 20:44:51 +0000 https://uptime.flolon.cc/#ceae2332d3aff8bc1409d2d715f2d9f583515456ddf9ff0f6418fa3f4656f1e8 flolon.cc went down flolon.cc recovered https://uptime.flolon.cc/ Tue, 06 Jan 2026 06:41:39 +0000 https://uptime.flolon.cc/#ad8b6dcaf9fc1856c4352d4f4d302ec68aa1cc62f67ec1ca403e123b498a553e flolon.cc recovered flolon.cc went down https://uptime.flolon.cc/ Tue, 06 Jan 2026 06:18:48 +0000 https://uptime.flolon.cc/#ad8b6dcaf9fc1856c4352d4f4d302ec68aa1cc62f67ec1ca403e123b498a553e flolon.cc went down Fenserv2 went down https://uptime.flolon.cc/ Thu, 06 Nov 2025 19:08:26 +0000 https://uptime.flolon.cc/#fe5ccaebc007e4e320a198ba08beb0e3d31c8fe191b14ff5fbe64d70f2ee61c8 Fenserv2 went down