Incidents reported on status page for nolife.uk https://status.nolife.uk/ en https://status.nolife.uk/ Fri, 25 Jul 2025 03:48:41 +0000 https://status.nolife.uk/#f8206c3f6609d3f6e394ae3ee54db4609b2d1fe6304156f81dfc1988f8ace32f nolife.uk recovered https://status.nolife.uk/ Thu, 24 Jul 2025 11:27:27 +0000 https://status.nolife.uk/#f8206c3f6609d3f6e394ae3ee54db4609b2d1fe6304156f81dfc1988f8ace32f nolife.uk went down https://status.nolife.uk/ Wed, 23 Jul 2025 09:49:23 +0000 https://status.nolife.uk/#e0da94cb070e49d8aa736203de8ea01dbeb9b26e33a0d70c4efa985fe8aecfca nolife.uk recovered https://status.nolife.uk/ Wed, 23 Jul 2025 08:50:02 +0000 https://status.nolife.uk/#e0da94cb070e49d8aa736203de8ea01dbeb9b26e33a0d70c4efa985fe8aecfca nolife.uk went down https://status.nolife.uk/ Tue, 24 Jun 2025 23:47:38 +0000 https://status.nolife.uk/#3b583107deef60efd2e13e49fe4de4afe27e273773c8a6e6759950d452a93d72 nolife.uk recovered https://status.nolife.uk/ Tue, 24 Jun 2025 23:39:20 +0000 https://status.nolife.uk/#3b583107deef60efd2e13e49fe4de4afe27e273773c8a6e6759950d452a93d72 nolife.uk went down https://status.nolife.uk/ Tue, 24 Jun 2025 11:23:18 +0000 https://status.nolife.uk/#cb0254a1ec903848fec32ac452bdec51059e07e3d25fcd39fb42587278af30cc nolife.uk recovered https://status.nolife.uk/ Tue, 24 Jun 2025 10:51:05 +0000 https://status.nolife.uk/#cb0254a1ec903848fec32ac452bdec51059e07e3d25fcd39fb42587278af30cc nolife.uk went down https://status.nolife.uk/ Mon, 23 Jun 2025 18:04:31 +0000 https://status.nolife.uk/#e5107c2fb12846ccf6d24ebbe553e43c8661c5e5edc978da4558fdd964d6e1d0 nolife.uk recovered https://status.nolife.uk/ Mon, 23 Jun 2025 17:59:13 +0000 https://status.nolife.uk/#e5107c2fb12846ccf6d24ebbe553e43c8661c5e5edc978da4558fdd964d6e1d0 nolife.uk went down https://status.nolife.uk/ Mon, 23 Jun 2025 10:57:52 +0000 https://status.nolife.uk/#9bb5b95cb60a6651cce61df5d8b74bead4f13108455d2e7ad59b460820f200ca nolife.uk recovered https://status.nolife.uk/ Mon, 23 Jun 2025 08:01:21 +0000 https://status.nolife.uk/#9bb5b95cb60a6651cce61df5d8b74bead4f13108455d2e7ad59b460820f200ca nolife.uk went down https://status.nolife.uk/ Mon, 23 Jun 2025 01:38:51 +0000 https://status.nolife.uk/#462ef2ab7162c93482ce7db076eb46a8a9315a7a2e76fe7559341fdd3200b5ab nolife.uk recovered https://status.nolife.uk/ Mon, 23 Jun 2025 01:32:51 +0000 https://status.nolife.uk/#462ef2ab7162c93482ce7db076eb46a8a9315a7a2e76fe7559341fdd3200b5ab nolife.uk went down https://status.nolife.uk/incident/436578 Sun, 29 Sep 2024 12:00:00 -0000 https://status.nolife.uk/incident/436578#6b9b74b05804b2c3ad53460589e900a016b821a6120178656308038cf223c95c misconfigured DNS now Solved https://status.nolife.uk/incident/436578 Sun, 29 Sep 2024 11:59:00 -0000 https://status.nolife.uk/incident/436578#74c7ca56a9438857dcd253de593c837efe181f63cd77f02781dbd959fe959ed7 servers are down investigating https://status.nolife.uk/incident/436578 Sun, 29 Sep 2024 00:11:00 -0000 https://status.nolife.uk/incident/436578#a01a9f147bbeb372c400b3f4613a9fe406913eed72a1c2bde20f4aef283bd134 1:11 AM GMT Downtime reported https://status.nolife.uk/incident/435776 Fri, 27 Sep 2024 13:58:00 -0000 https://status.nolife.uk/incident/435776#436317ed36840f07e926d78d9e844b0761d7255e6ba3048a19bc8d78b9ceb715 "The downtime was caused by a misconfigured Docker container that was assigned the wrong port. Upon server restart, the container attempted to start and stopped Apache in the process. This caused the Apache service to be interrupted https://status.nolife.uk/incident/435776 Fri, 27 Sep 2024 09:00:00 -0000 https://status.nolife.uk/incident/435776#172805952b5e8891cc2b9f13504ca2b368f0b0e87c8e4ea4da5e3ec633dd551f Down time started