ClickSend Outage History

Started Sep 03, 2026, 01:24 AM UTC· resolved Sep 09, 2026, 05:28 AM UTC

1. investigating Sep 03, 2026, 01:24 AM UTC

   Our vendor in the EU region is currently performing essential maintenance, which is causing delays to postal services in the region. All ClickSend systems are operating normally, and any letters/postcards submitted by customers have been successfully received and are securely held within our system. However, there may be a delay in forwarding these to our EU vendor while the maintenance is ongoing. We are monitoring the situation and will provide further updates as they become available.

2. investigating Sep 03, 2026, 01:34 AM UTC

   We are continuing to investigate this issue.

3. investigating Sep 04, 2026, 02:27 AM UTC

   We are continuing to investigate this issue.

4. investigating Sep 07, 2026, 12:36 AM UTC

   Our teams are actively working with the vendor to return the service safely to operation. We apologise for the continued disruption and appreciate your patience while this work continues. We will provide a further update as soon as more information is available.

5. resolved Sep 09, 2026, 05:28 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 08, 2026, 02:00 AM UTC· resolved Jul 09, 2026, 11:58 PM UTC

1. investigating Jul 08, 2026, 02:00 AM UTC

   We are currently observing delivery issues in Australia - Telstra Telstra has issued the following statement regarding the outage: "We’re looking into an issue affecting some mobile calls and data connections. If you’re having trouble connecting at first, try again as it may work on a retry. We’re on it and will share an update as soon as it’s fixed. Thanks for bearing with us." We are closely monitoring the situation on our end and will provide another update as soon as Telstra resolves the issue.

2. investigating Jul 08, 2026, 08:02 AM UTC

   We are continuing to investigate this issue.

3. investigating Jul 09, 2026, 12:52 AM UTC

   We are continuing to investigate this issue.

4. resolved Jul 09, 2026, 11:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 25, 2026, 06:51 AM UTC· resolved Jun 26, 2026, 03:57 AM UTC

1. investigating Jun 25, 2026, 06:51 AM UTC

   We are currently investigating an issue causing message delivery degradation. Customers may experience delays in message processing, with some message statuses remaining in "Message sent to the network for delivery" for longer than expected. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available.

2. investigating Jun 25, 2026, 11:56 AM UTC

   We are currently investigating an issue affecting our services. Our upstream vendor has identified an issue on their end and is actively working towards a resolution. We will provide further updates as more information becomes available.

3. investigating Jun 25, 2026, 01:09 PM UTC

   We are continuing to investigate this issue.

4. investigating Jun 25, 2026, 02:26 PM UTC

   We are continuing our investigation. Our upstream vendor has identified a problem on their end and is actively working towards a resolution. This issue is currently only impacting SMS traffic to the US and Australia (AU) routed through this upstream vendor. All other SMS traffic (including Rest of World) is unaffected and continues to process normally.

5. monitoring Jun 25, 2026, 03:34 PM UTC

   A fix has been implemented and we are monitoring the results.

6. monitoring Jun 26, 2026, 12:04 AM UTC

   Our upstream vendor has implemented a fix and messaging services have recovered. We have completed validation testing and confirmed message sending and delivery are functioning as expected. Their teams will continue to closely monitor platform performance to ensure stability. We are not currently observing any further issues related to this incident.

7. monitoring Jun 26, 2026, 03:56 AM UTC

   We are pleased to inform you that the issue with Message Delivery Degradation has now been resolved. Resolution Steps: Our upstream vendor has applied a fix to resolve the issue, and services are now operating normally again. If you experience any further technical issues or have any questions, please do not hesitate to contact our support team via chat. Our team is available 24/7 to assist you.

8. resolved Jun 26, 2026, 03:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 07, 2026, 03:39 AM UTC· resolved May 12, 2026, 02:26 PM UTC

1. investigating May 07, 2026, 03:39 AM UTC

   We are currently observing Inbound SMS delivery degradation for messages sending towards a subset of our United Kingdom Long Virtual Numbers affecting O2 network. You may experience failures or delays for Inbound SMS sending towards your subscribed United Kingdom Long Virtual Numbers affecting O2 network. We are working along with our partners to resolve the issue and will post an update as soon as more information becomes available.

2. investigating May 08, 2026, 10:21 AM UTC

   We have identified that, in addition to the previously reported impact on United Kingdom Long Virtual Numbers (O2 network), a subset of Swedish virtual numbers is also experiencing inbound SMS delivery degradation. Affected messages may be delayed or fail to deliver when sent to these Swedish numbers. The issue appears to be consistent with the ongoing degradation observed across certain inbound routes. We are continuing to work with our upstream partners to investigate the root cause and restore normal service as quickly as possible. Further updates will be provided as more information becomes available.

