<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Copperhost Status</title>
  <subtitle>Service incidents and scheduled maintenance</subtitle>
  <id>https://copperhost-status.pages.dev/</id>
  <link href="https://copperhost-status.pages.dev/"/>
  <link rel="self" href="https://copperhost-status.pages.dev/status.xml"/>
  <updated>2026-07-08T12:00:00Z</updated>
  <author><name>Copperhost</name></author>
  <entry>
    <title>[Scheduled] Scheduled: US-East network capacity upgrade</title>
    <id>tag:copperhost.example,2026:MNT-0106</id>
    <link href="https://copperhost-status.pages.dev/#history"/>
    <updated>2026-07-08T12:00:00Z</updated>
    <published>2026-07-08T12:00:00Z</published>
    <category term="Maintenance"/>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled&lt;/strong&gt; — 2026-07-08T12:00:00Z&lt;br/&gt;We will upgrade network capacity in our US-East region on July 15, 02:00–04:00 UTC. Brief connectivity blips of up to a few minutes are possible for hosted sites and the control panel during the window. Email and DNS are not affected. No action is required on your part.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>[Resolved] Email delivery delays</title>
    <id>tag:copperhost.example,2026:INC-1042</id>
    <link href="https://copperhost-status.pages.dev/#history"/>
    <updated>2026-07-05T11:15:00Z</updated>
    <published>2026-07-05T09:12:00Z</published>
    <category term="Degraded Performance"/>
    <content type="html">&lt;p&gt;&lt;strong&gt;Resolved&lt;/strong&gt; — 2026-07-05T11:15:00Z&lt;br/&gt;The backlog has fully cleared and mail is delivering at normal speed. Total impact: delayed delivery for roughly two hours. No messages were lost.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; — 2026-07-05T10:28:00Z&lt;br/&gt;The queue is draining and delivery times are returning to baseline. We are monitoring the backlog as it clears.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Identified&lt;/strong&gt; — 2026-07-05T09:41:00Z&lt;br/&gt;A mail queue processor on one node became stuck following a routine package update. We are restarting the affected workers and draining the backlog.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Investigating&lt;/strong&gt; — 2026-07-05T09:12:00Z&lt;br/&gt;We are investigating reports of delayed inbound and outbound email. Messages are queuing normally and are not being lost — delivery is simply slower than usual.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>[Resolved] DNS resolution failures for EU-routed queries</title>
    <id>tag:copperhost.example,2026:INC-1038</id>
    <link href="https://copperhost-status.pages.dev/#history"/>
    <updated>2026-06-22T15:05:00Z</updated>
    <published>2026-06-22T14:03:00Z</published>
    <category term="Partial Outage"/>
    <content type="html">&lt;p&gt;&lt;strong&gt;Resolved&lt;/strong&gt; — 2026-06-22T15:05:00Z&lt;br/&gt;DNS resolution is fully restored across all regions. Impact window: approximately 45 minutes for EU-routed queries. We have added a validation gate to our resolver config pipeline to prevent a repeat.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; — 2026-06-22T14:49:00Z&lt;br/&gt;The rollback is complete and query success rates have returned to normal. Monitoring to confirm stability.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Identified&lt;/strong&gt; — 2026-06-22T14:21:00Z&lt;br/&gt;A bad configuration push to the EU anycast resolvers caused a subset of queries to fail. We are rolling the change back.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Investigating&lt;/strong&gt; — 2026-06-22T14:03:00Z&lt;br/&gt;We are seeing elevated DNS query failures for customers routed through our Frankfurt resolver. Other regions are unaffected. Investigating now.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>[Completed] Completed: email storage migration</title>
    <id>tag:copperhost.example,2026:MNT-0100</id>
    <link href="https://copperhost-status.pages.dev/#history"/>
    <updated>2026-06-05T04:36:00Z</updated>
    <published>2026-05-29T16:00:00Z</published>
    <category term="Maintenance"/>
    <content type="html">&lt;p&gt;&lt;strong&gt;Completed&lt;/strong&gt; — 2026-06-05T04:36:00Z&lt;br/&gt;The migration completed ahead of schedule with no impact to mail delivery. Webmail is fully available.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In progress&lt;/strong&gt; — 2026-06-05T03:00:00Z&lt;br/&gt;The migration window has begun. Webmail may be intermittently unavailable for the next two hours.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Scheduled&lt;/strong&gt; — 2026-05-29T16:00:00Z&lt;br/&gt;We will migrate email storage to faster hardware on June 5, 03:00–05:00 UTC. Webmail may be briefly unavailable; mail delivery continues to queue and will not be lost.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>[Resolved] Control panel login failures</title>
    <id>tag:copperhost.example,2026:INC-1031</id>
    <link href="https://copperhost-status.pages.dev/#history"/>
    <updated>2026-05-30T22:09:00Z</updated>
    <published>2026-05-30T20:47:00Z</published>
    <category term="Degraded Performance"/>
    <content type="html">&lt;p&gt;&lt;strong&gt;Resolved&lt;/strong&gt; — 2026-05-30T22:09:00Z&lt;br/&gt;Control panel access is fully restored. Impact: about 1h20m of intermittent login failures. Hosting, email and DNS were never affected. We have added certificate-expiry alerting at the 30-day mark.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; — 2026-05-30T21:58:00Z&lt;br/&gt;Logins are succeeding again after the new certificate was rolled out. Monitoring for any repeat failures.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Identified&lt;/strong&gt; — 2026-05-30T21:10:00Z&lt;br/&gt;An expired internal certificate was being rejected by our session service. We are issuing and deploying a replacement.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Investigating&lt;/strong&gt; — 2026-05-30T20:47:00Z&lt;br/&gt;Some customers are unable to sign in to the Copperhost control panel. Hosted sites, email and DNS are fully unaffected. Investigating.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>[Resolved] Elevated latency for US-East hosted sites</title>
    <id>tag:copperhost.example,2026:INC-1024</id>
    <link href="https://copperhost-status.pages.dev/#history"/>
    <updated>2026-05-11T09:32:00Z</updated>
    <published>2026-05-11T06:30:00Z</published>
    <category term="Degraded Performance"/>
    <content type="html">&lt;p&gt;&lt;strong&gt;Resolved&lt;/strong&gt; — 2026-05-11T09:32:00Z&lt;br/&gt;Latency has returned to normal across all hosted sites. No data was affected. We are adding storage capacity to give the cluster more headroom.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; — 2026-05-11T08:40:00Z&lt;br/&gt;Response times have improved following the rebalance. We continue to monitor as traffic normalizes.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Identified&lt;/strong&gt; — 2026-05-11T07:05:00Z&lt;br/&gt;Increased load on one storage cluster is causing elevated I/O latency. We are rebalancing traffic away from the affected nodes.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Investigating&lt;/strong&gt; — 2026-05-11T06:30:00Z&lt;br/&gt;We are investigating slower-than-normal response times for a subset of hosted sites in our US-East region.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>[Resolved] Partial hosting outage in US-East (power fault)</title>
    <id>tag:copperhost.example,2026:INC-1009</id>
    <link href="https://copperhost-status.pages.dev/#history"/>
    <updated>2026-04-18T04:22:00Z</updated>
    <published>2026-04-18T02:14:00Z</published>
    <category term="Major Outage"/>
    <content type="html">&lt;p&gt;&lt;strong&gt;Resolved&lt;/strong&gt; — 2026-04-18T04:22:00Z&lt;br/&gt;All hosted sites and the control panel are fully restored. Total impact: about two hours for affected US-East customers. Redundant power to the affected hall has been validated, and a full post-incident review has been published to customers.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; — 2026-04-18T03:40:00Z&lt;br/&gt;Roughly 90% of affected sites are back online after migration. We are bringing the remaining nodes up and monitoring closely.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Identified&lt;/strong&gt; — 2026-04-18T02:35:00Z&lt;br/&gt;A power distribution fault in one datacenter hall took a rack of hosting nodes offline. Affected sites are being migrated onto healthy capacity.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Investigating&lt;/strong&gt; — 2026-04-18T02:14:00Z&lt;br/&gt;We are aware of an outage affecting a portion of hosted sites and the control panel in our US-East datacenter. We are engaging the facility team now.&lt;/p&gt;</content>
  </entry>
</feed>
