https://status.codrlabs.comAll systems operational — incident history for codrlabsSat, 03 Oct 2026 00:08:44 +000060https://status.codrlabs.com/#2026-09-21-website-host-errors2026-09-21-website-host-errorsMon, 21 Sep 2026 15:12:00 +0000<p><strong>12:15 MDT, 21 Sep — Resolved.</strong> Our website host reports its network healthy again, and codrlabs.com has loaded normally on every check since 11:08 MDT. Nothing is needed on your side.</p><p><strong>12:10 MDT, 21 Sep — Monitoring.</strong> From 09:12 MDT, the company that hosts our website had an incident causing errors and slow loading on the sites it serves, codrlabs.com included. They have fixed it, and our checks have shown the site healthy since 11:08 MDT. This notice will close itself once the site has stayed green for three checks in a row. If a page still fails to load for you, retrying should work. The platform, Maestronom Cast, the support portal and email run elsewhere and were not affected.</p>https://status.codrlabs.com/#2026-09-13-support-portal-unreachable2026-09-13-support-portal-unreachableSun, 13 Sep 2026 10:08:00 +0000<p><strong>08:20 MDT, 14 Sep — Resolved.</strong> The upstream network fault has cleared and the support portal is loading normally again. No tickets or replies were lost.</p><p><strong>18:20 MDT, 13 Sep — Still ongoing, and this page will swing between green and red while it lasts.</strong> The fault is intermittent: measured just now, 7 of 20 attempts to open the support portal failed. We check once an hour, so this page can show green at a moment when the portal is failing for you, and red at a moment when it works — the honest summary is that it is unreliable right now, not cleanly up or down. Retrying usually gets through. Our upstream provider has confirmed the fault and is working on it, with no estimated time to fix. Email is not affected.</p><p><strong>What to do in the meantime:</strong> write to <code>hello@codrlabs.com</code>, or to <code>artists@</code> or <code>open@</code>. Email does not travel through the part of our network that is failing — messages are arriving normally and we are reading and replying as usual. Retrying the portal also works more often than not.</p><p><strong>04:40 MDT, 13 Sep — Identified.</strong> This is a network fault between our content delivery network and the servers that run the support portal. It sits upstream of us and is not something we can fix from our side; the provider has acknowledged it and is working on it. Requests that fail never reach the helpdesk at all, so no tickets and no replies have been lost. If you see a <strong>Connection timed out</strong> page with <strong>error code 522</strong>, that is this.</p><p><strong>04:08 MDT, 13 Sep — Investigating.</strong> The support portal started failing to load for some people, some of the time. Tickets already open are unaffected, and retrying usually works.</p>