<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.skyslope.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.skyslope.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.skyslope.com/history.atom"/>
  <title>SkySlope Status - Incident history</title>
  <updated>2026-05-26T20:07:00.000+00:00</updated>
  <author>
    <name>SkySlope</name>
  </author>
  
<entry>
  <id>tag:status.skyslope.com,2005:Incident/cmpn3nsz303rgpfoyrm56frwk</id>
  <published>2026-05-26T20:07:00.000+00:00</published>
  <updated>2026-05-26T20:07:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.skyslope.com/incident/cmpn3nsz303rgpfoyrm56frwk"/>
  <title>SkySlope DigiSign degraded performance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> Forms, DigiSign</p>
    <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>20:07:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>20:24:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>21:07:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Beginning at approximately 13:07 PDT on May 26, 2026, users experienced degraded performance in our DigiSign and Forms applications. The incident was caused by a configuration change that introduced elevated error rates on down stream services. Application health was restored after increasing capacity on the relevant systems. Incident declared resolve at 14:07 PDT..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.skyslope.com,2005:Incident/cmpcwtcd501txqtou9296d3ay</id>
  <published>2026-04-16T01:01:00.000+00:00</published>
  <updated>2026-04-16T01:01:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.skyslope.com/incident/cmpcwtcd501txqtou9296d3ay"/>
  <title>SkySlope Forms Unavailable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 29 minutes</p>
    <p><strong>Affected Components:</strong> Forms</p>
    <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>01:01:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating reports that users are unable to load Forms at [forms.skyslope.com](http://forms.skyslope.com)..</p>
<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>01:32:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the cause and are working on implementing a solution..</p>
<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>02:04:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>02:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  On April 15, 2026 between 18:01 PDT and 19:04 PDT, users were unable to load SkySlope Forms at [forms.skyslope.com](http://forms.skyslope.com). Customers reported errors and white screens, and our synthetic monitoring and observability metrics confirmed elevated issues. This was caused by a configuration deployment that broke the path to Forms. The change was reverted within minutes, but routing did not immediately recover. We resolved the incident by applying a follow-up change that allowed our infrastructure to fully reconcile, restoring traffic to a healthy state..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.skyslope.com,2005:Incident/cmpcuna7l018sqtp1tmdn1wz4</id>
  <published>2026-03-31T13:01:00.000+00:00</published>
  <updated>2026-03-31T13:23:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.skyslope.com/incident/cmpcuna7l018sqtp1tmdn1wz4"/>
  <title>Books unavailable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> Books</p>
    <p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>13:23:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  On March 31, 2026 between 06:01 PDT and 06:22 PDT (March 31), users were unable to access SkySlope Books at [books.skyslope.com](http://books.skyslope.com). Customers reported that the application would not load and sign-in attempts failed. The root cause was a recent configuration change that removed the network path to Books. The underlying application and databases remained healthy throughout, and no customer data was lost or exposed. Service was restored after our teams corrected the affected routing configuration and confirmed normal traffic flow to the application..</p>
<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>13:01:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating reports users are unable to access SkySlope Books..</p>
<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>13:22:01</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>

        ]]>
  </content>
</entry>

</feed>