Incidents reported on status page for Flolon Server https://uptime.flolon.cc/ https://d1lppblt9t2x15.cloudfront.net/logos/4f74d6008592e67c68623cfd0a7ed8d0.png https://uptime.flolon.cc/ en https://uptime.flolon.cc/ Mon, 18 May 2026 01:26:42 +0000 https://uptime.flolon.cc/#2d99c5a66cc0ce79d1fbfc343f63cedb9bd57879c454208fcaff744fef7837c1 flolon.cc recovered https://uptime.flolon.cc/ Mon, 18 May 2026 01:24:29 +0000 https://uptime.flolon.cc/#2d99c5a66cc0ce79d1fbfc343f63cedb9bd57879c454208fcaff744fef7837c1 flolon.cc went down https://uptime.flolon.cc/ Thu, 02 Apr 2026 02:02:39 +0000 https://uptime.flolon.cc/#93e4f90760da30e00ef58b2310ed4aa0a6cedcb391ffbd0c24a6a9fdd2547c59 Fenserv1 went down https://uptime.flolon.cc/ Thu, 02 Apr 2026 01:56:02 +0000 https://uptime.flolon.cc/#c4435a6846ed698971736689a793cc7127f945fbdcf0334fc32c37da5f87fff8 Fenserv1 recovered https://uptime.flolon.cc/ Thu, 02 Apr 2026 01:47:18 +0000 https://uptime.flolon.cc/#c4435a6846ed698971736689a793cc7127f945fbdcf0334fc32c37da5f87fff8 Fenserv1 went down https://uptime.flolon.cc/ Thu, 02 Apr 2026 01:41:03 +0000 https://uptime.flolon.cc/#dc03d887ec46bc1f6d89a70a12c37c34d6bd409927fa5594cc0f01e91e7cdc38 Fenserv1 recovered https://uptime.flolon.cc/ Wed, 01 Apr 2026 23:26:09 +0000 https://uptime.flolon.cc/#dc03d887ec46bc1f6d89a70a12c37c34d6bd409927fa5594cc0f01e91e7cdc38 Fenserv1 went down https://uptime.flolon.cc/ Mon, 23 Mar 2026 20:08:45 +0000 https://uptime.flolon.cc/#599fc79de9b7530ff5b5e05b76195a407883ad8bfc797deb4dec8e3dd26a07d7 flolon.cc recovered https://uptime.flolon.cc/ Mon, 23 Mar 2026 20:06:37 +0000 https://uptime.flolon.cc/#599fc79de9b7530ff5b5e05b76195a407883ad8bfc797deb4dec8e3dd26a07d7 flolon.cc went down https://uptime.flolon.cc/ Mon, 23 Mar 2026 19:35:49 +0000 https://uptime.flolon.cc/#08aa931816e027bdf7da4ebe996960a5b927828f3e9a250b2dc89f375da9d70e flolon.cc recovered https://uptime.flolon.cc/ Mon, 23 Mar 2026 19:33:40 +0000 https://uptime.flolon.cc/#08aa931816e027bdf7da4ebe996960a5b927828f3e9a250b2dc89f375da9d70e flolon.cc went down https://uptime.flolon.cc/ Wed, 18 Mar 2026 15:50:39 +0000 https://uptime.flolon.cc/#b4befa2dbe49c53339950af8f9ae5d5bd0f3400d6bed8dbf3566bcc574450ab4 flolon.cc recovered https://uptime.flolon.cc/ Wed, 18 Mar 2026 15:26:36 +0000 https://uptime.flolon.cc/#b4befa2dbe49c53339950af8f9ae5d5bd0f3400d6bed8dbf3566bcc574450ab4 flolon.cc went down https://uptime.flolon.cc/ Sun, 15 Mar 2026 00:26:11 +0000 https://uptime.flolon.cc/#9d34cc0b35b3748f69316ec50f462279099d68bdab02f30e25c814b0de77e9c3 Fenserv1 recovered https://uptime.flolon.cc/ Fri, 13 Mar 2026 19:21:57 +0000 https://uptime.flolon.cc/#9d34cc0b35b3748f69316ec50f462279099d68bdab02f30e25c814b0de77e9c3 Fenserv1 went down https://uptime.flolon.cc/ Wed, 11 Mar 2026 13:29:44 +0000 https://uptime.flolon.cc/#5635791e0e1900caeb2c01008b3cc8b73c6bed67050145d658fb03ba260ee324 flolon.cc recovered https://uptime.flolon.cc/ Wed, 11 Mar 2026 06:39:37 +0000 https://uptime.flolon.cc/#5635791e0e1900caeb2c01008b3cc8b73c6bed67050145d658fb03ba260ee324 flolon.cc went down https://uptime.flolon.cc/ Tue, 10 Mar 2026 17:21:18 +0000 https://uptime.flolon.cc/#f3beb75604d1d9a397c560a925dbb50dc34e9d02fe958bae06f21b6c31134593 flolon.cc recovered https://uptime.flolon.cc/ Tue, 10 Mar 2026 17:12:44 +0000 https://uptime.flolon.cc/#f3beb75604d1d9a397c560a925dbb50dc34e9d02fe958bae06f21b6c31134593 flolon.cc went down