<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:airmarkradio.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://airmarkradio.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://airmarkradio.instatus.com/history.atom"/>
  <title>Airmark Radio Status - Incident history</title>
  <updated>2026-11-11T15:32:10.120+00:00</updated>
  <author>
    <name>Airmark Radio</name>
  </author>
  
<entry>
  <id>tag:airmarkradio.instatus.com,2005:Incident/cmwfcn2yn01sd1bq9435im12h</id>
  <published>2026-11-11T15:32:10.120+00:00</published>
  <updated>2026-11-11T16:15:41.392+00:00</updated>
  <link rel="alternate" type="text/html" href="https://airmarkradio.instatus.com/incident/cmwfcn2yn01sd1bq9435im12h"/>
  <title>Shield Zone Update Failures</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 19 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> Edge Shield</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>
</entry>

<entry>
  <id>tag:airmarkradio.instatus.com,2005:Maintenance/cmwfcn42s01se1bq9n3swpopj</id>
  <published>2026-08-24T14:00:00.000+00:00</published>
  <updated>2026-08-24T22:00:07.478+00:00</updated>
  <link rel="alternate" type="text/html" href="https://airmarkradio.instatus.com/maintenance/cmwfcn42s01se1bq9n3swpopj"/>
  <title>Storage, Database and Magic Containers Network Maintenance Notice (Sydney)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 8 hours</p>
    <p><strong>Affected Components:</strong> Edge Shield</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>
</entry>

<entry>
  <id>tag:airmarkradio.instatus.com,2005:Incident/cmwgil5la00860wqphz6deqit</id>
  <published>2026-08-17T07:17:00.000+00:00</published>
  <updated>2026-08-17T07:27:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://airmarkradio.instatus.com/incident/cmwgil5la00860wqphz6deqit"/>
  <title>Issue with Logins and Payments Acceptance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours</p>
    <p><strong>Affected Components:</strong> Payment Processing, Refunds</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>
</entry>

</feed>