<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Airmark Radio Status - Incident history</title>
    <link>https://airmarkradio.instatus.com</link>
    <description>Airmark Radio</description>
    <pubDate>Wed, 11 Nov 2026 15:32:10 +0000</pubDate>
    
<item>
  <title>Shield Zone Update Failures</title>
  <description>
    Type: Incident
    Duration: 1 day, 19 hours and 31 minutes

    Affected Components: Edge Shield
    Nov 11, 16:15:41 GMT+0 - Resolved - This issue has now been resolved. Nov 11, 15:51:46 GMT+0 - Monitoring - Our Engineering team has applied a fix to the Shield rule logic and we are currently monitoring the situation. Any updates performed on Shield from 11:48am UTC will need to be reissued on the affected zone (API call or change toggle). Nov 11, 15:32:10 GMT+0 - Investigating - We are currently reviewing an issue where shield zone rule or logic changes are failing to propagate across our network. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 19 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>16:15:41</var> GMT+0</small><br><strong>Resolved</strong> -
  This issue has now been resolved..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>15:51:46</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our Engineering team has applied a fix to the Shield rule logic and we are currently monitoring the situation. Any updates performed on Shield from 11:48am UTC will need to be reissued on the affected zone (API call or change toggle)..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>15:32:10</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently reviewing an issue where shield zone rule or logic changes are failing to propagate across our network..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 11 Nov 2026 15:32:10 +0000</pubDate>
  <link>https://airmarkradio.instatus.com/incident/cmwfcn2yn01sd1bq9435im12h</link>
  <guid>https://airmarkradio.instatus.com/incident/cmwfcn2yn01sd1bq9435im12h</guid>
</item>

<item>
  <title>Scheduled maintenance: Aster Mail temporarily unavailable</title>
  <description>
    Type: Maintenance
    Duration: 10 minutes

    Affected Components: Outgoing Mail
    Oct 24, 02:36:13 GMT+0 - Completed - The upgrade is finished, and all Aster services are running normally. Thank you for your patience. Oct 24, 02:35:11 GMT+0 - Completed - Maintenance ended Oct 24, 02:24:56 GMT+0 - Identified - Summary: Scheduled maintenance on Aster Mail infrastructure

Description: We will perform scheduled maintenance on Saturday, 2026-10-24, from 03:00 to 03:30 UTC (Friday, 2026-10-23, 23:00 to 23:30 US/Eastern). During this window, our engineers will upgrade the database server that supports Aster Mail to add memory, processing capacity, and storage.

We expect Aster Mail to be unavailable for approximately 10 minutes within this window. We will provide an update on this page when the maintenance is complete.

Customer impact:
- You can&#039;t sign in, load your mailbox, or send email in the web app, the desktop and mobile apps, or Aster Bridge.
- Email sent to you during the maintenance is held on our mail servers and delivered to your inbox when the maintenance is complete. No email is lost.
- Your account, settings, and data are not affected.

Workaround: None required. You don&#039;t need to take any action.

We thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>02:36:13</var> GMT+0</small><br><strong>Completed</strong> -
  The upgrade is finished, and all Aster services are running normally. Thank you for your patience..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>02:35:11</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance ended.</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>02:24:56</var> GMT+0</small><br><strong>Identified</strong> -
  Summary: Scheduled maintenance on Aster Mail infrastructure

Description: We will perform scheduled maintenance on Saturday, 2026-10-24, from 03:00 to 03:30 UTC (Friday, 2026-10-23, 23:00 to 23:30 US/Eastern). During this window, our engineers will upgrade the database server that supports Aster Mail to add memory, processing capacity, and storage.

We expect Aster Mail to be unavailable for approximately 10 minutes within this window. We will provide an update on this page when the maintenance is complete.

Customer impact:
- You can&#039;t sign in, load your mailbox, or send email in the web app, the desktop and mobile apps, or Aster Bridge.
- Email sent to you during the maintenance is held on our mail servers and delivered to your inbox when the maintenance is complete. No email is lost.
- Your account, settings, and data are not affected.

Workaround: None required. You don&#039;t need to take any action.

We thank you for your patience..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 24 Oct 2026 02:24:56 +0000</pubDate>
  <link>https://airmarkradio.instatus.com/maintenance/cmwgvbamp02tg1mo2631mttat</link>
  <guid>https://airmarkradio.instatus.com/maintenance/cmwgvbamp02tg1mo2631mttat</guid>
</item>

