Skribble AG - Notice history

All systems operational

Operational

Skribble API - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

Skribble Platform - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 99.65%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

Skribble Document Validation API - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024
Operational

A-Trust - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

GlobalSign Atlas - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 99.78%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CloudScale - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

VSHN - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

Swisscom Trust Services - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

SparkPost - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

Stripe API - Operational

Stripe Checkout - Operational

Notice history

Nov 2024

Swiss Mail Server outage
  • Resolved
    Resolved

    Incident Report: Email Delivery Issue

    Summary:

    An issue was identified where emails sent from our Swiss Mail Server were being classified as spam and discarded by recipient mail servers.

    Root Cause:

    The issue stemmed from a broken DNS record. Emails were being sent using the sender domain "@mail.skribble.com," which was not properly configured. This led to spam protection measures by recipient mail servers rejecting the emails.

    Timeline of Events:

    12:10 - Reports were received that emails sent from the server were being rejected or discarded as spam.

    12:32 - Problems confirmed, investigations started

    12:38 - Identified DNS records as source of the issues.

    13:02 - DNS records repaired an updates.

    13:xx - Monitoring DNS propagation and successful e-mail delivery.

    Incident Status:

    The issue has been resolved. Emails are now being successfully delivered as DNS propagation completes.

  • Monitoring
    Monitoring

    Update: The DNS record has been corrected. Please note that it may take some time for the changes to propagate across other DNS servers.

  • Identified
    Identified

    Update: The issue has been identified as a broken DNS record for our mail server. This is causing recipients to classify and discard our emails as spam.

  • Investigating
    Investigating

    We are currently investigating this incident, why our Swiss Mail server is not sending e-mails.

    This is only effecting customers, with the "Swiss Mail Server" option.

Signatures with AES4Business / GlobalSign - Connectivity issues
  • Resolved
    Resolved

    Incident Summary:

    On November 12th 2024, an upgrade to the latest version of GlobalSign Atlas inadvertently disabled the mTLS certificate expiration warning. As a result, no notification was received on either the GlobalSign or Skribble side regarding the certificate status. This led to a temporary disruption in the secure communication channel, impacting functionality for signatures and the AES4Business feature.

    Timeline of Events:

    1. Issue Detected: 12:00 - Discovered interruption in the secure channel between GlobalSign and Skribble, affecting specific features.

    2. Root Cause Analysis: 12:15 - Identified that the mTLS certificate expiration warning had been disabled in the updated GlobalSign Atlas version, preventing any proactive alerts.

    3. Resolution: 13:40 - Updated the secure channel between GlobalSign and Skribble, restoring all functionalities, including AES4Business.

    Resolution:

    The secure communication channel between GlobalSign and Skribble was reestablished. Signature services and the AES4Business feature are now functioning as expected.

    Follow-Up Actions:

    1. Review and Update Communication Channels: All communication channels between Skribble and GlobalSign will be reviewed and updated to ensure uninterrupted notifications and functionality.

    2. Long-Term Validity Assurance: The renewed connection is valid for the next five years, minimizing the risk of similar issues during this period.

    Conclusion:

    The issue has been resolved, and measures are in place to prevent recurrence. We expect smooth operations and reliable notifications over the next five years due to the updated connection configuration.

  • Investigating
    Investigating

    We are currently investigating this incident with our AES4Business features and connectivity with GlobalSign.

Oct 2024

Oct 2024 to Dec 2024

Next