Incidents reported on status page for Spring Creek https://status.springcreek.io/ en https://status.springcreek.io/incident/964057 Tue, 14 Jul 2026 16:42:00 -0000 https://status.springcreek.io/incident/964057#84c0981275c1bb59fe5bc891e5e15999aebaf76f200d594b1c6609c8cf01ed24 We have identified the root cause of the downtime. High latency on a primary uplink was causing repeated failovers between the primary and secondary uplink. Redirecting all traffic over to the secondary link has resolved the availability problems. https://status.springcreek.io/ Tue, 14 Jul 2026 16:41:31 +0000 https://status.springcreek.io/#8eb97294f94c6b41cff4728755c5e0310f5bc3de0a49a00e02d9851d3d8f9d73 kenyonwx.com recovered https://status.springcreek.io/ Tue, 14 Jul 2026 16:35:48 +0000 https://status.springcreek.io/#8eb97294f94c6b41cff4728755c5e0310f5bc3de0a49a00e02d9851d3d8f9d73 kenyonwx.com went down https://status.springcreek.io/ Tue, 14 Jul 2026 16:23:30 +0000 https://status.springcreek.io/#507bf598b8d6e834f9b48a5e67312311a05f9238e7aaef493d8ef4f267542268 kenyonwx.com recovered https://status.springcreek.io/ Tue, 14 Jul 2026 16:11:34 +0000 https://status.springcreek.io/#507bf598b8d6e834f9b48a5e67312311a05f9238e7aaef493d8ef4f267542268 kenyonwx.com went down https://status.springcreek.io/ Tue, 14 Jul 2026 14:41:27 +0000 https://status.springcreek.io/#6f9cfc403542ce8c2a7b9fba0370240465b43058128be6746b4b5322b6aea492 kenyonwx.com recovered https://status.springcreek.io/incident/964057 Tue, 14 Jul 2026 14:40:00 -0000 https://status.springcreek.io/incident/964057#dd4caf38903392890178e532c0a5c7ebd5db5402fe5ce1cabf1336a9aee566a0 Monitoring is alerting to KenyonWX being unavailable. https://status.springcreek.io/ Tue, 14 Jul 2026 14:35:29 +0000 https://status.springcreek.io/#6f9cfc403542ce8c2a7b9fba0370240465b43058128be6746b4b5322b6aea492 kenyonwx.com went down https://status.springcreek.io/incident/937768 Sun, 28 Jun 2026 15:20:00 -0000 https://status.springcreek.io/incident/937768#e05367053571c60b5d497121b8baa34b09a914e70fe08408c5ea89feccebfca0 We have identified the root cause of the downtime. Severe weather resulted in the primary power source failing. The backup power source kicked in within 30 seconds, but an upstream router failed to power cycle correctly. A reboot of that router restored connectivity. https://status.springcreek.io/ Sun, 28 Jun 2026 15:17:32 +0000 https://status.springcreek.io/#526b3d1f9064be7face1a7826e111d904acc03ea002aa0aa4679b5e616402cdf kenyonwx.com recovered https://status.springcreek.io/ Sun, 28 Jun 2026 14:05:32 +0000 https://status.springcreek.io/#526b3d1f9064be7face1a7826e111d904acc03ea002aa0aa4679b5e616402cdf kenyonwx.com went down https://status.springcreek.io/incident/937768 Sun, 28 Jun 2026 14:05:00 -0000 https://status.springcreek.io/incident/937768#655e77b3af6a52f432214c6b2c75c81aff442cc0ff223765a59a4deaef88560a Monitoring is alerting to KenyonWX being unavailable. https://status.springcreek.io/incident/931668 Mon, 22 Jun 2026 14:12:00 -0000 https://status.springcreek.io/incident/931668#0e8f8d6760c411b3c5cbabcb24fb7e8e70dc403a5ec6a6eb1f63d3c7be851a49 Cloudflare has mitigated the network traffic disruption. With the issue fixed upstream at Cloudflare, Kenyonwx is reachable again. We will continue to monitor Cloudflare's status updates and will open a new incident if issues reoccur. Updates are occurring at https://new.cloudflarestatus.com/incidents/v3yl7jqmqj51 https://status.springcreek.io/ Mon, 22 Jun 2026 14:11:38 +0000 https://status.springcreek.io/#6f0a653807124e5650728d2822d80b0e591fb65af2fa11dc0fd6777dee21ac03 kenyonwx.com recovered https://status.springcreek.io/incident/931668 Mon, 22 Jun 2026 13:40:00 -0000 https://status.springcreek.io/incident/931668#686ff597df7dccf13b29d619a46721fbd0cd2035bf144feeae7ebe64a0869744 An upstream incident with Cloudflare is likely behind the outage. Updates can be tracked from Cloudflare here: https://new.cloudflarestatus.com/incidents/v3yl7jqmqj51 https://status.springcreek.io/ Mon, 22 Jun 2026 13:38:54 +0000 https://status.springcreek.io/#6f0a653807124e5650728d2822d80b0e591fb65af2fa11dc0fd6777dee21ac03 kenyonwx.com went down https://status.springcreek.io/incident/931668 Mon, 22 Jun 2026 13:35:00 -0000 https://status.springcreek.io/incident/931668#238e3a8a449f3850fcd649d042ca42d54a05d57172acefdcc0f119c4edeb6d63 Monitoring is alerting to consistent 502s when attempting to visit KenyonWX. https://status.springcreek.io/ Fri, 19 Jun 2026 18:23:31 +0000 https://status.springcreek.io/#1e420eb8165b34f54905eec6cede1dd555a9f4819614ada45b7c24dfb6948d8c kenyonwx.com recovered https://status.springcreek.io/incident/930075 Fri, 19 Jun 2026 18:20:00 -0000 https://status.springcreek.io/incident/930075#029a85466dc616cfa47586c8f469f6b4c4c510dd7b38fa96c578e2bf8cf8bc0e We have identified the root cause of the downtime. An upstream router failed over. Upon completion of the router failover, connectivity was restored. Downtime was less than 3 minutes. https://status.springcreek.io/ Fri, 19 Jun 2026 18:17:32 +0000 https://status.springcreek.io/#1e420eb8165b34f54905eec6cede1dd555a9f4819614ada45b7c24dfb6948d8c kenyonwx.com went down https://status.springcreek.io/incident/930075 Fri, 19 Jun 2026 18:17:00 -0000 https://status.springcreek.io/incident/930075#b32fe55a2b596c97a93b61b42c3e29ca66b17129953335afdd72034e1f76e648 Monitoring is alerting to consistent 502s when attempting to visit KenyonWX. https://status.springcreek.io/ Wed, 06 May 2026 17:17:47 +0000 https://status.springcreek.io/#4a433397cc2d9488ea5c33d377ddb8fb0bec3d33f292a488f6fd850722eeaf96 kenyonwx.com recovered https://status.springcreek.io/ Wed, 06 May 2026 16:54:42 +0000 https://status.springcreek.io/#4a433397cc2d9488ea5c33d377ddb8fb0bec3d33f292a488f6fd850722eeaf96 kenyonwx.com went down https://status.springcreek.io/incident/886076 Sun, 03 May 2026 00:20:00 -0000 https://status.springcreek.io/incident/886076#28f455a33fd0d2a1168207f5c0aabdcaf67cbd70587492c6d0aed4211a27e465 We have identified the root cause of the downtime. An upstream router was upgraded. The upgrade look less than 5 minutes and included several reboots that caused brief connection interruptions. Upon completion of the router upgrade, connectivity was restored. https://status.springcreek.io/ Sun, 03 May 2026 00:17:39 +0000 https://status.springcreek.io/#cad55ce5686139e32949be9acb2cbf6df98be4e0cb13a3040853138fe2bc5ddc kenyonwx.com recovered https://status.springcreek.io/ Sun, 03 May 2026 00:12:29 +0000 https://status.springcreek.io/#cad55ce5686139e32949be9acb2cbf6df98be4e0cb13a3040853138fe2bc5ddc kenyonwx.com went down https://status.springcreek.io/incident/886076 Sun, 03 May 2026 00:12:00 -0000 https://status.springcreek.io/incident/886076#206a1af3590ebe4512c31ff1a40a7292827d2ce48088047e6c4b6c219574394f Monitoring is alerting to consistent 502s when attempting to visit KenyonWX. https://status.springcreek.io/incident/871001 Tue, 14 Apr 2026 01:43:00 -0000 https://status.springcreek.io/incident/871001#8a462e106e6af7cf2e8232799a74727a848341353195c48c008a6c7c541d430e We have identified the root cause of the downtime. A brief power interruption caused downtime for upstream routers. A reboot of the upstream router automatically occurred after the power interruption and connectivity was restored. Downtime was approximately 3 minutes and 30 seconds. https://status.springcreek.io/incident/871001 Tue, 14 Apr 2026 01:38:00 -0000 https://status.springcreek.io/incident/871001#3642d5769871490079243056c630cabbec757049e95dc25f3fffa524c983cfdb Monitoring is alerting to consistent 502s when attempting to visit KenyonWX. https://status.springcreek.io/ Sun, 12 Apr 2026 10:37:32 +0000 https://status.springcreek.io/#5678e03f982e7e6740708f6864bdc7a882509e422f6a519b7891b8a48564d211 kenyonwx.com recovered https://status.springcreek.io/incident/869977 Sun, 12 Apr 2026 10:37:00 -0000 https://status.springcreek.io/incident/869977#4cde524a7a8c4cc3cbe69b92b5b4792831aada1de23c8ecbbf759048e4e7243a We have identified the root cause of the downtime. A brief power interruption caused downtime for upstream routers. A reboot of the upstream router automatically occurred after the power interruption and connectivity was restored. Downtime was approximately 3 minutes and 30 seconds. https://status.springcreek.io/ Sun, 12 Apr 2026 10:32:25 +0000 https://status.springcreek.io/#5678e03f982e7e6740708f6864bdc7a882509e422f6a519b7891b8a48564d211 kenyonwx.com went down https://status.springcreek.io/incident/869977 Sun, 12 Apr 2026 10:32:00 -0000 https://status.springcreek.io/incident/869977#f4e071f470707ba3a4a77b32b4ebce59963540688d6146cb35dabf0409fc851d Monitoring is alerting to consistent 502s when attempting to visit KenyonWX. https://status.springcreek.io/incident/854321 Sat, 21 Mar 2026 08:03:00 -0000 https://status.springcreek.io/incident/854321#71521be3d17035fd7761b8b392d7c3e1a9dfb12855ebf73299b81fff806449be We have identified the root cause of the downtime. An upstream router was upgraded. The upgrade look less than 5 minutes and included several reboots that caused brief connection interruptions. Upon completion of the router upgrade, connectivity was restored. https://status.springcreek.io/ Sat, 21 Mar 2026 07:57:36 +0000 https://status.springcreek.io/#e4b2845702a1d5f449a23a49fac425e752ea091bb29772cfc9b99bd3c39198ae kenyonwx.com recovered https://status.springcreek.io/ Sat, 21 Mar 2026 07:52:31 +0000 https://status.springcreek.io/#e4b2845702a1d5f449a23a49fac425e752ea091bb29772cfc9b99bd3c39198ae kenyonwx.com went down https://status.springcreek.io/incident/854321 Sat, 21 Mar 2026 07:52:00 -0000 https://status.springcreek.io/incident/854321#3d29f2d4b4197772cc9c3ada1c8e2cbe02277529527bd7045d289f9ed5b00882 Monitoring is alerting to consistent timeouts when attempting to visit KenyonWX. https://status.springcreek.io/ Tue, 17 Feb 2026 15:22:35 +0000 https://status.springcreek.io/#9eab6a74f0403656b3f4e1034b3d03976b7e770cf6838a2034955fc5ce1367f7 kenyonwx.com recovered https://status.springcreek.io/incident/828460 Tue, 17 Feb 2026 15:15:00 -0000 https://status.springcreek.io/incident/828460#641919e7ba8fdc21413cfba2b54ed510ed58207567b54e62fa7f1768e4a6f759 The site is now stable and monitoring has stabilized. Root Cause: The machine hosting the website experienced several network disconnections. With network connectivity stabilized, the intermittent timeouts resolved. https://status.springcreek.io/ Tue, 17 Feb 2026 15:09:49 +0000 https://status.springcreek.io/#9eab6a74f0403656b3f4e1034b3d03976b7e770cf6838a2034955fc5ce1367f7 kenyonwx.com went down https://status.springcreek.io/incident/828460 Tue, 17 Feb 2026 15:05:00 -0000 https://status.springcreek.io/incident/828460#10fcf860a541c8d73307cdd6935c75fd6bc5ff8f27eccc6e6f8005716cec1cb3 Alerting triggered notifying the team that KenyonWX is now unavailable. https://status.springcreek.io/incident/828460 Tue, 17 Feb 2026 15:03:00 -0000 https://status.springcreek.io/incident/828460#0d464567cd8cb040f12e459345b27067a20cfe05129ffb74974b5f8bdab2573f Monitoring is alerting to intermittent timeouts when attempting to visit KenyonWX. https://status.springcreek.io/incident/818826 Wed, 04 Feb 2026 20:50:00 -0000 https://status.springcreek.io/incident/818826#4b63f383b3b35c065be2fd765722c9b37a815cc4947eb33a9d270a147229974d The site is now stable and monitoring has stabilized. Alerting triggered notifying the team that KenyonWX was unavailable. Downtime was less than 3 minutes. Root Cause: The machine hosting the website experienced several network disconnections that were less than 10 seconds a piece. With network connectivity stabilized, the intermittent timeouts resolved. https://status.springcreek.io/incident/818826 Wed, 04 Feb 2026 20:35:00 -0000 https://status.springcreek.io/incident/818826#9b5df2d660a5227a3740c8c9959436e275be22543735f198f1c811b7d73620e5 Monitoring is alerting to intermittent timeouts when attempting to visit KenyonWX. https://status.springcreek.io/incident/812320 Tue, 27 Jan 2026 00:39:00 -0000 https://status.springcreek.io/incident/812320#a5979dcbf9517a3690926c5f3f4b4a93712bd0526412197d9e93cb979472b899 Earlier today, intermittent timeouts (approximately 30 seconds each) were observed on the site. These brief network stalls caused the uptime monitor to report an incident, even though the service remained largely available. Root Cause: Short-lived origin response delays combined with previous monitoring thresholds. Resolution & Improvements: - Monitoring timeout increased to 30 seconds - Check frequency, confirmation, and recovery periods adjusted to reduce false positives - Logging enabled for better visibility into future incidents The site is now stable and monitoring reflects actual availability.