<?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>Skribble AG Status - Incident history</title>
    <link>https://status.skribble.com</link>
    <description>Skribble AG</description>
    <pubDate>Sat, 10 Oct 2026 07:00:00 +0000</pubDate>
    
<item>
  <title>Scheduled maintenance by Swisscom – 10/11 October 2026</title>
  <description>
    Type: Maintenance
    

    Affected Components: Swisscom Trust Services
    Oct 5, 07:46:45 GMT+0 - Identified - Our trust service provider Swisscom will carry out scheduled maintenance on its signing platform from Saturday, 10 October 2026, 22:00 to Sunday, 11 October 2026, 06:00 (CEST). During this time, signing and identification may be unavailable or only partly available. You don&#039;t need to do anything. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:46:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our trust service provider Swisscom will carry out scheduled maintenance on its signing platform from Saturday, 10 October 2026, 22:00 to Sunday, 11 October 2026, 06:00 (CEST). During this time, signing and identification may be unavailable or only partly available. You don&#039;t need to do anything..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 10 Oct 2026 07:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmuuy502k016z0wjwtoqe9jdv</link>
  <guid>https://status.skribble.com/maintenance/cmuuy502k016z0wjwtoqe9jdv</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Oct 5, 07:35:29 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Oct 6, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 6, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:35:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 6 Oct 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmuuxqidb031x0wlp5s10r3aw</link>
  <guid>https://status.skribble.com/maintenance/cmuuxqidb031x0wlp5s10r3aw</guid>
</item>

<item>
  <title>Issues with QES Identifications</title>
  <description>
    Type: Incident
    Duration: 1 hour and 23 minutes

    Affected Components: Skribble Platform CH, Skribble Platform DE
    Oct 6, 09:23:58 GMT+0 - Investigating - Our identification partner for QES identifications has reported an issue affecting their services.

As a result, users may experience errors or difficulties when completing an identification. If you encounter any issues, we recommend trying the identification again later.

Our partner is investigating the issue, and we are closely monitoring the situation. We will provide an update as soon as more information becomes available. Oct 6, 09:38:02 GMT+0 - Monitoring - Our identification partner has informed us that the previously reported issues **should now be resolved.**

QES identifications should be working as expected again. We will continue to monitor the situation and provide a final update shortly.

If you are still experiencing any issues, please contact our support team at [support@skribble.com](mailto:support@skribble.com). Oct 6, 10:47:14 GMT+0 - Resolved - The issue with QES identifications has been resolved.

Following our previous update, we continued to monitor the situation and have not received any further reports of issues from customers. We therefore consider this incident resolved.

If you are still experiencing any issues, please contact our support team at [support@skribble.com](mailto:support@skribble.com). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 23 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:23:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Our identification partner for QES identifications has reported an issue affecting their services.

As a result, users may experience errors or difficulties when completing an identification. If you encounter any issues, we recommend trying the identification again later.

Our partner is investigating the issue, and we are closely monitoring the situation. We will provide an update as soon as more information becomes available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:38:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Our identification partner has informed us that the previously reported issues **should now be resolved.**

QES identifications should be working as expected again. We will continue to monitor the situation and provide a final update shortly.

If you are still experiencing any issues, please contact our support team at [support@skribble.com](mailto:support@skribble.com)..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:47:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue with QES identifications has been resolved.

Following our previous update, we continued to monitor the situation and have not received any further reports of issues from customers. We therefore consider this incident resolved.

If you are still experiencing any issues, please contact our support team at [support@skribble.com](mailto:support@skribble.com)..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 6 Oct 2026 09:23:58 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmuwh1vn70grc0wlpkbhlsh3w</link>
  <guid>https://status.skribble.com/incident/cmuwh1vn70grc0wlpkbhlsh3w</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Sep 28, 07:31:09 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Sep 29, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 29, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:31:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 29 Sep 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmukxhytj06nv13qt9te2eq6n</link>
  <guid>https://status.skribble.com/maintenance/cmukxhytj06nv13qt9te2eq6n</guid>
</item>

<item>
  <title>DE platform only: Platform unavailable</title>
  <description>
    Type: Incident
    Duration: 4 hours and 58 minutes

    Affected Components: Skribble Platform DE, Skribble API DE, Skribble Document Validation API DE
    Sep 29, 06:30:08 GMT+0 - Investigating - We are currently investigating an issue in context with IONOS managed service used by our German platform.

The German platform is currently unavailable. We a investigating. 