<item>
  <title>Service disruption during data center power maintenance (Hetzner FSN1-DC8)</title>
  <description>
    Type: Incident
    Duration: 6 days and 1 hour

    Affected Components: Outgoing Mail, Incoming Mail
    Sep 30, 09:02:00 GMT+0 - Resolved - All Aster services are back to normal. Services were unavailable or degraded from 08:37 to 11:02 CEST. Mail sent to you during this window is delivered as normal once the senders&#039; servers retry. We&#039;re sorry for the disruption. Sep 30, 07:15:00 GMT+0 - Investigating - The disruption is caused by maintenance on the emergency power systems at our hosting provider&#039;s data center (Hetzner, FSN1-DC8), which left a storage volume on one of our servers unresponsive. We&#039;re monitoring the situation and will restore full service as soon as the server is stable. Hetzner&#039;s status: https://status.hetzner.com/incident/846711ea-c512-4e62-ac0b-1b29f057847a Sep 30, 06:40:00 GMT+0 - Investigating - We&#039;re seeing errors and timeouts across Aster Mail. Some users may be unable to sign in, load their mailbox, or send mail. We&#039;re investigating. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days and 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>09:02:00</var> GMT+0</small><br><strong>Resolved</strong> -
  All Aster services are back to normal. Services were unavailable or degraded from 08:37 to 11:02 CEST. Mail sent to you during this window is delivered as normal once the senders&#039; servers retry. We&#039;re sorry for the disruption..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>07:15:00</var> GMT+0</small><br><strong>Investigating</strong> -
  The disruption is caused by maintenance on the emergency power systems at our hosting provider&#039;s data center (Hetzner, FSN1-DC8), which left a storage volume on one of our servers unresponsive. We&#039;re monitoring the situation and will restore full service as soon as the server is stable. Hetzner&#039;s status: https://status.hetzner.com/incident/846711ea-c512-4e62-ac0b-1b29f057847a.</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>06:40:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re seeing errors and timeouts across Aster Mail. Some users may be unable to sign in, load their mailbox, or send mail. We&#039;re investigating..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Sep 2026 06:37:00 +0000</pubDate>
  <link>https://airmarkradio.instatus.com/incident/cmwgvb9e702tf1mo27jixjayy</link>
  <guid>https://airmarkradio.instatus.com/incident/cmwgvb9e702tf1mo27jixjayy</guid>
</item>

<item>
  <title>Storage, Database and Magic Containers Network Maintenance Notice (Sydney)</title>
  <description>
    Type: Maintenance
    Duration: 8 hours

    Affected Components: Edge Shield
    Aug 24, 22:00:07 GMT+0 - Completed - The scheduled maintenance has been completed. Aug 24, 18:12:59 GMT+0 - Identified - Scheduled maintenance is still in progress. We will provide updates as necessary. Aug 24, 14:00:12 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug 24, 13:00:14 GMT+0 - Planned - Maintenance will begin as scheduled in 60 minutes. Aug 21, 12:19:46 GMT+0 - Planned - We will be performing a maintenance to replace a faulty hardware part in our network that will temporarily affect access to files stored in non-replicated storage zones, Magic Container and Database workloads running in Sydney.

Expected Impact
During the maintenance window, requests for files in non-replicated storage zones may result in temporary 5xx errors. Replicated files will remain fully accessible.

For Magic Containers and Bunny Database, single-location workloads in Sydney will experience a period of unavailability.

Maintenance Window
Date: August 24th
Time: 14:00 - 22:00 (UTC +0)
Expected Impact Duration: Up to 60 minutes 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 8 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>22:00:07</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>18:12:59</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is still in progress. We will provide updates as necessary..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>14:00:12</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>13:00:14</var> GMT+0</small><br><strong>Planned</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>12:19:46</var> GMT+0</small><br><strong>Planned</strong> -
  We will be performing a maintenance to replace a faulty hardware part in our network that will temporarily affect access to files stored in non-replicated storage zones, Magic Container and Database workloads running in Sydney.

Expected Impact
During the maintenance window, requests for files in non-replicated storage zones may result in temporary 5xx errors. Replicated files will remain fully accessible.

For Magic Containers and Bunny Database, single-location workloads in Sydney will experience a period of unavailability.

Maintenance Window
Date: August 24th
Time: 14:00 - 22:00 (UTC +0)
Expected Impact Duration: Up to 60 minutes.</p>
]]>
  </content:encoded>
  <pubDate>Mon, 24 Aug 2026 14:00:00 +0000</pubDate>
  <link>https://airmarkradio.instatus.com/maintenance/cmwfcn42s01se1bq9n3swpopj</link>
  <guid>https://airmarkradio.instatus.com/maintenance/cmwfcn42s01se1bq9n3swpopj</guid>
</item>

<item>
  <title>Issue with Logins and Payments Acceptance</title>
  <description>
    Type: Incident
    Duration: 10 hours

    Affected Components: Payment Processing, Refunds
    Aug 17, 07:27:00 GMT+0 - Resolved - The issue has been fixed.

SumUp services have returned to normal. You can stay up to date on the status of our services anytime here on our status page: https://status.sumup.com. Aug 17, 07:17:00 GMT+0 - Identified - Issue identified, we&#039;re working on a fix right now.

Our engineering team has identified an issue affecting logins and payments, and is working to return our services to normal. You can stay up to date here on our status page: https://status.sumup.com. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>07:27:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue has been fixed.

SumUp services have returned to normal. You can stay up to date on the status of our services anytime here on our status page: https://status.sumup.com..</p>
<p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>07:17:00</var> GMT+0</small><br><strong>Identified</strong> -
  Issue identified, we&#039;re working on a fix right now.

Our engineering team has identified an issue affecting logins and payments, and is working to return our services to normal. You can stay up to date here on our status page: https://status.sumup.com..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 17 Aug 2026 07:17:00 +0000</pubDate>
  <link>https://airmarkradio.instatus.com/incident/cmwgil5la00860wqphz6deqit</link>
  <guid>https://airmarkradio.instatus.com/incident/cmwgil5la00860wqphz6deqit</guid>
</item>

  </channel>
  </rss>