3. resolved May 12, 2026, 02:26 PM UTC

   We are pleased to inform you that the previously reported inbound SMS degradation issue has now been resolved. Resolution Steps: We worked closely with our vendor to identify and resolve the issue, and services are now operating normally again. If you experience any further technical issues or have any questions, please do not hesitate to contact our support team via chat. Our team is available 24/7 to assist you.

Read the full incident report →

Started Feb 09, 2026, 02:23 AM UTC· resolved Feb 09, 2026, 05:47 AM UTC

1. investigating Feb 09, 2026, 02:23 AM UTC

   New messages should now work, previously sent messages will likely be delayed Are you Impacted by signing into ClickSend Dashboard? Workaround: Select the Email Verification option instead of SMS New Customer? Please reach out to our Chat Support or send an email to [email protected]

2. monitoring Feb 09, 2026, 03:09 AM UTC

   New messages should now work, previously sent messages will likely be delayed Are you Impacted by signing into ClickSend Dashboard? Workaround: Select the Email Verification option instead of SMS New Customer? Please reach out to our Chat Support or send an email to [email protected]

3. resolved Feb 09, 2026, 05:47 AM UTC

   This incident has been resolved, please let us know if you encounter any issues

Read the full incident report →

Started Dec 08, 2025, 11:21 AM UTC· resolved Dec 09, 2025, 10:11 AM UTC

1. investigating Dec 08, 2025, 11:21 AM UTC

   We are aware of connection issues from UK ISPs (including Sky & BT Openreach) to our AWS cloud regional datacenter leading to errors when customers try to log in or access our platform. We have escalated this to AWS.

2. monitoring Dec 09, 2025, 07:08 AM UTC

   ISP's like 'Sky' seem to have fixed their routing issue to our Datacentre, we are getting confirmation from customers to confirm if the issue is resolved

3. resolved Dec 09, 2025, 10:11 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 26, 2025, 12:00 AM UTC· resolved Nov 27, 2025, 12:29 AM UTC

1. identified Nov 26, 2025, 07:52 AM UTC

   We are aware of an issue with our short URLs being flagged by Microsoft as suspicious, we are actively working with Microsoft to get this resolved. This impacts some customers who are using Microsoft Edge browser and/or Microsoft Defender. This is a temporary issue.

2. identified Nov 26, 2025, 01:10 PM UTC

   The issue has been partially resolved. New SMS messages and campaigns using short URLs are no longer affected. We are continuing to work with Microsoft on resolving the cases that were impacted prior to the fix.

3. identified Nov 26, 2025, 01:13 PM UTC

   We are continuing to work with Microsoft on resolving the cases that were impacted prior to the fix.

4. resolved Nov 27, 2025, 12:29 AM UTC

   This incident has been resolved. Microsoft has removed the flag, we have also changed our ShortURL from smsu.io to smsg.us

Read the full incident report →

Started Nov 18, 2025, 12:12 PM UTC· resolved Nov 18, 2025, 12:39 PM UTC

1. investigating Nov 18, 2025, 12:12 PM UTC

   We are aware of, and investigating an issue which impacts multiple customers: Widespread 500 errors, Dashboard and API also failing. We are working to understand the full impact and mitigate this problem. More updates to follow shortly

2. resolved Nov 18, 2025, 12:39 PM UTC

   The following services are now operational: • Online Dashboard • REST API We are continuing to monitor performance to ensure stability.

Read the full incident report →

Started Oct 20, 2025, 06:30 PM UTC· resolved Oct 20, 2025, 10:49 PM UTC

1. investigating Oct 20, 2025, 06:30 PM UTC

   The issues has been successfully resolved, and both SMS and MMS campaign services are now fully operational, as well as the login to the dashboard. If you continue to experience any issues, please don’t hesitate to contact our chat support for further assistance.

2. investigating Oct 20, 2025, 07:10 PM UTC

   The issues has been successfully resolved, and both SMS and MMS campaign services are now fully operational, as well as the login to the dashboard. If you continue to experience any issues, please don’t hesitate to contact our chat support for further assistance.

3. investigating Oct 20, 2025, 10:22 PM UTC

   The issues has been successfully resolved, and both SMS and MMS campaign services are now fully operational, as well as the login to the dashboard. If you continue to experience any issues, please don’t hesitate to contact our chat support for further assistance.

