Commslayer Outage History

Commslayer had 7 outages in the last 2 years totaling 152h 53m of downtime — averaging 0.3 incidents per month.

There were 7 Commslayer outages since October 16, 2025 totaling 152h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.commslayer.com

Minor April 8, 2026

Performance Degradation

Detected by Pingoru: Apr 08, 2026, 09:00 AM UTC
Resolved: Apr 11, 2026, 08:00 PM UTC
Duration: 3d 11h

Timeline · 3 updates

investigating Apr 08, 2026, 09:00 AM UTC

We identified increased database query times and elevated error rates affecting a subset of requests.
monitoring Apr 10, 2026, 02:30 AM UTC

Performance optimizations were rolled out progressively, reducing unnecessary database queries. Email routing issues were also identified and corrected during this period.
resolved Apr 11, 2026, 08:00 PM UTC

All fixes have been applied. Response times and error rates have returned to normal levels.

Read the full incident report →

Minor April 5, 2026

Elevated Error Rates

Detected by Pingoru: Apr 05, 2026, 10:00 AM UTC
Resolved: Apr 06, 2026, 06:00 PM UTC
Duration: 1d 8h

Timeline · 2 updates

investigating Apr 05, 2026, 10:00 AM UTC

We identified background processes that were triggering unexpected actions on resolved conversations.
resolved Apr 06, 2026, 06:00 PM UTC

The stale processes were cleaned up and safeguards were put in place. Error rates returned to normal.

Read the full incident report →

Minor March 30, 2026

Email Sync Disruption

Detected by Pingoru: Mar 30, 2026, 08:00 AM UTC
Resolved: Mar 30, 2026, 04:30 PM UTC
Duration: 8h 30m

Timeline · 2 updates

investigating Mar 30, 2026, 08:00 AM UTC

We identified a stuck background job that was blocking email synchronization across all connected email accounts.
resolved Mar 30, 2026, 04:30 PM UTC

The stuck process was cleared and safeguards were added to prevent recurrence. All email accounts resumed syncing normally.

Read the full incident report →

Minor February 10, 2026

Intermittent Errors Affecting Some Requests

Detected by Pingoru: Feb 10, 2026, 01:00 PM UTC
Resolved: Feb 11, 2026, 05:00 PM UTC
Duration: 1d 4h

Timeline · 3 updates

investigating Feb 10, 2026, 01:00 PM UTC

We identified issues that caused sporadic errors for a subset of requests.
monitoring Feb 11, 2026, 03:00 AM UTC

Multiple fixes were applied progressively. The update was rolled back and re-applied successfully the following day.
resolved Feb 11, 2026, 05:00 PM UTC

All identified issues have been fixed. Total affected time was approximately 11 minutes of accumulated errors spread across the period.

Read the full incident report →

Minor December 7, 2025

Brief Service Interruption

Detected by Pingoru: Dec 07, 2025, 09:14 PM UTC
Resolved: Dec 07, 2025, 09:17 PM UTC
Duration: 3m

Timeline · 2 updates

investigating Dec 07, 2025, 09:14 PM UTC

We identified the configuration change that caused the brief interruption.
resolved Dec 07, 2025, 09:17 PM UTC

The change was corrected and normal service resumed within minutes.

Read the full incident report →

Minor November 28, 2025

Brief Service Degradation

Detected by Pingoru: Nov 28, 2025, 08:30 PM UTC
Resolved: Nov 28, 2025, 08:40 PM UTC
Duration: 10m

Timeline · 2 updates

investigating Nov 28, 2025, 08:30 PM UTC

We identified the faulty update affecting backend services.
resolved Nov 28, 2025, 08:40 PM UTC

The update was rolled back and service was fully restored.

Read the full incident report →

Minor October 16, 2025

Brief Service Disruption

Detected by Pingoru: Oct 16, 2025, 07:30 PM UTC
Resolved: Oct 16, 2025, 08:40 PM UTC
Duration: 1h 10m

Timeline · 2 updates

investigating Oct 16, 2025, 07:30 PM UTC

We identified connection failures caused by a routing misconfiguration.
resolved Oct 16, 2025, 08:40 PM UTC

The misconfiguration was corrected and all connections were restored.

Read the full incident report →