Skribble AG - Notice history

All systems operational

Operational

Skribble API - Operational

99% - uptime
May 2025 · 100.0%Jun · 97.15%Jul · 100.0%
May 2025
Jun 2025
Jul 2025

Skribble Platform - Operational

100% - uptime
May 2025 · 100.0%Jun · 99.43%Jul · 100.0%
May 2025
Jun 2025
Jul 2025

Skribble Document Validation API - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%
May 2025
Jun 2025
Jul 2025

Skribble UI - Operational

99% - uptime
May 2025 · 99.78%Jun · 97.15%Jul · 100.0%
May 2025
Jun 2025
Jul 2025
Operational

A-Trust - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%
May 2025
Jun 2025
Jul 2025

GlobalSign Atlas - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%
May 2025
Jun 2025
Jul 2025

CloudScale - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%
May 2025
Jun 2025
Jul 2025

VSHN - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%
May 2025
Jun 2025
Jul 2025

Swisscom Trust Services - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%
May 2025
Jun 2025
Jul 2025

SparkPost - Operational

100% - uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%
May 2025
Jun 2025
Jul 2025

Stripe API - Operational

Stripe Checkout - Operational

Notice history

Jun 2025

Partial Unavailability of Signature Activity and Signature Reports
  • Postmortem
    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.


  • Resolved
    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


  • Monitoring
    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.

  • Identified
    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.
Login not working for skribble.com
  • Postmortem
    Postmortem

    Incident Summary
    As part of preparations for our upcoming data center migration on 23.06.2025, a critical infrastructure update introduced a version incompatibility. This led to a database schema corruption within our authentication service.

    To ensure system stability and maintain data integrity, we performed a database restore, which successfully resolved the issue.

  • Resolved
    Resolved
    **Status Update** **09:20:** We identified a database error and started the resolution process. **12:14:** The database has been restored. All services have been tested and are back online.
  • Investigating
    Investigating
    We are currently experiencing issues with the login functionality on [skribble.com](http://skribble.com), which may impact users' ability to access their accounts and use our services. Our team is investigating the situation and working to resolve the root cause. We first noticed this issue on **June 18, 2025, at approximately 8:07**, and have since been actively working to mitigate any disruptions. We apologize for any inconvenience this may cause and thank you for your patience. We will update this page as more information becomes available.We are currently investigating this incident.

May 2025

Certificate Update for API Callbacks
  • Resolved
    Resolved

    We have updated the certificate used in our API Callbacks. If your systems rely on this certificate, please retrieve the new version at your earliest convenience. You can download the updated certificate from the following link:

    Download New Certificate

    Thank you for your prompt attention to this update. If you have any questions, please contact us at support@skribble.com.

May 2025 to Jul 2025

Next