4. resolved Oct 20, 2025, 10:49 PM UTC

   The issues has been successfully resolved, and both SMS and MMS campaign services are now fully operational, as well as the login to the dashboard. If you continue to experience any issues, please don’t hesitate to contact our chat support for further assistance.

Read the full incident report →

Started Sep 24, 2025, 06:20 PM UTC· resolved Sep 25, 2025, 05:23 AM UTC

1. investigating Sep 24, 2025, 06:20 PM UTC

   We are currently investigating an issue that began around 8:27 AM PST on September 24, 2025, where some Transactional Emails are remaining in the Queued:WaitSend status. Our team is actively working to identify the cause and resolve the problem.

2. investigating Sep 24, 2025, 06:20 PM UTC

   We are continuing to investigate this issue.

3. investigating Sep 24, 2025, 08:26 PM UTC

   We are continuing to investigate this issue.

4. investigating Sep 25, 2025, 05:23 AM UTC

   We are continuing to investigate this issue.

5. resolved Sep 25, 2025, 05:23 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 29, 2025, 11:20 PM UTC· resolved Aug 30, 2025, 01:15 AM UTC

1. investigating Aug 29, 2025, 11:20 PM UTC

   Some customers from Belgium could still be facing issues when sending SMS with shared numbers

2. identified Aug 30, 2025, 12:15 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Aug 30, 2025, 01:06 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Aug 30, 2025, 01:15 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 29, 2025, 08:09 PM UTC· resolved Aug 29, 2025, 09:16 PM UTC

1. investigating Aug 29, 2025, 08:09 PM UTC

   We are currently experiencing SMS delivery issues for Belgium

2. resolved Aug 29, 2025, 09:16 PM UTC

   We have resolved the issue for Belgium customers

Read the full incident report →

Started Jul 22, 2025, 06:44 AM UTC· resolved Jul 23, 2025, 01:46 AM UTC

1. investigating Jul 22, 2025, 06:44 AM UTC

   We are currently investigating reports of delays in message approvals and website registration processing. Our team is working to assess the cause and will provide updates as more information becomes available. Thank you for your patience.

2. resolved Jul 23, 2025, 01:46 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 22, 2025, 01:58 AM UTC· resolved Jul 23, 2025, 02:22 AM UTC

1. investigating Jul 22, 2025, 01:58 AM UTC

   We are currently investigating reports of unexpected behavior involving Sender IDs and dedicated numbers. Our technical team is actively assessing the root cause and working to resolve the issue as quickly as possible. We will continue to provide updates as more information becomes available. We appreciate your patience and understanding while we work to restore full functionality.

2. monitoring Jul 22, 2025, 03:04 AM UTC

   Issues appear to have ceased and we are monitoring the situation

3. resolved Jul 23, 2025, 02:22 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 30, 2025, 06:32 AM UTC· resolved Jul 01, 2025, 12:11 AM UTC

1. identified Jun 30, 2025, 06:32 AM UTC

   Due to a planned service outage, please expect delays in our chat support response times between 2:30 PM and 3:30 PM AWST. We sincerely apologise for any inconvenience this may cause and appreciate your understanding.

2. resolved Jul 01, 2025, 12:11 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 30, 2025, 03:40 AM UTC· resolved Jul 01, 2025, 01:45 AM UTC

1. identified Jun 30, 2025, 03:40 AM UTC

   While we work on fixing this, we’ll be temporarily redirecting to our old portal.

2. identified Jun 30, 2025, 03:42 AM UTC

   We are continuing to work on a fix for this issue.

3. resolved Jul 01, 2025, 03:28 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 18, 2025, 01:22 AM UTC· resolved Jun 18, 2025, 03:57 AM UTC

1. investigating Jun 18, 2025, 01:22 AM UTC

   This is a temporary issue that we are currently investigating. This does not impact API

2. investigating Jun 18, 2025, 01:22 AM UTC

   We are continuing to investigate this issue.

3. monitoring Jun 18, 2025, 03:16 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jun 18, 2025, 03:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 24, 2025, 07:10 AM UTC· resolved May 21, 2025, 05:30 AM UTC

1. investigating Apr 24, 2025, 07:10 AM UTC

   We are currently observing delivery issues for 10DLC in United States - AT&T. Impact for 10DLC: Delayed MT's/Delayed MO's/Missing delivery receipts/Late delivery receipts We will update as soon as we have more information.

2. investigating Apr 28, 2025, 04:56 AM UTC

   We are continuing to investigate this issue.

