<?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>Battleground Live Status - Incident history</title>
    <link>https://status.battleground.com.au</link>
    <description>Battleground Live</description>
    <pubDate>Wed, 9 Sep 2026 17:47:18 +0000</pubDate>
    
<item>
  <title>Messaging Services Message Send Failures</title>
  <description>
    Type: Incident
    

    Affected Components: Twilio (SMS provider)
    Sep 9, 17:47:18 GMT+0 - Resolved - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:47:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 9 Sep 2026 17:47:18 +0000</pubDate>
  <link>https://status.battleground.com.au/incident/cmtue7f9c6i2k0rqj7adaalqd</link>
  <guid>https://status.battleground.com.au/incident/cmtue7f9c6i2k0rqj7adaalqd</guid>
</item>

<item>
  <title>Send Pipeline Latency</title>
  <description>
    Type: Incident
    Duration: 4 days, 21 hours and 17 minutes

    Affected Components: Courier (Touchbase SMS and Push)
    Jun 18, 21:53:47 GMT+0 - Monitoring - Messages are being processed while our pipeline continues to process enqueued messages. Jun 18, 20:11:52 GMT+0 - Identified - 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 Jun 18, 20:35:18 GMT+0 - Identified - The rollback deploy will land in about 30 minutes. Jun 18, 21:31:00 GMT+0 - Identified - 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. Jun 18, 22:09:09 GMT+0 - Resolved - Send pipeline has resolved and enqueued messages are now sending properly. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 21 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:53:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Messages are being processed while our pipeline continues to process enqueued messages..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:11:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:35:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The rollback deploy will land in about 30 minutes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:31:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:09:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Send pipeline has resolved and enqueued messages are now sending properly..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 18 Jun 2026 20:11:51 +0000</pubDate>
  <link>https://status.battleground.com.au/incident/cmt0unt0m41yz0rmgxy3jfhte</link>
  <guid>https://status.battleground.com.au/incident/cmt0unt0m41yz0rmgxy3jfhte</guid>
</item>

  </channel>
  </rss>