<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.battleground.com.au,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.battleground.com.au"/>
  <link rel="self" type="application/atom+xml" href="https://status.battleground.com.au/history.atom"/>
  <title>Battleground Live Status - Incident history</title>
  <updated>2026-09-09T17:47:18.436+00:00</updated>
  <author>
    <name>Battleground Live</name>
  </author>
  
<entry>
  <id>tag:status.battleground.com.au,2005:Incident/cmtue7f9c6i2k0rqj7adaalqd</id>
  <published>2026-09-09T17:47:18.436+00:00</published>
  <updated>2026-09-09T17:47:18.495+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.battleground.com.au/incident/cmtue7f9c6i2k0rqj7adaalqd"/>
  <title>Messaging Services Message Send Failures</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Twilio (SMS provider)</p>
    <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>17:47:18</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our engineers have investigated and resolved an issue with Messaging Services. From 10:28AM PDT on Tuesday, 7/21/26 to 6:00PM PDT on Friday, 9/4/26, customers may have experienced HTTP 400 responses with Twilio error code 21620 when sending messages through Messaging Services if the media URL parameter contained a comma. The issue has been resolved and all impacted services are operating normally..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.battleground.com.au,2005:Incident/cmt0unt0m41yz0rmgxy3jfhte</id>
  <published>2026-06-18T20:11:51.999+00:00</published>
  <updated>2026-06-18T21:53:47.705+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.battleground.com.au/incident/cmt0unt0m41yz0rmgxy3jfhte"/>
  <title>Send Pipeline Latency</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 21 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> Courier (Touchbase SMS and Push)</p>
    <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>21:53:47</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Messages are being processed while our pipeline continues to process enqueued messages..</p>
<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>20:11:52</var> GMT+0</small><br /><strong>Identified</strong> -
  The team has identified a regression causing send requests to be stuck in a queued state. We have initiated a rollback to quickly resolve the issue. More updates to follow.</p>
<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>20:35:18</var> GMT+0</small><br /><strong>Identified</strong> -
  The rollback deploy will land in about 30 minutes..</p>
<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>21:31:00</var> GMT+0</small><br /><strong>Identified</strong> -
  The team has identified that the most recent deployment was not the cause of the regression. The team is still working on identifying the root cause. Messages will not be dropped, and they will be processed once the fix is out..</p>
<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>22:09:09</var> GMT+0</small><br /><strong>Resolved</strong> -
  Send pipeline has resolved and enqueued messages are now sending properly..</p>

        ]]>
  </content>
</entry>

</feed>