We apologize for any inconvenience this may cause. Sep 29, 07:21:08 GMT+0 - Investigating - IONOS is reporting that [Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations](https://status.ionos.cloud/incidents/zprjxl2b1kmy) Sep 29, 08:42:55 GMT+0 - Monitoring - Although IONOS has not yet issued an all-clear, the system appears to be stabilizing again. 

We will keep monitoring this.  Sep 29, 11:28:11 GMT+0 - Resolved - A fix has been implemented by IONOS. This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 58 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:30:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an issue in context with IONOS managed service used by our German platform.

The German platform is currently unavailable. We a investigating. 

We apologize for any inconvenience this may cause..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:21:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  IONOS is reporting that [Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations](https://status.ionos.cloud/incidents/zprjxl2b1kmy).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:42:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Although IONOS has not yet issued an all-clear, the system appears to be stabilizing again. 

We will keep monitoring this. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:28:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  A fix has been implemented by IONOS. This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 29 Sep 2026 06:30:08 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmumdrkui02m10wob4f2hkt9s</link>
  <guid>https://status.skribble.com/incident/cmumdrkui02m10wob4f2hkt9s</guid>
</item>

<item>
  <title>Skribble unscheduled maintenance on German platform</title>
  <description>
    Type: Maintenance
    Duration: 20 minutes

    Affected Components: Skribble Platform DE, Skribble API DE
    Sep 23, 08:57:51 GMT+0 - Identified - We are planning for a unscheduled maintenance on the German platform during that time. The login functionality might be shortly interrupted. Sep 24, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 24, 18:20:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:57:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a unscheduled maintenance on the German platform during that time. The login functionality might be shortly interrupted..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmudve7sw00uy1bqh2xdl5429</link>
  <guid>https://status.skribble.com/maintenance/cmudve7sw00uy1bqh2xdl5429</guid>
</item>

<item>
  <title>DE Only: Issues with DNS resolving swisscom.com </title>
  <description>
    Type: Incident
    Duration: 1 hour and 21 minutes

    Affected Components: Swisscom Trust Services, Skribble Platform DE, Skribble API DE
    Sep 24, 13:30:18 GMT+0 - Monitoring - We are currently experiencing DNS service issues in our IONOS datacenter. The issue affects [skribble.de](http://skribble.de) and is primarily impacting signing with Swisscom TSP.

We are monitoring the DNS issues and will provide updates as the situation develops. Sep 24, 14:50:55 GMT+0 - Resolved - The issue has been resolved. We temporarily switched to alternative DNS servers to restore normal service.  

We will continue to monitor the situation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 21 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:30:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are currently experiencing DNS service issues in our IONOS datacenter. The issue affects [skribble.de](http://skribble.de) and is primarily impacting signing with Swisscom TSP.

We are monitoring the DNS issues and will provide updates as the situation develops..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:50:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been resolved. We temporarily switched to alternative DNS servers to restore normal service.  

We will continue to monitor the situation..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 13:30:18 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmufn7z0j01qm1bqneie1k7s2</link>
  <guid>https://status.skribble.com/incident/cmufn7z0j01qm1bqneie1k7s2</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Sep 21, 07:24:11 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Sep 22, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 22, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:24:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 22 Sep 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmuax620w1epe13pcdfatecng</link>
  <guid>https://status.skribble.com/maintenance/cmuax620w1epe13pcdfatecng</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Sep 14, 07:22:26 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Sep 15, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 15, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:22:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 15 Sep 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmu0x0u4r09h21boanorj31pu</link>
  <guid>https://status.skribble.com/maintenance/cmu0x0u4r09h21boanorj31pu</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Skribble Platform CH, Skribble Platform DE, Skribble API DE, Skribble API CH, Skribble UI
    Sep 7, 07:21:05 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Sep 8, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 8, 20:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:21:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 8 Sep 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmtqww55h04ef1moa9xqbqwkv</link>
  <guid>https://status.skribble.com/maintenance/cmtqww55h04ef1moa9xqbqwkv</guid>
</item>

<item>
  <title>Skribble CH unavailable – Service Disruption</title>
  <description>
    Type: Incident
    Duration: 3 hours and 15 minutes

    Affected Components: Skribble Document Validation API CH, CloudScale, Skribble Platform CH, Skribble API CH, VSHN
    Sep 4, 06:21:19 GMT+0 - Investigating - We are currently experiencing an issue affecting our platform, making it temporarily unavailable. Our engineering team is actively investigating the root cause to restore service as quickly as possible. Currently investigating this incident. Sep 4, 06:57:30 GMT+0 - Identified - Our cloud infrastructure provider is currently investigating failures affecting multiple Linux nodes. We are monitoring the situation and will provide updates as more information becomes available.  
  
&lt;https://www.cloudscale-status.net/incidents/247957&gt; Sep 4, 07:26:18 GMT+0 - Identified - **Update:** We have identified the root cause as an update by our cloud infrastructure provider that caused multiple Linux nodes to fail.

We are currently restoring the platform on new nodes. The platform remains unavailable at this time.

We will provide another update as soon as the platform is restored. Sep 4, 08:26:22 GMT+0 - Monitoring - Update: Our attempt to restore the platform on new nodes was unsuccessful due to the underlying storage issues within the Kubernetes cluster.  

Both of our infrastructure providers are actively working to resolve these issues. The platform remains unavailable at this time.  
\- &lt;https://www.cloudscale-status.net/incidents/247957&gt;  
\- &lt;https://status.vshn.net/incidents/247998&gt;

We will provide another update as soon as we have further information. Sep 4, 09:36:00 GMT+0 - Resolved - This incident has been resolved.  
  
The issue affecting the Skribble platform, caused by scheduled security maintenance at our infrastructure provider, has been fixed. If you still experience issues, please log out and log back in. We apologise for the inconvenience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:21:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing an issue affecting our platform, making it temporarily unavailable. Our engineering team is actively investigating the root cause to restore service as quickly as possible. Currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:57:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our cloud infrastructure provider is currently investigating failures affecting multiple Linux nodes. We are monitoring the situation and will provide updates as more information becomes available.  
  
&lt;https://www.cloudscale-status.net/incidents/247957&gt;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:26:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  **Update:** We have identified the root cause as an update by our cloud infrastructure provider that caused multiple Linux nodes to fail.

We are currently restoring the platform on new nodes. The platform remains unavailable at this time.

We will provide another update as soon as the platform is restored..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:26:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Update: Our attempt to restore the platform on new nodes was unsuccessful due to the underlying storage issues within the Kubernetes cluster.  

Both of our infrastructure providers are actively working to resolve these issues. The platform remains unavailable at this time.  
\- &lt;https://www.cloudscale-status.net/incidents/247957&gt;  
\- &lt;https://status.vshn.net/incidents/247998&gt;

We will provide another update as soon as we have further information..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:36:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved.  
  
The issue affecting the Skribble platform, caused by scheduled security maintenance at our infrastructure provider, has been fixed. If you still experience issues, please log out and log back in. We apologise for the inconvenience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 4 Sep 2026 06:21:19 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmtmkfqvk07qd1no52anl6f55</link>
  <guid>https://status.skribble.com/incident/cmtmkfqvk07qd1no52anl6f55</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Sep 1, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 1, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully Aug 31, 07:19:51 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:19:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 1 Sep 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmtgwrl3504071bs3d0di9zoc</link>
  <guid>https://status.skribble.com/maintenance/cmtgwrl3504071bs3d0di9zoc</guid>
</item>

<item>
  <title>Scheduled maintenance: identity service update ( DE platform )</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Skribble Platform DE, Skribble API DE
    Aug 26, 14:54:15 GMT+0 - Identified - We will perform a scheduled security update of our login and identity service. During the maintenance window, sign-ins and account-related actions may be briefly unavailable. Aug 26, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 26, 20:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:54:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will perform a scheduled security update of our login and identity service. During the maintenance window, sign-ins and account-related actions may be briefly unavailable..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 26 Aug 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmta7sok108t01blgs3wiixi7</link>
  <guid>https://status.skribble.com/maintenance/cmta7sok108t01blgs3wiixi7</guid>
</item>

<item>
  <title>Intermittent Platform Errors Following Infrastructure Maintenance</title>
  <description>
    Type: Incident
    

    Affected Components: Skribble Document Validation API CH, Skribble API CH, Skribble Platform CH
    Aug 25, 20:00:00 GMT+0 - Resolved - On August 25, scheduled infrastructure maintenance was performed on parts of our messaging infrastructure. While the maintenance itself completed successfully, some application components did not properly restore their connections afterward.

As a result, certain operations on the Skribble platform, including signing and accessing signed documents, could fail with an error. The impact increased as traffic picked up the following morning.

We identified the affected components and restored their connections, returning the platform to normal operation.

We are reviewing our connection recovery mechanisms to ensure application components automatically and reliably reconnect after similar infrastructure maintenance in the future. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  On August 25, scheduled infrastructure maintenance was performed on parts of our messaging infrastructure. While the maintenance itself completed successfully, some application components did not properly restore their connections afterward.

As a result, certain operations on the Skribble platform, including signing and accessing signed documents, could fail with an error. The impact increased as traffic picked up the following morning.

We identified the affected components and restored their connections, returning the platform to normal operation.

We are reviewing our connection recovery mechanisms to ensure application components automatically and reliably reconnect after similar infrastructure maintenance in the future..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 25 Aug 2026 20:00:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmt9trvst05y01blg1udkrjfm</link>
  <guid>https://status.skribble.com/incident/cmt9trvst05y01blg1udkrjfm</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble API CH, Skribble Platform CH
    Aug 24, 07:25:27 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Aug 25, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 25, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:25:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 25 Aug 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmt6wvtih1atd1aplaw8kgvn1</link>
  <guid>https://status.skribble.com/maintenance/cmt6wvtih1atd1aplaw8kgvn1</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Aug 17, 07:22:41 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Aug 18, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 18, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:22:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Aug 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmswwpan410vp0zqx7lixlirk</link>
  <guid>https://status.skribble.com/maintenance/cmswwpan410vp0zqx7lixlirk</guid>
</item>

<item>
  <title>Issues with QES signing</title>
  <description>
    Type: Incident
    Duration: 15 hours

    Affected Components: Skribble Platform CH
    Aug 12, 15:12:32 GMT+0 - Investigating - We are currently experiencing issues with the qualified electronic signature (QES). Some users may incorrectly be asked to upgrade their signature quality or repeat their identification, even though their identification is valid — **no re-identification is necessary.** 

Signing with other signature qualities (SES/AES) is not affected. 

The issue is caused by a disruption at one of our partners; we are in close contact with them to resolve it as quickly as possible. We will provide an update as soon as the service is fully restored. Aug 12, 15:44:56 GMT+0 - Investigating - We are continuing to work with our partner on resolving this issue. 

Clarification on scope: the disruption affects **both** qualified (QES) and advanced (AES) electronic signatures. Affected users may incorrectly be asked to increase their signature quality, repeat their identification, or purchase an identification — even though their identification is valid. No re-identification or purchase is necessary, and already completed signatures remain fully valid. 

Signing with simple electronic signatures (SES) is not affected. 

We will provide a further update as soon as the service is restored. Aug 13, 06:12:33 GMT+0 - Resolved - The issue affecting qualified (QES) and advanced (AES) electronic signatures has been resolved, and signing is operating normally again.

Users with a valid identification can now sign as expected without being incorrectly prompted to increase their signature quality, repeat their identification, or purchase an identification.

No action is required from affected users. All signatures completed during the incident remain fully valid.

We apologize for the inconvenience and thank you for your patience while we worked to resolve the issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:12:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing issues with the qualified electronic signature (QES). Some users may incorrectly be asked to upgrade their signature quality or repeat their identification, even though their identification is valid — **no re-identification is necessary.** 

Signing with other signature qualities (SES/AES) is not affected. 

The issue is caused by a disruption at one of our partners; we are in close contact with them to resolve it as quickly as possible. We will provide an update as soon as the service is fully restored..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:44:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are continuing to work with our partner on resolving this issue. 

Clarification on scope: the disruption affects **both** qualified (QES) and advanced (AES) electronic signatures. Affected users may incorrectly be asked to increase their signature quality, repeat their identification, or purchase an identification — even though their identification is valid. No re-identification or purchase is necessary, and already completed signatures remain fully valid. 

Signing with simple electronic signatures (SES) is not affected. 

We will provide a further update as soon as the service is restored..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:12:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue affecting qualified (QES) and advanced (AES) electronic signatures has been resolved, and signing is operating normally again.

Users with a valid identification can now sign as expected without being incorrectly prompted to increase their signature quality, repeat their identification, or purchase an identification.

No action is required from affected users. All signatures completed during the incident remain fully valid.

We apologize for the inconvenience and thank you for your patience while we worked to resolve the issue..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 12 Aug 2026 15:12:32 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmsq8aaii009e1aqimnaeuts7</link>
  <guid>https://status.skribble.com/incident/cmsq8aaii009e1aqimnaeuts7</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Aug 10, 07:33:49 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Aug 11, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 11, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:33:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 11 Aug 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmsmx0nz30ipq0rrpob58dmn0</link>
  <guid>https://status.skribble.com/maintenance/cmsmx0nz30ipq0rrpob58dmn0</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Aug 3, 08:10:04 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Aug 4, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 4, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:10:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 4 Aug 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmscy8bih07xb0rl8bk73xuij</link>
  <guid>https://status.skribble.com/maintenance/cmscy8bih07xb0rl8bk73xuij</guid>
</item>

<item>
  <title>Skribble unscheduled maintenance on German platform</title>
  <description>
    Type: Maintenance
    Duration: 5 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Jul 29, 15:38:58 GMT+0 - Identified - We are planning for a unscheduled maintenance on the German platform during that time. The login functionality might be shortly interrupted. Jul 30, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 30, 18:05:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:38:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a unscheduled maintenance on the German platform during that time. The login functionality might be shortly interrupted..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 30 Jul 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cms692c5u04hz0rpa5g8dro98</link>
  <guid>https://status.skribble.com/maintenance/cms692c5u04hz0rpa5g8dro98</guid>
</item>

<item>
  <title>Planned Maintenance: Update Login Experience for German platform (skribble.de)</title>
  <description>
    Type: Maintenance
    Duration: 3 hours and 36 minutes

    Affected Components: Skribble Document Validation API CH, Identification Shop, Skribble Platform CH, Skribble API CH, Skribble UI
    Jul 24, 13:40:22 GMT+0 - Identified - ### Notice for customers of our German platform ([skribble.de](http://skribble.de)).

During this scheduled maintenance window, we will introduce an update to the login process.

Going forward, logins and account registrations will be handled by our central, modernised authentication service. 

This change is an important technical improvement that further enhances the security, stability and future-readiness of the platform.

### What does this mean for you?

For most users, no action is required. You will simply notice a slightly updated login and signup experience. The signing experience and all other platform functionality remain unchanged.

### Note for customers using SSO or OIDC integrations on the German platform

The authentication flow will now be handled directly by our authentication service. Existing integrations are expected to continue working without any changes. 

However, if you have implemented custom authentication logic or rely on hardcoded login URLs, we recommend validating your configuration after the maintenance window.

**Thank you for your understanding** — we are continuously working to improve the security and reliability of the Skribble platform.  
  
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

### Hinweis für Kundinnen und Kunden unserer deutschen Plattform ([skribble.de](http://skribble.de)).

Im Rahmen des geplanten Wartungsfensters führen wir eine Aktualisierung des Anmeldeprozesses ein.

Anmeldungen und Registrierungen erfolgen künftig über unseren zentralen,modernisierten Anmeldedienst. 

Diese Umstellung ist eine wichtige technische Weiterentwicklung, die die Sicherheit, Stabilität und Zukunftsfähigkeit der Plattform weiter verbessert.

### Was bedeutet das für Sie?

Für die meisten Nutzerinnen und Nutzer ist keine Aktion erforderlich. Sie werden lediglich eine leicht angepasste Login- und

Registrierungsseite bemerken. Das Signieren sowie alle weiteren Funktionen der Plattform bleiben unverändert. 

### Hinweis für Kunden mit SSO- oder OIDC-Integration auf der deutschen Plattform

Der Authentifizierungsablauf wird künftig direkt von unserem Anmeldedienst abgewickelt. Bestehende Integrationen funktionieren

voraussichtlich ohne Anpassung weiter. 

Sollten Sie jedoch eigene Authentifizierungslogik implementiert haben oder fest hinterlegte Login-URLs verwenden, empfehlen wir, Ihre Konfiguration nach dem Wartungsfenster zu überprüfen.

**Vielen Dank für Ihr Verständnis** — wir arbeiten kontinuierlich daran,die Sicherheit und Zuverlässigkeit der Skribble-Plattform zu verbessern. Jul 28, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 28, 21:35:46 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours and 36 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:40:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  ### Notice for customers of our German platform ([skribble.de](http://skribble.de)).

During this scheduled maintenance window, we will introduce an update to the login process.

Going forward, logins and account registrations will be handled by our central, modernised authentication service. 

This change is an important technical improvement that further enhances the security, stability and future-readiness of the platform.

### What does this mean for you?

For most users, no action is required. You will simply notice a slightly updated login and signup experience. The signing experience and all other platform functionality remain unchanged.

### Note for customers using SSO or OIDC integrations on the German platform

The authentication flow will now be handled directly by our authentication service. Existing integrations are expected to continue working without any changes. 

However, if you have implemented custom authentication logic or rely on hardcoded login URLs, we recommend validating your configuration after the maintenance window.

**Thank you for your understanding** — we are continuously working to improve the security and reliability of the Skribble platform.  
  
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

### Hinweis für Kundinnen und Kunden unserer deutschen Plattform ([skribble.de](http://skribble.de)).

Im Rahmen des geplanten Wartungsfensters führen wir eine Aktualisierung des Anmeldeprozesses ein.

Anmeldungen und Registrierungen erfolgen künftig über unseren zentralen,modernisierten Anmeldedienst. 

Diese Umstellung ist eine wichtige technische Weiterentwicklung, die die Sicherheit, Stabilität und Zukunftsfähigkeit der Plattform weiter verbessert.

### Was bedeutet das für Sie?

Für die meisten Nutzerinnen und Nutzer ist keine Aktion erforderlich. Sie werden lediglich eine leicht angepasste Login- und

Registrierungsseite bemerken. Das Signieren sowie alle weiteren Funktionen der Plattform bleiben unverändert. 

### Hinweis für Kunden mit SSO- oder OIDC-Integration auf der deutschen Plattform

Der Authentifizierungsablauf wird künftig direkt von unserem Anmeldedienst abgewickelt. Bestehende Integrationen funktionieren

voraussichtlich ohne Anpassung weiter. 

Sollten Sie jedoch eigene Authentifizierungslogik implementiert haben oder fest hinterlegte Login-URLs verwenden, empfehlen wir, Ihre Konfiguration nach dem Wartungsfenster zu überprüfen.

**Vielen Dank für Ihr Verständnis** — wir arbeiten kontinuierlich daran,die Sicherheit und Zuverlässigkeit der Skribble-Plattform zu verbessern..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:35:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 28 Jul 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmryzmk2a09ar0zlc66bjbj96</link>
  <guid>https://status.skribble.com/maintenance/cmryzmk2a09ar0zlc66bjbj96</guid>
</item>

<item>
  <title>DE Platform only: Ongoing issues at IONOS</title>
  <description>
    Type: Incident
    Duration: 2 hours and 26 minutes

    Affected Components: Skribble API CH
    Jul 28, 11:47:00 GMT+0 - Investigating - We are currently investigating an ongoing issue affecting the IONOS managed service used by our German platform.

We are in contact with the provider and are monitoring the situation closely. We will provide another update as soon as more information is available or the issue has been resolved.

We apologize for any inconvenience this may cause. Jul 28, 14:02:33 GMT+0 - Monitoring - IONOS is rolling back their changes. We are monitoring the progress.

&lt;https://status.ionos.cloud/incidents/1573fwzccn81&gt; Jul 28, 14:13:09 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 26 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:47:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an ongoing issue affecting the IONOS managed service used by our German platform.

We are in contact with the provider and are monitoring the situation closely. We will provide another update as soon as more information is available or the issue has been resolved.

We apologize for any inconvenience this may cause..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:02:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  IONOS is rolling back their changes. We are monitoring the progress.

&lt;https://status.ionos.cloud/incidents/1573fwzccn81&gt;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:13:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 28 Jul 2026 11:47:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cms4o8hb9093l1cn2407f0cf3</link>
  <guid>https://status.skribble.com/incident/cms4o8hb9093l1cn2407f0cf3</guid>
</item>

<item>
  <title>Urgent Maintenance: Platform Protection Update</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Skribble Platform CH, Skribble API CH
    Jul 23, 13:49:30 GMT+0 - Identified - Today, between **19:00 and 20:00 (Zürich/Berlin time)**, we will perform an unplanned maintenance to deploy additional platform protection measures.  

The maintenance is expected to take **approximately one hour**. Regular customer accounts and normal platform usage are **not expected to be affected**.  

This update is part of our ongoing efforts to enhance the security and reliability of the platform. Jul 23, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 23, 18:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:49:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Today, between **19:00 and 20:00 (Zürich/Berlin time)**, we will perform an unplanned maintenance to deploy additional platform protection measures.  

The maintenance is expected to take **approximately one hour**. Regular customer accounts and normal platform usage are **not expected to be affected**.  

This update is part of our ongoing efforts to enhance the security and reliability of the platform..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 23 Jul 2026 17:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmrxkiga301ff1bk0t2he9lzo</link>
  <guid>https://status.skribble.com/maintenance/cmrxkiga301ff1bk0t2he9lzo</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Jul 21, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully Jul 20, 10:11:07 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Jul 21, 18:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:11:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 21 Jul 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmrt2e25c04p50rqwxtg1stzo</link>
  <guid>https://status.skribble.com/maintenance/cmrt2e25c04p50rqwxtg1stzo</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Jul 13, 08:05:19 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Jul 14, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 14, 19:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:05:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 14 Jul 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmrixtbhc07c50klvtcztdeg2</link>
  <guid>https://status.skribble.com/maintenance/cmrixtbhc07c50klvtcztdeg2</guid>
</item>

<item>
  <title>Document Access Errors Affecting Some Signers</title>
  <description>
    Type: Incident
    Duration: 3 hours and 1 minute

    Affected Components: Skribble Platform CH
    Jul 8, 13:01:27 GMT+0 - Resolved - The issue has been resolved, and our monitoring has confirmed that affected signers can now access documents as expected.

  
**Root Cause**

A recent update to our Identity and Access Management (IAM) system introduced changes that caused unexpected malfunctions in specific scenarios, primarily affecting signers without a Skribble account.

We apologize for any inconvenience this may have caused and thank you for your patience while we resolved the issue. Jul 8, 10:00:00 GMT+0 - Investigating - We are currently investigating an issue where some signers receive an error message when attempting to access a document.

Based on our current findings, the issue primarily affects signers **without a Skribble account**, while signers with an account appear to be largely unaffected.

Our team is actively investigating the root cause and is already implementing potential fixes. We will provide another update as soon as more information becomes available. Jul 8, 12:05:33 GMT+0 - Identified - We have identified the root cause of the issue and are actively working on a resolution.

A potential fix has been implemented, and we are currently monitoring the system to verify that it resolves the issue. We will provide another update once we have confirmed the outcome. Jul 8, 12:31:03 GMT+0 - Monitoring - We are no longer seeing any new occurrences of this issue following the implemented fix.

We will continue to closely monitor the system to ensure the issue has been fully resolved and remains stable. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:01:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been resolved, and our monitoring has confirmed that affected signers can now access documents as expected.

  
**Root Cause**

A recent update to our Identity and Access Management (IAM) system introduced changes that caused unexpected malfunctions in specific scenarios, primarily affecting signers without a Skribble account.

We apologize for any inconvenience this may have caused and thank you for your patience while we resolved the issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an issue where some signers receive an error message when attempting to access a document.

Based on our current findings, the issue primarily affects signers **without a Skribble account**, while signers with an account appear to be largely unaffected.

Our team is actively investigating the root cause and is already implementing potential fixes. We will provide another update as soon as more information becomes available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:05:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the root cause of the issue and are actively working on a resolution.

A potential fix has been implemented, and we are currently monitoring the system to verify that it resolves the issue. We will provide another update once we have confirmed the outcome..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:31:03&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are no longer seeing any new occurrences of this issue following the implemented fix.

We will continue to closely monitor the system to ensure the issue has been fully resolved and remains stable..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 8 Jul 2026 10:00:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmrc06bsw01gk10o6w228d1n8</link>
  <guid>https://status.skribble.com/incident/cmrc06bsw01gk10o6w228d1n8</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 30 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Jul 6, 08:33:19 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Jul 7, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 7, 20:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:33:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 7 Jul 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmr8yqcsw0z5q1amjp10bqoi1</link>
  <guid>https://status.skribble.com/maintenance/cmr8yqcsw0z5q1amjp10bqoi1</guid>
</item>

<item>
  <title>Skribble Authentication System Upgrade</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Skribble Document Validation API CH, Identification Shop, Skribble Platform CH, Skribble API CH, Skribble UI
    Jun 29, 08:41:52 GMT+0 - Identified - We will be performing a scheduled system upgrade on **July 7, 2026**. During this time, we will be updating our identity and access management system to **Keycloak 26.2.0** to bring you improved security, performance, and stability. Jul 7, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 7, 20:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:41:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will be performing a scheduled system upgrade on **July 7, 2026**. During this time, we will be updating our identity and access management system to **Keycloak 26.2.0** to bring you improved security, performance, and stability..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 7 Jul 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmqyyye9a19062omm0ezfxaeh</link>
  <guid>https://status.skribble.com/maintenance/cmqyyye9a19062omm0ezfxaeh</guid>
</item>

<item>
  <title>Skribble DE(Germany) Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Skribble Document Validation API CH, Identification Shop, Skribble Platform CH, Skribble API CH, Skribble UI
    Jul 3, 11:28:06 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jul 6, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 6, 20:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:28:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance during that time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 6 Jul 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmr4unk4j016s1ao4lvkjc2oy</link>
  <guid>https://status.skribble.com/maintenance/cmr4unk4j016s1ao4lvkjc2oy</guid>
</item>

<item>
  <title>SMS Authentication Issues for International Numbers (Resolved)</title>
  <description>
    Type: Incident
    Duration: 1 day, 2 hours and 30 minutes

    Affected Components: Skribble Platform CH
    Jul 2, 04:00:00 GMT+0 - Investigating - We identified an issue affecting SMS authentication for AES signing with non-Swiss mobile numbers. Users with international mobile numbers may not have received SMS authentication codes and may have been unable to complete AES signatures. Jul 3, 06:30:00 GMT+0 - Resolved - SMS authentication for AES signing was unavailable for users with **non-Swiss mobile numbers** during the incident window.

Our SMS authentication provider, **Tyntec**, experienced an issue that prevented SMS delivery to users with non-Swiss mobile numbers.

The issue has been resolved, and SMS authentication is now functioning normally for all supported mobile numbers.

**What you need to do**

If you were unable to complete an AES signature during the affected time period, please retry the signing process. SMS authentication is now working as expected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 2 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We identified an issue affecting SMS authentication for AES signing with non-Swiss mobile numbers. Users with international mobile numbers may not have received SMS authentication codes and may have been unable to complete AES signatures..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  SMS authentication for AES signing was unavailable for users with **non-Swiss mobile numbers** during the incident window.

Our SMS authentication provider, **Tyntec**, experienced an issue that prevented SMS delivery to users with non-Swiss mobile numbers.

The issue has been resolved, and SMS authentication is now functioning normally for all supported mobile numbers.

**What you need to do**

If you were unable to complete an AES signature during the affected time period, please retry the signing process. SMS authentication is now working as expected..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 2 Jul 2026 04:00:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmr4no5a407v11aqfjmmamqpa</link>
  <guid>https://status.skribble.com/incident/cmr4no5a407v11aqfjmmamqpa</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Skribble Document Validation API CH, Skribble Platform CH, Identification Shop, Skribble API CH, Skribble UI
    Jun 30, 20:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jun 30, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance during that time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 30 Jun 2026 20:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmr134pr500fm1amozt6ha8cq</link>
  <guid>https://status.skribble.com/maintenance/cmr134pr500fm1amozt6ha8cq</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 26 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Jun 29, 08:40:47 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Jun 30, 18:00:00 GMT+0 - Identified - Maintenance is now in progress Jun 30, 19:25:54 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 26 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:40:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:25:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 30 Jun 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmqyyx01n01wk2it8x78wpw5m</link>
  <guid>https://status.skribble.com/maintenance/cmqyyx01n01wk2it8x78wpw5m</guid>
</item>

<item>
  <title>Skribble regular maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 54 minutes

    Affected Components: Skribble Platform CH, Skribble API CH, Skribble UI
    Jun 22, 09:04:59 GMT+0 - Identified - Regular maintenance/update of Skribble platform and infrastructure. Jun 22, 09:05:00 GMT+0 - Identified - Maintenance is now in progress Jun 23, 07:07:28 GMT+0 - Identified - Maintenance didn&#039;t start yet. Jun 23, 18:05:30 GMT+0 - Identified - Maintenance is now in progress. Jun 23, 20:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 54 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:04:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Regular maintenance/update of Skribble platform and infrastructure..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:07:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance didn&#039;t start yet..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:05:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 23 Jun 2026 18:00:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmqozp5o2001v2jnwlevqkxq7</link>
  <guid>https://status.skribble.com/maintenance/cmqozp5o2001v2jnwlevqkxq7</guid>
</item>

<item>
  <title>Skribble unscheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 30 minutes

    Affected Components: Skribble Platform CH
    Jun 19, 09:51:12 GMT+0 - Identified - We are planning for an unscheduled maintenance during that period. We do not expect any disruptions during this time. Jun 19, 10:30:01 GMT+0 - Identified - Maintenance is now in progress Jun 19, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:51:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for an unscheduled maintenance during that period. We do not expect any disruptions during this time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 19 Jun 2026 10:30:00 +0000</pubDate>
  <link>https://status.skribble.com/maintenance/cmqkr11ci01af2oqj6c6ifc9c</link>
  <guid>https://status.skribble.com/maintenance/cmqkr11ci01af2oqj6c6ifc9c</guid>
</item>

<item>
  <title>SSO Login Redirect Issue</title>
  <description>
    Type: Incident
    

    Affected Components: Skribble Platform CH, Skribble UI
    May 27, 07:04:00 GMT+0 - Resolved - We experienced an issue affecting SSO logins this morning. Users attempting to sign in via their organization&#039;s identity provider were unable to complete the login redirect.

The issue was identified following customer reports and internal testing. We resolved the problem within 30 minutes of processing the first complaint.

The root cause was traced back to a regression introduced during a recent deployment. The fix has been applied and SSO logins are operating normally again.

We apologize for the inconvenience and appreciate your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:04:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We experienced an issue affecting SSO logins this morning. Users attempting to sign in via their organization&#039;s identity provider were unable to complete the login redirect.

The issue was identified following customer reports and internal testing. We resolved the problem within 30 minutes of processing the first complaint.

The root cause was traced back to a regression introduced during a recent deployment. The fix has been applied and SSO logins are operating normally again.

We apologize for the inconvenience and appreciate your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 27 May 2026 07:04:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmpnr58pu12iip2n07ppwoxl7</link>
  <guid>https://status.skribble.com/incident/cmpnr58pu12iip2n07ppwoxl7</guid>
</item>

<item>
  <title>Login Issue – skribble.de</title>
  <description>
    Type: Incident
    Duration: 1 hour and 8 minutes

    Affected Components: Skribble Platform CH
    May 26, 06:21:02 GMT+0 - Investigating - Users are currently unable to log in via [skribble.de](http://skribble.de).   
  
([skribble.com](http://skribble.com) is not affected and works as expected.)  

We are investigating the issue and will provide updates as soon as possible. May 26, 07:28:37 GMT+0 - Resolved - The login issue affecting [skribble.de](http://skribble.de) has been resolved. All systems are now operational. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:21:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Users are currently unable to log in via [skribble.de](http://skribble.de).   
  
([skribble.com](http://skribble.com) is not affected and works as expected.)  

We are investigating the issue and will provide updates as soon as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:28:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The login issue affecting [skribble.de](http://skribble.de) has been resolved. All systems are now operational..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 26 May 2026 06:21:02 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmpm8ydo208nenrm70pnozj82</link>
  <guid>https://status.skribble.com/incident/cmpm8ydo208nenrm70pnozj82</guid>
</item>

<item>
  <title>SMS Issues Impacting AES Signature Signing</title>
  <description>
    Type: Incident
    Duration: 3 days, 3 hours and 32 minutes

    Affected Components: Skribble Platform CH
    Apr 4, 09:48:43 GMT+0 - Investigating - SMS delivery is currently impacted. Due to an attack on a partner’s infrastructure used for 2FA notifications, AES signature signing is temporarily limited. We are investigating and working on a resolution. Apr 6, 13:03:50 GMT+0 - Identified - We have found the source of the issue together with our supplier. **The attacks on our 2FA SMS infrastructure have successfully been stopped, and no customer data has been affected.** We plan to restart AES services to non-Swiss mobile numbers by Tuesday, April 7th. Apr 7, 13:20:25 GMT+0 - Resolved - The issue has been resolved and SMS services for 2FA have been enabled again. We will continue to monitor the situation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 3 hours and 32 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:48:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  SMS delivery is currently impacted. Due to an attack on a partner’s infrastructure used for 2FA notifications, AES signature signing is temporarily limited. We are investigating and working on a resolution..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:03:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have found the source of the issue together with our supplier. **The attacks on our 2FA SMS infrastructure have successfully been stopped, and no customer data has been affected.** We plan to restart AES services to non-Swiss mobile numbers by Tuesday, April 7th..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:20:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been resolved and SMS services for 2FA have been enabled again. We will continue to monitor the situation..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 4 Apr 2026 09:48:43 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmnk5h3z80ajbwkksz0kx9vri</link>
  <guid>https://status.skribble.com/incident/cmnk5h3z80ajbwkksz0kx9vri</guid>
</item>

<item>
  <title>Email Delivery Disruption on skribble.de</title>
  <description>
    Type: Incident
    Duration: 10 hours and 6 minutes

    Affected Components: Skribble Platform CH
    Feb 17, 21:00:55 GMT+0 - Identified - We have identified a networking issue affecting [**skribble.de**](http://skribble.de) that is currently preventing the sending of emails.

Our engineering team is actively working on resolving the issue as quickly as possible. Feb 18, 07:07:11 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified a networking issue affecting [**skribble.de**](http://skribble.de) that is currently preventing the sending of emails.

Our engineering team is actively working on resolving the issue as quickly as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:07:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 17 Feb 2026 21:00:55 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmlr6ekcm0105r0upnag84j7w</link>
  <guid>https://status.skribble.com/incident/cmlr6ekcm0105r0upnag84j7w</guid>
</item>

<item>
  <title>Mobile ID Authentication Disruption</title>
  <description>
    Type: Incident
    Duration: 2 hours and 44 minutes

    Affected Components: Swisscom Trust Services, , 
External (Third Party) Services →
    Feb 11, 09:19:21 GMT+0 - Identified - We are currently experiencing intermittent issues with **Mobile ID authentication** due to a service disruption at our external partner, **Swisscom**, caused by an ongoing external attack.

Customers may notice temporary connection issues or delays when using Mobile ID. There is **no risk to customer data or security**.

Swisscom is actively working to stabilize the service. We will provide updates as more information becomes available. Feb 11, 10:52:02 GMT+0 - Monitoring - Mobile ID authentication is now operating normally. The earlier disruption at our external partner (Swisscom) appears resolved. We will continue to monitor the service closely.  Feb 11, 12:03:09 GMT+0 - Resolved - This incident has been resolved.  
  
Our Partner, Swisscom, has successfully switched their services back to the regular operating environment and they are currently functioning properly and with high performance. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:19:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are currently experiencing intermittent issues with **Mobile ID authentication** due to a service disruption at our external partner, **Swisscom**, caused by an ongoing external attack.

Customers may notice temporary connection issues or delays when using Mobile ID. There is **no risk to customer data or security**.

Swisscom is actively working to stabilize the service. We will provide updates as more information becomes available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:52:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Mobile ID authentication is now operating normally. The earlier disruption at our external partner (Swisscom) appears resolved. We will continue to monitor the service closely. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:03:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved.  
  
Our Partner, Swisscom, has successfully switched their services back to the regular operating environment and they are currently functioning properly and with high performance..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 11 Feb 2026 09:19:21 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmlhtj1v60087dd6ylf87fm6z</link>
  <guid>https://status.skribble.com/incident/cmlhtj1v60087dd6ylf87fm6z</guid>
</item>

<item>
  <title>Degraded performance</title>
  <description>
    Type: Incident
    Duration: 1 hour and 6 minutes

    Affected Components: Skribble UI
    Dec 12, 09:34:58 GMT+0 - Investigating - We are currently experiencing degraded performance across parts of the platform for some of our customers. 

All core services remain operational. Our team is actively working to improve the situation and restore normal service levels. Dec 12, 10:41:11 GMT+0 - Resolved - This incident has been resolved.  
  
Recent performance slowdowns on our platform was due to unusual increased traffic. Our team has promptly added additional resources to improve responsiveness and stability. The issue is now resolved, and we apologize for any inconvenience caused. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:34:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing degraded performance across parts of the platform for some of our customers. 

All core services remain operational. Our team is actively working to improve the situation and restore normal service levels..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:41:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved.  
  
Recent performance slowdowns on our platform was due to unusual increased traffic. Our team has promptly added additional resources to improve responsiveness and stability. The issue is now resolved, and we apologize for any inconvenience caused..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 12 Dec 2025 09:34:58 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmj2o86e305wmthagotibh3oi</link>
  <guid>https://status.skribble.com/incident/cmj2o86e305wmthagotibh3oi</guid>
</item>

<item>
  <title>Potential Impact on Skribble Support &amp; Login Due to Global Cloudflare Issue</title>
  <description>
    Type: Incident
    Duration: 10 minutes

    Affected Components: Skribble Platform CH
    Dec 5, 07:56:00 GMT+0 - Monitoring - A **global Cloudflare outage** is currently ongoing.  
  
As a result, **login and support access for Skribble may be affected** intermittently.  

You can monitor Cloudflare’s updates here: [**Cloudflare Status Link**](https://www.cloudflarestatus.com).  

We are closely monitoring the situation and will provide updates as needed. Dec 5, 08:20:00 GMT+0 - Resolved - This incident has been resolved. We have not noticed any direct impact in our platform.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:56:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  A **global Cloudflare outage** is currently ongoing.  
  
As a result, **login and support access for Skribble may be affected** intermittently.  

You can monitor Cloudflare’s updates here: [**Cloudflare Status Link**](https://www.cloudflarestatus.com).  

We are closely monitoring the situation and will provide updates as needed..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. We have not noticed any direct impact in our platform. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 5 Dec 2025 07:56:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmisow1s00b9x11tt4flmrf7f</link>
  <guid>https://status.skribble.com/incident/cmisow1s00b9x11tt4flmrf7f</guid>
</item>

<item>
  <title>Limited platform availability</title>
  <description>
    Type: Incident
    Duration: 2 hours and 10 minutes

    Affected Components: , Skribble UI, Skribble Platform CH, Skribble API CH, 
Internal Services →
    Dec 1, 16:26:00 GMT+0 - Investigating - We see degraded availability of our platform. We are currently investigating this incident.  Dec 1, 17:47:18 GMT+0 - Monitoring - The issue has been identified, and corrective measures have been taken. 

The system appears to be gradually recovering, and we continue to monitor it closely. Dec 1, 18:35:40 GMT+0 - Resolved - The platform is back online. Since the recovery, there have been no further known interruptions or issues. 

We are continuing to conduct tests and closely monitor the situation. Dec 2, 14:22:53 GMT+0 - Postmortem - **Incident Summary**  
During the rollout of a new service, an unexpected interaction with our production environment caused a temporary disruption of some of our main services. 

Our team immediately intervened, initiated the recovery process, and restored all affected components shortly thereafter. 

The platform has been fully stable since the recovery, and we are taking steps to ensure similar issues do not occur in the future. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:26:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We see degraded availability of our platform. We are currently investigating this incident. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 1&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;Monitoring&lt;/strong&gt; -
  The issue has been identified, and corrective measures have been taken. 

The system appears to be gradually recovering, and we continue to monitor it closely..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:35:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The platform is back online. Since the recovery, there have been no further known interruptions or issues. 

We are continuing to conduct tests and closely monitor the situation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:22:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postmortem&lt;/strong&gt; -
  **Incident Summary**  
During the rollout of a new service, an unexpected interaction with our production environment caused a temporary disruption of some of our main services. 

Our team immediately intervened, initiated the recovery process, and restored all affected components shortly thereafter. 

The platform has been fully stable since the recovery, and we are taking steps to ensure similar issues do not occur in the future..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 1 Dec 2025 16:26:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmind2el6007svwfl24z76rjs</link>
  <guid>https://status.skribble.com/incident/cmind2el6007svwfl24z76rjs</guid>
</item>

<item>
  <title>External provider issues ( Cloudflare down ) </title>
  <description>
    Type: Incident
    Duration: 2 hours and 52 minutes

    Affected Components: Skribble Document Validation API CH, Skribble UI, GlobalSign Atlas, SparkPost, Skribble Platform CH, Skribble API CH, Swisscom Trust Services, , A-Trust, CloudScale, VSHN, 
External (Third Party) Services →
    Nov 18, 14:27:11 GMT+0 - Resolved - The incident was resolved , but complete recovery will take a bit more time in different regions as we have been informed by cloudflare. Nov 18, 11:35:00 GMT+0 - Monitoring - We&#039;re currently experiencing degraded performance across the platform due to a major Cloudflare outage affecting multiple regions. This external dependency issue may cause slow loading, intermittent errors, or temporary unavailability for some users. We&#039;ll update this page as soon as Cloudflare restores full service—our systems are otherwise healthy and the team is monitoring closely. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 52 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:27:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The incident was resolved , but complete recovery will take a bit more time in different regions as we have been informed by cloudflare..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We&#039;re currently experiencing degraded performance across the platform due to a major Cloudflare outage affecting multiple regions. This external dependency issue may cause slow loading, intermittent errors, or temporary unavailability for some users. We&#039;ll update this page as soon as Cloudflare restores full service—our systems are otherwise healthy and the team is monitoring closely..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 11:35:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmi4jczf100g1izl235z46b6w</link>
  <guid>https://status.skribble.com/incident/cmi4jczf100g1izl235z46b6w</guid>
</item>

<item>
  <title>Authentication SMS for Advanced E-Signatures (AES)</title>
  <description>
    Type: Incident
    Duration: 12 days, 4 hours and 25 minutes

    Affected Components: , Skribble Platform CH, Skribble API CH, 
Internal Services →
    Nov 2, 10:07:00 GMT+0 - Investigating - We are currently experiencing a degradation in the delivery of authentication SMS for advanced e-signatures (AES).

Our team is investigating the issue and working with our provider to restore full functionality.

We will provide an update as soon as we have more information. Nov 3, 16:17:35 GMT+0 - Identified - We have identified the source of the issue and **closed the entry point**. To **re-enable AES signing for non-Swiss phone numbers**, we need to **deploy an update**, which is scheduled for **tomorrow morning**.

No customer data was at risk: the exploit misused our messaging system to trigger SMS messages, which led to an **automated shutdown** due to unusually high volume.

More updates will follow as soon as the deployment is completed. Nov 2, 11:42:00 GMT+0 - Identified - We have identified the issue; it only affects authentication SMS sent to **non-Swiss phone numbers**.

Our team is working with our SMS provider to resolve the problem and restore full delivery.

We will provide an update as soon as we have more information. Nov 4, 10:46:45 GMT+0 - Resolved - The issue has been **resolved**.

**AES signing for non-Swiss phone numbers is fully operational again.**

More details will follow in a post-incident report. Nov 4, 12:27:23 GMT+0 - Monitoring - The issue has **reopened**.

A **backlog of undelivered messages** is currently affecting the delivery of new authentication SMS.

We are working on a solution and will provide an update as soon as more information is available. Nov 4, 13:13:28 GMT+0 - Resolved - The issue has been **resolved**.

All authentication SMS are now **fully operational again**. Nov 3, 11:25:06 GMT+0 - Identified - Due to **fraudulent use of our SMS authentication service**, all authentication SMS to **non-Swiss phone numbers** are currently **blocked** for signing with AES. We are actively investigating the source of the abuse and working to **close the exploited gap**.

In the meantime, we recommend using **SES** or **QES** signature levels as alternatives.

We will provide an update as soon as we have more information. Nov 6, 09:01:54 GMT+0 - Postmortem - **Incident Summary (31.10.2025 – 03.11.2025)**  
We experienced abuse of SMS resends in **trial accounts**, where SMS messages were sent to **high-cost numbers outside the EU and CH**.

  
After detection, the **SMS gateway was temporarily deactivated** while we analyzed the issue and implemented countermeasures.  

**Impact:**

* Financial loss to Skribble only
* No customer data affected or exposed

**Countermeasures:**

* Trial (non-paying) accounts can no longer send SMS outside defined “safe” countries
* Paying customers remain unrestricted

We apologize for the disruption during this period. The temporary outage was necessary to ensure no security breach and to protect our customers from any negative impact.  
  
Sincerely,  
Waldemar Dick (CTO) Nov 14, 11:13:08 GMT+0 - Identified - We have detected new issues with sending authentication SMS to **certain EU countries**.

Currently, AES signatures for signers with **German** and **French** phone numbers are **not functioning**. At this stage, we cannot rule out that **additional countries** may also be affected.

We are investigating the full scope of the problem and are in contact with our SMS provider to resolve it.

More updates will follow as soon as we have additional information. Nov 14, 14:09:21 GMT+0 - Identified - We can now confirm that the issue affects **all non-Swiss phone numbers**, not only German and French numbers as initially observed. Authentication SMS for AES currently work **only** with Swiss numbers.

We are in direct contact with our SMS provider to resolve the issue as quickly as possible.

We will provide another update as soon as we have more information. Nov 14, 14:31:41 GMT+0 - Resolved - We were able to **resolve the issue**; all authentication SMS are now being sent **normally again**, including to non-Swiss phone numbers.

We are still in contact with our SMS provider to **verify the root cause**. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 days, 4 hours and 25 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:07:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing a degradation in the delivery of authentication SMS for advanced e-signatures (AES).

Our team is investigating the issue and working with our provider to restore full functionality.

We will provide an update as soon as we have more information..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:17:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the source of the issue and **closed the entry point**. To **re-enable AES signing for non-Swiss phone numbers**, we need to **deploy an update**, which is scheduled for **tomorrow morning**.

No customer data was at risk: the exploit misused our messaging system to trigger SMS messages, which led to an **automated shutdown** due to unusually high volume.

More updates will follow as soon as the deployment is completed..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:42:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the issue; it only affects authentication SMS sent to **non-Swiss phone numbers**.

Our team is working with our SMS provider to resolve the problem and restore full delivery.

We will provide an update as soon as we have more information..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:46:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been **resolved**.

**AES signing for non-Swiss phone numbers is fully operational again.**

More details will follow in a post-incident report..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:27:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The issue has **reopened**.

A **backlog of undelivered messages** is currently affecting the delivery of new authentication SMS.

We are working on a solution and will provide an update as soon as more information is available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:13:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been **resolved**.

All authentication SMS are now **fully operational again**..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:25:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Due to **fraudulent use of our SMS authentication service**, all authentication SMS to **non-Swiss phone numbers** are currently **blocked** for signing with AES. We are actively investigating the source of the abuse and working to **close the exploited gap**.

In the meantime, we recommend using **SES** or **QES** signature levels as alternatives.

We will provide an update as soon as we have more information..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:01:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postmortem&lt;/strong&gt; -
  **Incident Summary (31.10.2025 – 03.11.2025)**  
We experienced abuse of SMS resends in **trial accounts**, where SMS messages were sent to **high-cost numbers outside the EU and CH**.

  
After detection, the **SMS gateway was temporarily deactivated** while we analyzed the issue and implemented countermeasures.  

**Impact:**

* Financial loss to Skribble only
* No customer data affected or exposed

**Countermeasures:**

* Trial (non-paying) accounts can no longer send SMS outside defined “safe” countries
* Paying customers remain unrestricted

We apologize for the disruption during this period. The temporary outage was necessary to ensure no security breach and to protect our customers from any negative impact.  
  
Sincerely,  
Waldemar Dick (CTO).&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:13:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have detected new issues with sending authentication SMS to **certain EU countries**.

Currently, AES signatures for signers with **German** and **French** phone numbers are **not functioning**. At this stage, we cannot rule out that **additional countries** may also be affected.

We are investigating the full scope of the problem and are in contact with our SMS provider to resolve it.

More updates will follow as soon as we have additional information..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:09:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We can now confirm that the issue affects **all non-Swiss phone numbers**, not only German and French numbers as initially observed. Authentication SMS for AES currently work **only** with Swiss numbers.

We are in direct contact with our SMS provider to resolve the issue as quickly as possible.

We will provide another update as soon as we have more information..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:31:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We were able to **resolve the issue**; all authentication SMS are now being sent **normally again**, including to non-Swiss phone numbers.

We are still in contact with our SMS provider to **verify the root cause**..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 2 Nov 2025 10:07:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmhhlxeiz00h2jlz6sth35f5q</link>
  <guid>https://status.skribble.com/incident/cmhhlxeiz00h2jlz6sth35f5q</guid>
</item>

<item>
  <title>Issues with notifications </title>
  <description>
    Type: Incident
    Duration: 5 days, 10 hours and 49 minutes

    Affected Components: Skribble Platform CH
    Sep 23, 18:22:50 GMT+0 - Investigating - We are currently experiencing issues with our notification service, resulting in some users not receiving notifications from our platform. Our team is actively investigating to determine the root cause. Sep 24, 17:39:41 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 29, 05:12:13 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 10 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:22:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing issues with our notification service, resulting in some users not receiving notifications from our platform. Our team is actively investigating to determine the root cause..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:39:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:12:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 23 Sep 2025 18:22:50 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmfwvuuvu006911v5sfa3lpgn</link>
  <guid>https://status.skribble.com/incident/cmfwvuuvu006911v5sfa3lpgn</guid>
</item>

<item>
  <title>Login not working for skribble.com</title>
  <description>
    Type: Incident
    Duration: 3 hours and 18 minutes

    Affected Components: Skribble Platform CH, Skribble UI
    Sep 2, 17:20:00 GMT+0 - Resolved - We have not detected any further abnormalities, and the issue appears to be fully resolved. We will continue monitoring to ensure stable performance. Sep 2, 14:02:00 GMT+0 - Investigating - We are currently experiencing issues with the login functionality on \[skribble.com\](http://skribble.com), which may impact users&#039; ability to access their accounts and use our services. Our team is investigating the situation and working to resolve the root cause. We apologize for any inconvenience this may cause and thank you for your patience. We will update this page as more information becomes available. Sep 2, 16:20:00 GMT+0 - Monitoring - We have identified the issue, which was related to a service of an external (third-party) provider that we were not actively monitoring. Loading times have returned to normal, and we will continue to closely monitor the situation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have not detected any further abnormalities, and the issue appears to be fully resolved. We will continue monitoring to ensure stable performance..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:02:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing issues with the login functionality on \[skribble.com\](http://skribble.com), which may impact users&#039; ability to access their accounts and use our services. Our team is investigating the situation and working to resolve the root cause. We apologize for any inconvenience this may cause and thank you for your patience. We will update this page as more information becomes available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have identified the issue, which was related to a service of an external (third-party) provider that we were not actively monitoring. Loading times have returned to normal, and we will continue to closely monitor the situation..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 2 Sep 2025 14:02:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmf2nela7000t53o3bivhafmd</link>
  <guid>https://status.skribble.com/incident/cmf2nela7000t53o3bivhafmd</guid>
</item>

<item>
  <title>Signature protocols not available for newly created documents</title>
  <description>
    Type: Incident
    Duration: 5 hours and 24 minutes

    Affected Components: Skribble Platform CH, Skribble API CH
    Aug 27, 13:03:21 GMT+0 - Investigating - We have identified an issue where signature protocols cannot currently be downloaded for newly created documents. Our team is actively investigating the cause and working on a resolution.

**Impact:**  
Users may experience errors when attempting to access signature protocols for documents created today. Aug 27, 14:29:20 GMT+0 - Monitoring - We have identified the root cause of the issue. It was caused by high event load. Systems are recovering, and signature protocols are becoming available again. We continue to monitor. Aug 27, 18:27:16 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:03:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We have identified an issue where signature protocols cannot currently be downloaded for newly created documents. Our team is actively investigating the cause and working on a resolution.

**Impact:**  
Users may experience errors when attempting to access signature protocols for documents created today..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:29:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have identified the root cause of the issue. It was caused by high event load. Systems are recovering, and signature protocols are becoming available again. We continue to monitor..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:27:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 27 Aug 2025 13:03:21 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmetzk0eb0001wbp2bz78lh6e</link>
  <guid>https://status.skribble.com/incident/cmetzk0eb0001wbp2bz78lh6e</guid>
</item>

<item>
  <title>Disruption on my.skribble.com</title>
  <description>
    Type: Incident
    Duration: 1 hour and 32 minutes

    Affected Components: , Skribble Platform CH, Skribble Document Validation API CH, Skribble API CH, Skribble UI, 
Internal Services →
    Jul 29, 14:05:15 GMT+0 - Investigating - We are currently experiencing disruptions on our .COM platform ([my.skribble.com](http://my.skribble.com)), resulting in unusually long loading times. This may impact login and signing operations.

Our team is actively investigating and monitoring all relevant services to identify the root cause. We will provide updates as soon as we have more information. Thank you for your patience. Jul 29, 14:17:03 GMT+0 - Identified - We’ve identified the issue causing disruptions on [my.skribble.com](http://my.skribble.com) — it’s related to our database. This is impacting loading times, login, and signing.

We&#039;re working on a fix and will share updates as soon as possible. Jul 29, 15:37:41 GMT+0 - Resolved - The database is recovering. The platform is operational again for most users, but some residual slowdowns may still occur. We continue to monitor the situation closely. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 32 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:05:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing disruptions on our .COM platform ([my.skribble.com](http://my.skribble.com)), resulting in unusually long loading times. This may impact login and signing operations.

Our team is actively investigating and monitoring all relevant services to identify the root cause. We will provide updates as soon as we have more information. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:17:03&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We’ve identified the issue causing disruptions on [my.skribble.com](http://my.skribble.com) — it’s related to our database. This is impacting loading times, login, and signing.

We&#039;re working on a fix and will share updates as soon as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:37:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The database is recovering. The platform is operational again for most users, but some residual slowdowns may still occur. We continue to monitor the situation closely..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 29 Jul 2025 14:05:15 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmdolzwgw003jvtfgjrm5iet8</link>
  <guid>https://status.skribble.com/incident/cmdolzwgw003jvtfgjrm5iet8</guid>
</item>

<item>
  <title>Login Issues on EU Platform (my.skribble.de)</title>
  <description>
    Type: Incident
    Duration: 10 minutes

    Affected Components: Skribble Platform CH
    Jul 15, 09:00:31 GMT+0 - Investigating - We are currently experiencing issues with the login functionality on our EU platform, [my.skribble.de](http://my.skribble.de). Users may be unable to access their accounts at this time.

Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We will provide an update as soon as more information is available. Jul 15, 09:10:08 GMT+0 - Resolved - The problem has been identified and resolved. Login functionality is now fully restored and working as expected.

We apologize for the disruption and thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:00:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing issues with the login functionality on our EU platform, [my.skribble.de](http://my.skribble.de). Users may be unable to access their accounts at this time.

Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We will provide an update as soon as more information is available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:10:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The problem has been identified and resolved. Login functionality is now fully restored and working as expected.

We apologize for the disruption and thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 15 Jul 2025 09:00:31 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmd4ay3pu00sy2lrx2kuijoun</link>
  <guid>https://status.skribble.com/incident/cmd4ay3pu00sy2lrx2kuijoun</guid>
</item>

<item>
  <title>Partial Unavailability of Signature Activity and Signature Reports</title>
  <description>
    Type: Incident
    Duration: 2 days, 20 hours and 20 minutes

    Affected Components: Skribble API CH, Skribble UI
    Jun 23, 20:00:00 GMT+0 - Identified - After our data center migration, we observed that a backlog of audit events was being processed with delay. Impact: \* The Signature Activity tab in the admin interface displayed audit events with delay. \* Signature Reports, which rely on audit events, are generated partially or not at all if relevant audit data are missing. Jun 25, 16:40:00 GMT+0 - Monitoring - The audit event backlog has been fully processed. All delayed audit entries are now complete and available in the system.  
  
The Signature Activity tab in the admin interface is now displaying all audit events correctly. Jun 26, 16:20:00 GMT+0 - Resolved - Fixed Report Cache

  
Signature Reports are signed and cached at the time of generation. As a result, any reports created during the incident window (23.06\. 22:00 – 25.06\. 18:40) may still have remained incomplete even after the audit log was fixed.

  
Mitigation:

We have removed all Signature Reports generated during the affected timeframe. These reports will now be automatically re-generated on demand (via UI or API) using the complete and corrected audit data

   Jun 27, 07:23:26 GMT+0 - Postmortem - **High-Level Summary**

After moving our systems to a new data center, background data that powers some signature reports was delayed. Reports created between Monday evening and Wednesday evening may have been incomplete. We’ve fixed the issue and will automatically re-create any affected reports as soon as they are accessed.

  
**No data has been lost**. Signature reports can be re-created **up to 10 years** into the past at any time.  

  
**Technical Details**

Following the data center migration, a backlog of audit events accumulated and was only processed with delay between Monday 23.06\. 22:00 and Wednesday 25.06\. 18:40.

Impact:

* Audit events in the Signature Activity tab appeared with delay.
* Signature Reports generated during this window were incomplete or not generated, depending on audit event availability at the time.

As of Wednesday 25.06\. 18:40, the backlog was fully processed. All delayed audit events have been restored and are complete.

Multiple customers reported incomplete Signature Reports.

We conducted a thorough review of the audit logs and the report generation process. The issue was traced to cached reports that had been created while audit events were still delayed. Since Signature Reports are signed and cached at the time of generation, any reports generated during the affected period remained incomplete, even after the underlying audit data had been fully restored.

  
Mitigation 26.07\. 18:20:

All Signature Reports generated between **23.06\. 22:00 and 25.06\. 18:40** have been **removed**. When accessed via UI or API, they will now be **automatically re-generated** using the complete and accurate audit data.

   
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 20 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  After our data center migration, we observed that a backlog of audit events was being processed with delay. Impact: \* The Signature Activity tab in the admin interface displayed audit events with delay. \* Signature Reports, which rely on audit events, are generated partially or not at all if relevant audit data are missing..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The audit event backlog has been fully processed. All delayed audit entries are now complete and available in the system.  
  
The Signature Activity tab in the admin interface is now displaying all audit events correctly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Fixed Report Cache

  
Signature Reports are signed and cached at the time of generation. As a result, any reports created during the incident window (23.06\. 22:00 – 25.06\. 18:40) may still have remained incomplete even after the audit log was fixed.

  
Mitigation:

We have removed all Signature Reports generated during the affected timeframe. These reports will now be automatically re-generated on demand (via UI or API) using the complete and corrected audit data

  .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:23:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postmortem&lt;/strong&gt; -
  **High-Level Summary**

After moving our systems to a new data center, background data that powers some signature reports was delayed. Reports created between Monday evening and Wednesday evening may have been incomplete. We’ve fixed the issue and will automatically re-create any affected reports as soon as they are accessed.

  
**No data has been lost**. Signature reports can be re-created **up to 10 years** into the past at any time.  

  
**Technical Details**

Following the data center migration, a backlog of audit events accumulated and was only processed with delay between Monday 23.06\. 22:00 and Wednesday 25.06\. 18:40.

Impact:

* Audit events in the Signature Activity tab appeared with delay.
* Signature Reports generated during this window were incomplete or not generated, depending on audit event availability at the time.

As of Wednesday 25.06\. 18:40, the backlog was fully processed. All delayed audit events have been restored and are complete.

Multiple customers reported incomplete Signature Reports.

We conducted a thorough review of the audit logs and the report generation process. The issue was traced to cached reports that had been created while audit events were still delayed. Since Signature Reports are signed and cached at the time of generation, any reports generated during the affected period remained incomplete, even after the underlying audit data had been fully restored.

  
Mitigation 26.07\. 18:20:

All Signature Reports generated between **23.06\. 22:00 and 25.06\. 18:40** have been **removed**. When accessed via UI or API, they will now be **automatically re-generated** using the complete and accurate audit data.

  .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 23 Jun 2025 20:00:00 +0000</pubDate>
  <link>https://status.skribble.com/incident/cmcegv5i2007rmldu9iya0had</link>
  <guid>https://status.skribble.com/incident/cmcegv5i2007rmldu9iya0had</guid>
</item>

  </channel>
  </rss>