3. identified May 16, 2025, 03:37 AM UTC

   We are continuing to work on a fix for this issue.

4. monitoring May 16, 2025, 03:38 AM UTC

   We have received an update from AT&T, and AT&T is currently upgrading their network to accommodate the growing demands of the industry and to introduce new services. As part of this upgrade, AT&T is migrating A2P traffic from older network components to a new gateway. During this transition, Sinch ClickSend, along with other partners, have actively migrated significant volumes of traffic throughout April and May. However, this process encountered some issues that necessitated updates to AT&T's network. These challenges did affect message processing temporarily, but they have since been resolved, and A2P message processing is now operating at the expected service levels. Sinch ClickSend remains in continuous communication with AT&T regarding the above information, and we have observed a significant improvement following AT&T's corrective actions. We continue to collaborate with AT&T to address a few residual error types that some customers are still experiencing.

5. monitoring May 16, 2025, 03:39 AM UTC

   We are continuing to monitor for any further issues.

6. resolved May 21, 2025, 05:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 11, 2025, 10:39 PM UTC· resolved Feb 11, 2025, 10:49 PM UTC

1. investigating Feb 11, 2025, 10:39 PM UTC

   We are having issues with our chat platform; we may not be responsive or able to provide service support immediately. Please bear with us for this short period; we will update our status page once this is resolved. Alternatively, you can send an email to [email protected].

2. resolved Feb 11, 2025, 10:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 07, 2025, 08:47 AM UTC· resolved Feb 07, 2025, 10:16 AM UTC

1. investigating Feb 07, 2025, 08:47 AM UTC

   We are having issues with our chat platform, we may not be responsive or able to service support immediately. Please bear with us for this short period, we will update our statuspage once this is resolved

2. resolved Feb 07, 2025, 10:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 19, 2025, 04:07 AM UTC· resolved Jan 19, 2025, 05:49 AM UTC

1. investigating Jan 19, 2025, 04:07 AM UTC

   We are currently investigating the issue.

2. investigating Jan 19, 2025, 04:38 AM UTC

   We are continuing to investigate this issue.

3. monitoring Jan 19, 2025, 05:13 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jan 19, 2025, 05:49 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 11, 2024, 03:45 AM UTC· resolved Dec 11, 2024, 04:01 AM UTC

1. investigating Dec 11, 2024, 03:45 AM UTC

   A blank screen is appearing when users attempt to login to the ClickSend Dashboard This does not appear to be impacting our API, we are aware of the issue and are investigating the cause

2. monitoring Dec 11, 2024, 03:49 AM UTC

   A fix has been implemented and we are monitoring the results. Please clear your browsers cache if you are still experiencing this issue

3. resolved Dec 11, 2024, 04:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 03, 2024, 10:32 PM UTC· resolved Dec 04, 2024, 12:31 AM UTC

1. investigating Dec 03, 2024, 10:32 PM UTC

   The issue has been identified and we have applied a fixed; we are currently monitoring it.

2. investigating Dec 03, 2024, 10:46 PM UTC

   The issue has been identified and we have applied a fixed; we are currently monitoring it.

3. identified Dec 03, 2024, 11:00 PM UTC

   The issue has been identified and we have applied a fix.

4. resolved Dec 04, 2024, 12:31 AM UTC

   Transactional Emails are stuck in queued status.

Read the full incident report →

Started Nov 29, 2024, 01:05 AM UTC· resolved Nov 29, 2024, 04:10 AM UTC

1. investigating Nov 29, 2024, 01:05 AM UTC

   We have identified an issue on the Telstra network where SMS delivery to Telstra handsets appears to be delayed. We are awaiting feedback from Telstra. Other carriers are not affected.

2. identified Nov 29, 2024, 02:39 AM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring Nov 29, 2024, 02:40 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Nov 29, 2024, 04:10 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 21, 2024, 09:38 AM UTC· resolved Nov 22, 2024, 04:48 AM UTC

1. investigating Nov 21, 2024, 09:38 AM UTC

   Quick Letters via the Dashboard is not taking uploads at the moment. The technical team is working to investigate the issue. We will keep you updated as we make progress towards resolution. Thank you for your patience and understanding. We strongly recommend you subscribe to our status page to get latest updates https://status.clicksend.com/#

2. investigating Nov 21, 2024, 09:39 AM UTC

   We are continuing to investigate this issue.

3. identified Nov 21, 2024, 10:05 AM UTC

   The issue has been identified and a fix is being implemented.

4. resolved Nov 22, 2024, 04:48 AM UTC

   This incident has been resolved.

Read the full incident report →