<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.gracopulse.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.gracopulse.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.gracopulse.com/history.atom"/>
  <title>Graco Status - Incident history</title>
  <updated>2026-09-22T13:13:00.000+00:00</updated>
  <author>
    <name>Graco</name>
  </author>
  
<entry>
  <id>tag:status.gracopulse.com,2005:Incident/cmucpnpyc00gw13nziu2cg21p</id>
  <published>2026-09-22T13:13:00.000+00:00</published>
  <updated>2026-09-25T14:48:27.823+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.gracopulse.com/incident/cmucpnpyc00gw13nziu2cg21p"/>
  <title>Pulse Level - Cellular Device Comm Errors</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours</p>
    <p><strong>Affected Components:</strong> 1nce NB-IoT Network, Pulse Pro TLM Data Ingestion Endpoint, Pulse Level Telemetry Ingestion Endpoint, Aeris Fusion North America IoT Service, Aeris Fusion Global IoT Service, User REST API, Tank Monitoring Dashboard</p>
    <p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>14:48:27</var> GMT+0</small><br /><strong>Postmortem</strong> -
  **Incident: Pulse Level Communication Errors**

**Impact**

Beginning at approximately 8:25 PM CDT on Sunday, September 20, the Pulse Level platform experienced a service disruption that affected device communication processing. As a result, updates from connected TLM devices were delayed until service was restored.

**Detection**

The issue was identified on Tuesday, September 22, following customer reports of communication-related issues. These reports initiated an investigation by our engineering team.

**Resolution**

Service was fully restored at 1:07 PM CDT after the underlying processing issue was identified and corrected. Following restoration, engineering teams verified normal system operation and confirmed that device communications were again being processed as expected.

**Root Cause**

The disruption was caused by an unexpected service interruption within the cloud-hosted infrastructure supporting device communications. The condition prevented communication data from being processed until corrective action was taken.

**Corrective Actions**

* Enhanced monitoring and alerting have been implemented to improve detection and response time for similar service interruptions.
* Additional resiliency improvements are being implemented to increase service availability and reduce the likelihood and impact of future disruptions.
* Recovery procedures have been strengthened to support faster restoration of service should a similar event occur..</p>
<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>18:29:53</var> GMT+0</small><br /><strong>Resolved</strong> -
  Service has been restored, and systems are currently returning to normal operation.

Users are encouraged to monitor their devices and data over the next several hours as system performance stabilizes. Please note that new readings may take up to **24 hours** to report and appear within the application..</p>
<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>13:13:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.gracopulse.com,2005:Incident/cmtun6s68014l07qyxasounia</id>
  <published>2026-09-09T22:00:29.759+00:00</published>
  <updated>2026-09-10T12:29:53.062+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.gracopulse.com/incident/cmtun6s68014l07qyxasounia"/>
  <title>Aeris Fusion NA IoT Service has Returned to Operational Status</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Aeris Fusion North America IoT Service</p>
    <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>12:29:53</var> GMT+0</small><br /><strong>Postmortem</strong> -
  This incident has been resolved. See Aeris incident case number 186030 for details:

&lt;https://caas.status.aeris.net/incidents/btv90rz27gdz&gt;.</p>
<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>22:00:29</var> GMT+0</small><br /><strong>Investigating</strong> -
  This incident was automatically created by Instatus monitoring. Additional updates will be provided as they come in..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>04:30:57</var> GMT+0</small><br /><strong>Resolved</strong> -
  This issue has been resolved. Automated monitoring has confirmed that the operational status has returned to normal. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.gracopulse.com,2005:Incident/cmtun6p5k02b507nvu23mygbj</id>
  <published>2026-09-09T22:00:25.595+00:00</published>
  <updated>2026-09-10T12:31:10.126+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.gracopulse.com/incident/cmtun6p5k02b507nvu23mygbj"/>
  <title>Aeris Fusion Global IoT Service has Returned to Operational Status</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Aeris Fusion Global IoT Service</p>
    <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>12:31:10</var> GMT+0</small><br /><strong>Postmortem</strong> -
  This incident has been resolved. See Aeris incident case number 186030 for details:

&lt;https://caas.status.aeris.net/incidents/btv90rz27gdz&gt;.</p>
<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>22:00:25</var> GMT+0</small><br /><strong>Investigating</strong> -
  This incident was automatically created by Instatus monitoring. Additional updates will be provided as they come in..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>04:28:24</var> GMT+0</small><br /><strong>Resolved</strong> -
  This issue has been resolved. Automated monitoring has confirmed that the operational status has returned to normal. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.gracopulse.com,2005:Incident/cmtufk0zz0mqq1fpqcli1ybeo</id>
  <published>2026-07-08T21:27:00.000+00:00</published>
  <updated>2026-07-09T16:03:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.gracopulse.com/incident/cmtufk0zz0mqq1fpqcli1ybeo"/>
  <title>Third Party Interface Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 hours and 36 minutes</p>
    <p><strong>Affected Components:</strong> Third Party Connector Service</p>
    <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>16:03:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. 

The outage was caused by an issue within our cloud infrastructure that prevented a service component from restarting correctly following routine maintenance activities. To prevent a similar issue from occurring in the future, we have implemented immediate safeguards and are making additional improvements to our deployment and retention processes. These changes will ensure that required service components remain available during maintenance and system updates..</p>
<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>21:27:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>

        ]]>
  </content>
</entry>

</feed>