SocketLabs Outage History

SocketLabs is up right now

SocketLabs had 6 outages in the last 2 years totaling 40h 13m of downtime — averaging 0.2 incidents per month.

There were 6 SocketLabs outages since April 19, 2026 totaling 40h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.socketlabs.com

Minor September 4, 2026

Microsoft - Exchange Online Errors

Detected by Pingoru
Sep 04, 2026, 12:27 PM UTC
Resolved
Sep 04, 2026, 04:01 PM UTC
Duration
3h 34m
Timeline · 3 updates
  1. identified Sep 04, 2026, 12:27 PM UTC

    We are monitoring reports of "Server busy" errors from Microsoft recipients. This issue has been identified by Microsoft (EX1467029), affecting users who may be attempting to send and receive email messages from external domains in Exchange Online. We will update when more information is available.

  2. monitoring Sep 04, 2026, 02:37 PM UTC

    Microsoft has reported that mitigation for incident EX1467029 is being applied, and we are seeing a significant reduction in the number of “Server busy” responses from Microsoft. Some delivery attempts to Microsoft recipients are still being deferred, and messages affected earlier in the incident remain queued for retry. SocketLabs will continue retrying these messages automatically in accordance with normal delivery procedures. As Microsoft service continues to recover, we expect delayed messages to be delivered over time. We will continue monitoring delivery performance and Microsoft’s status updates.

  3. resolved Sep 04, 2026, 04:01 PM UTC

    The Microsoft service issue associated with incident EX1467029 has been resolved, and delivery to Microsoft recipients has returned to normal. Messages delayed during the incident have been processed through our normal retry queues and the backlog has just about fully cleared. If you continue to experience delivery delays and issues to Microsoft recipients, please contact SocketLabs Support for further investigation.

Read the full incident report →

Minor August 25, 2026

Message Delays

Detected by Pingoru
Aug 25, 2026, 02:09 PM UTC
Resolved
Aug 25, 2026, 05:39 PM UTC
Duration
3h 30m
Timeline · 4 updates
  1. investigating Aug 25, 2026, 02:09 PM UTC

    We are currently investigating delays affecting a subset of customers.

  2. identified Aug 25, 2026, 04:07 PM UTC

    We have identified an issue causing delays for a subset of customers, and are actively mitigating.

  3. monitoring Aug 25, 2026, 04:49 PM UTC

    Mitigations have been applied and messages for affected customers are being processed. We will update again within 2 hours.

  4. resolved Aug 25, 2026, 05:39 PM UTC

    All message processing operations have returned to normal, and we consider this issue resolved.

Read the full incident report →

Minor June 15, 2026

Outbound delivery delays affecting some customers in the SocketLabs US2 region

Detected by Pingoru
Jun 15, 2026, 01:59 AM UTC
Resolved
Jun 15, 2026, 05:16 AM UTC
Duration
3h 17m
Timeline · 5 updates
  1. investigating Jun 15, 2026, 01:59 AM UTC

    We are currently investigating reports of delivery delays for certain customers.

  2. identified Jun 15, 2026, 02:51 AM UTC

    We have identified networking issues affecting the SocketLabs US2-* region. Customers assigned to deliver messages via SocketLabs IP addresses in the 142.0.180.0/24 and 142.0.181.0/24 ranges may experience delays in outbound message delivery. Messages will remain queued and continue to be automatically retried for delivery as quickly as possible. Customers configured with IP addresses across multiple availability zones have been automatically failed over to their other available regions. Our engineering team is actively working with our upstream vendor to address the issue and we will provide another update as more information becomes available.

  3. identified Jun 15, 2026, 04:43 AM UTC

    We continue to experience outbound delivery delays for customers assigned to the affected SocketLabs US2-* infrastructure. Our upstream vendor has confirmed a widespread carrier connectivity issue. Messages routed through the affected infrastructure remain queued and will continue to be automatically retried for delivery as quickly as possible. Customers configured with IP addresses across multiple availability zones remain failed over to their other available regions. Impacted customers may open a support ticket by emailing [email protected] to request a temporary reroute of their traffic while this issue remains ongoing. Our engineering team continues to work with our upstream vendor to address the issue, and we will provide another update as more information becomes available.

  4. monitoring Jun 15, 2026, 04:54 AM UTC

    Our upstream vendor has confirmed that carrier connectivity has been restored for the affected infrastructure. We are continuing to monitor outbound delivery performance as queued messages are processed and delivery latency returns to normal. Customers may continue to see delays for some previously submitted messages while the remaining queue is retried and delivered. We will continue monitoring and will provide a final resolved update once message queues and delivery latency have fully normalized.

  5. resolved Jun 15, 2026, 05:16 AM UTC

    All impacted message queues have cleared, and outbound delivery has been fully restored. Our upstream vendor previously confirmed that carrier connectivity was restored for the affected infrastructure. After continued monitoring, we have confirmed that message delivery latency has returned to normal. This incident is now resolved.

Read the full incident report →

Minor May 16, 2026

BGP / Connectivity Issues

Detected by Pingoru
May 16, 2026, 10:53 AM UTC
Resolved
May 16, 2026, 01:15 PM UTC
Duration
2h 21m
Timeline · 5 updates
  1. investigating May 16, 2026, 10:53 AM UTC

    We are currently investigating connectivity issues with an upstream provider.

  2. identified May 16, 2026, 12:50 PM UTC

    We have identified a BGP issue affecting SocketLabs traffic, and have escalated with our upstream provider. To assist with mitigation, we have temporarily shifted the IP addresses of the following endpoints: SMTP API: smtp.socketlabs.com (20.237.111.4) Injection API: inject.socketlabs.com, inject-cx.socketlabs.com (52.170.174.53)

  3. identified May 16, 2026, 01:11 PM UTC

    Connectivity to SocketLabs Portal and Identity have been restored. We are continuing to work on mitigation efforts for all affected services.

  4. monitoring May 16, 2026, 01:14 PM UTC

    All components are now operational.

  5. resolved May 18, 2026, 03:42 AM UTC

Read the full incident report →

Minor April 24, 2026

Increased Latency

Detected by Pingoru
Apr 24, 2026, 04:07 PM UTC
Resolved
Apr 25, 2026, 12:51 AM UTC
Duration
8h 43m
Timeline · 3 updates
  1. investigating Apr 24, 2026, 04:07 PM UTC

    We are currently investigating increased latency across several services due to an issue with an upstream provider.

  2. monitoring Apr 24, 2026, 06:31 PM UTC

    We are showing improvements in response times and internal metrics show recovery progress from our upstream provider. We will continue to monitor closely and update once we are confident of a full recovery.

  3. resolved Apr 25, 2026, 12:51 AM UTC

    Internal metrics have shown sustained improvement and return to normal levels, and our upstream provider has reported mitigation actions are complete. We consider this incident resolved and will continue to monitor closely.

Read the full incident report →