Freshsales Outage History

Started Oct 19, 2026, 01:45 PM UTC· resolved Oct 19, 2026, 02:50 PM UTC

1. investigating Oct 19, 2026, 01:45 PM UTC

   Some customers may experience delays in outgoing email delivery. Our engineering team is actively investigating the issue and working to restore normal functionality as quickly as possible.

2. resolved Oct 19, 2026, 02:50 PM UTC

   Our engineering team has resolved the issue, and outgoing email processing is now operating normally. Emails received during the incident have been processed. We continue to monitor the system closely to ensure ongoing stability.

Read the full incident report →

Started Sep 04, 2026, 07:45 AM UTC· resolved Sep 04, 2026, 02:47 PM UTC

1. investigating Sep 04, 2026, 07:45 AM UTC

   We are aware that some customers may experience delays or failures when sending emails to microsoft recipients, caused by a delivery issue on Microsoft's end (Exchange Online Protection throttling/server busy errors). This is not caused by an issue on our platform. We are actively monitoring the situation and will provide updates as more information becomes available. Affected emails are typically queued and retried automatically; no action is required from customers at this time.

2. investigating Sep 04, 2026, 11:00 AM UTC

   We continue to investigate the email delivery delays affecting some customers sending via Outlook. We have engaged our messaging service provider (MSP) and are working with them to resolve the underlying issue on Microsoft's end. We will post another update as soon as we have more information.

3. resolved Sep 04, 2026, 02:47 PM UTC

   The email delivery issue affecting some customers sending via Outlook has been resolved. The underlying issue on Microsoft's end has been cleared, and previously failed emails have been retried. If you notice any emails still missing, they will be auto-retried and delivered shortly with a slight delay. We apologize for any inconvenience caused.

Read the full incident report →

Started Aug 25, 2026, 04:02 AM UTC· resolved Aug 25, 2026, 06:18 AM UTC

1. investigating Aug 25, 2026, 04:02 AM UTC

   We experienced an issue accessing the Analytics Reports section within the dashboard between 9:32 AM to 10:48 AM, and from 11:14 AM to 11:48 AM. Our team investigated the issue and successfully resolved it. The service has been restored and is functioning as expected.

2. resolved Aug 25, 2026, 06:18 AM UTC

Read the full incident report →

Started Aug 05, 2026, 05:48 AM UTC· resolved Aug 05, 2026, 07:53 AM UTC

1. investigating Aug 05, 2026, 05:48 AM UTC

   We are currently experiencing performance issues impacting contact import and bulk update operations. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible.

2. investigating Aug 05, 2026, 06:00 AM UTC

   Our engineering teams are actively working to mitigate the ongoing issue. We are continuing our investigation and will provide further updates as more information becomes available.

3. resolved Aug 05, 2026, 07:53 AM UTC

   The issue has been resolved. We will continue to monitor it to ensure stability.

Read the full incident report →

Started Jun 21, 2026, 07:41 AM UTC· resolved Jun 21, 2026, 08:06 AM UTC

1. investigating Jun 21, 2026, 07:41 AM UTC

   We experienced intermittent issues impacting Analytics access for some users. The issue has been identified and resolved, and all Analytics services are now operating normally.

2. resolved Jun 21, 2026, 08:06 AM UTC

Read the full incident report →

Started Jun 15, 2026, 06:36 PM UTC· resolved Jun 15, 2026, 10:51 PM UTC

1. investigating Jun 15, 2026, 06:36 PM UTC

   We are currently experiencing issues with outgoing message delivery on WhatsApp channels. This is due to an ongoing issue with a third‑party provider supporting WhatsApp message delivery. Our team is actively monitoring the situation and working with the provider to restore normal service as quickly as possible.

2. identified Jun 15, 2026, 08:30 PM UTC

   Our engineering team is currently working with our third-party provider to resolve the issue with high priority. We will keep you informed and share further updates as soon as more information becomes available.

3. identified Jun 15, 2026, 10:30 PM UTC

   Our engineering team collaborated with our external partner to identify the root cause and implement a fix. Recovery was observed in the US region at 3:25 AM IST, the IN region at 3:50 AM IST, and the EUN region at 3:57 AM IST. We are continuing to work on the remaining affected regions and will share further updates as soon as more information becomes available.

4. resolved Jun 15, 2026, 10:51 PM UTC

   The issue has been resolved in collaboration with our third‑party service provider, and service has been restored across all regions. All systems are now operating normally.

Read the full incident report →

Started May 11, 2026, 02:30 PM UTC· resolved May 11, 2026, 07:44 PM UTC

1. investigating May 11, 2026, 02:30 PM UTC

   We experienced performance issues affecting the search module. Our engineering team has identified and resolved the issue, and the service is now operating normally.

2. resolved May 11, 2026, 07:44 PM UTC

Read the full incident report →

Started May 07, 2026, 11:48 PM UTC· resolved May 08, 2026, 01:50 AM UTC

1. investigating May 07, 2026, 11:48 PM UTC

   We are currently observing a partial outage within our cloud provider’s US-East-1 region, which may be impacting Freshworks services. Our team is actively working with the cloud provider to assess the impact and mitigate the issue. Further updates will be shared as more information becomes available.

2. investigating May 08, 2026, 01:30 AM UTC

   We are working closely with our third-party infrastructure provider as they perform restoration efforts. Our teams are actively taking mitigation steps to minimize the impact on our users and ensure service stability.

3. resolved May 08, 2026, 01:50 AM UTC

   The issue has been resolved and all affected services are now operating normally. We will continue to monitor to ensure stability.

Read the full incident report →

Started Apr 23, 2026, 01:00 PM UTC· resolved Apr 23, 2026, 03:37 PM UTC

1. investigating Apr 23, 2026, 01:00 PM UTC

   We are currently observing performance issues affecting workflow automations. Our engineering team is actively investigating the issue and working to resolve it as quickly as possible.

2. investigating Apr 23, 2026, 02:00 PM UTC

   We are currently addressing performance issues impacting workflow automations. Our engineering team is working on this with the highest priority, and we’ll keep you updated as we move toward resolution.

3. investigating Apr 23, 2026, 03:00 PM UTC

   Our engineering team has identified the issue with workflow automation and has implemented a fix. Workflow automation processing has now resumed and we are closely monitoring the system.

4. resolved Apr 23, 2026, 03:37 PM UTC

   The issue impacting workflow automation has been identified and resolved. All services are operating normally, and we will continue to monitor system performance.

Read the full incident report →

Started Apr 23, 2026, 10:12 AM UTC· resolved Apr 23, 2026, 05:10 PM UTC

1. investigating Apr 23, 2026, 10:12 AM UTC

   We are currently experiencing an issue with outgoing emails pertaining to custom mail server. Our team is actively working towards resolving the issue.

2. resolved Apr 23, 2026, 05:10 PM UTC

   Our engineering team has identified and resolved the issue affecting outgoing emails through custom mail servers. Services have been restored, and we are continuing to monitor system performance to ensure stability.

Read the full incident report →

Started Apr 20, 2026, 07:23 AM UTC· resolved Apr 30, 2026, 10:45 AM UTC

1. investigating Apr 20, 2026, 07:23 AM UTC

   We are currently observing an issue affecting a subset of customers using Microsoft custom mailboxes, resulting in intermittent connectivity issues. As a workaround, reauthenticating the mailbox connection may help restore access. We are actively monitoring the situation and will share further updates as more information becomes available.

2. investigating Apr 20, 2026, 11:30 AM UTC

   We are currently working with our third-party service provider to address this issue. We will share further updates as more information becomes available.

3. investigating Apr 20, 2026, 01:30 PM UTC

   We are continuing to work with our third-party service provider and are seeing progress toward mitigation. We remain focused on restoring full functionality and will share further updates as more information becomes available.

4. investigating Apr 21, 2026, 04:30 PM UTC

   We are actively working with the Microsoft team to investigate connectivity issues impacting some customers using custom mailboxes between their tenant and Microsoft services. This issue is being treated with high priority. If you are experiencing connectivity issues, please raise a high‑priority support ticket directly with Microsoft from your end, while we continue to coordinate closely with the Microsoft team in parallel. As a temporary workaround, customers may try re‑authenticating their mailbox when a disconnection occurs. Further updates will be shared as more information becomes available.

5. investigating Apr 27, 2026, 12:00 PM UTC

   Microsoft has prioritized this issue, and their engineering team continues to work on the investigation. We are closely coordinating with Microsoft to address the connectivity issues affecting some customers using custom mailboxes. If you are still experiencing issues, please consider raising a high‑priority support ticket with Microsoft, which can help speed up resolution. As a temporary workaround, re‑authenticating the mailbox may restore connectivity. We appreciate your patience and will share further updates as they become available.

6. monitoring Apr 29, 2026, 01:45 PM UTC

   We are in touch with Microsoft regarding this issue. They have confirmed that a fix has been implemented; however, it may take some time to fully propagate across all tenants globally. As a result, some customers may already be seeing recovery, while others may continue to experience the issue. At this time, we are still observing errors on our end and are closely monitoring the situation. We expect the next update from Microsoft by May 4th and will share further information as it becomes available.

7. resolved Apr 30, 2026, 10:45 AM UTC

   Our monitoring shows that no further errors have been observed since April 30th at 4:15 PM IST, and the service has been operating normally. While we are still awaiting formal confirmation from Microsoft regarding full global propagation of the fix, the issue is no longer being observed on our end. Given the sustained stability, we are proceeding to mark this incident as resolved. Thank you for your patience and understanding.

Read the full incident report →

Started Apr 19, 2026, 09:17 PM UTC· resolved Apr 20, 2026, 03:31 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Mar 25, 2026, 11:18 AM UTC· resolved Mar 25, 2026, 01:45 PM UTC

1. investigating Mar 25, 2026, 11:18 AM UTC

   We are currently experiencing issues with background workers, which is impacting certain functionalities. Our team is actively investigating and working towards a resolution.

2. investigating Mar 25, 2026, 11:48 AM UTC

   Our engineering team continues to actively work on resolving the latency impacting the affected services. We appreciate your patience and will share additional updates as more information becomes available.

3. investigating Mar 25, 2026, 12:48 PM UTC

   Our engineering team is actively working to mitigate the issue affecting the impacted services. We will continue to share updates as progress is made.

4. resolved Mar 25, 2026, 01:45 PM UTC

   The issue has been resolved and all services are now functioning normally. Our team will continue to monitor the system to ensure stability.

Read the full incident report →

Started Mar 16, 2026, 10:57 AM UTC· resolved Mar 16, 2026, 04:37 PM UTC

1. investigating Mar 16, 2026, 10:57 AM UTC

   We are currently experiencing an issue with the Microsoft Graph API, which is impacting the processing of incoming emails and may cause delays or disruptions. This issue specifically affects customers using Graph-based custom mailboxes.

2. investigating Mar 16, 2026, 01:00 PM UTC

   Our team is actively monitoring the situation and working with the provider to restore normal functionality. We will share further updates as more information becomes available.

3. investigating Mar 16, 2026, 03:00 PM UTC

   We’re seeing signs of recovery, and only a small number of customers may still be experiencing issues. Our team is working on this with top priority, and we’ll keep you updated as we make progress.

4. resolved Mar 16, 2026, 04:37 PM UTC

   The issue with incoming emails caused by the Microsoft Graph API has been resolved. Microsoft has confirmed the root cause was an issue on their end, and email processing is now functioning normally.

Read the full incident report →

Started Mar 02, 2026, 05:22 AM UTC· resolved Apr 20, 2026, 01:30 PM UTC

1. investigating Mar 02, 2026, 05:22 AM UTC

   Due to ongoing AWS infrastructure issues in the UAE, Freshworks is migrating impacted customer data to a secure European facility. For full details and next steps, visit our Community post: https://freshworks.com/medc-bcp

2. investigating Mar 02, 2026, 07:22 AM UTC

   We are working closely with our cloud provider as they perform restoration efforts. Our teams are actively taking mitigation steps to minimise the impact on our users and ensure service stability.

3. investigating Mar 02, 2026, 08:22 AM UTC

   We are currently experiencing a wider impact and have migrated the incident to a Major Outage. Our team is actively involved in mitigating the issue and closely working with our cloud providers to restore normal operations. We will continue to provide further updates as more information becomes available.

4. investigating Mar 02, 2026, 11:45 AM UTC

   We understand the continued disruption this situation is causing for our customers. Our teams are actively engaged with our cloud provider(AWS), who is currently experiencing an issue affecting our service availability in MEA region . We are closely monitoring their progress and working together toward resolution, while carefully considering regional and regulatory requirements. At this time, there is no confirmed timeline for full service restoration. We will continue to share updates as more information becomes available.

5. investigating Mar 02, 2026, 06:30 PM UTC

   Our engineering team is actively monitoring the situation and working closely with AWS to track resolution progress, and we will continue to provide updates as more information becomes available, with the next update within 24 hours or sooner if there is a significant development.

6. investigating Mar 03, 2026, 01:30 PM UTC

   Our engineering team is working urgently to restore services and is closely coordinating with AWS to resolve the ongoing issue in the Middle East region. We recognize the impact this disruption may have on your operations and appreciate your patience during recovery. Restoration efforts are ongoing, and there is currently no ETA for full recovery. We will provide the next update by 03‑Mar‑2026, 5:30 PM PST / 04‑Mar‑2026, 5:30 AM GST.

7. investigating Mar 04, 2026, 02:00 AM UTC

   Our engineering teams continue to monitor the situation and are working in coordination with AWS regarding the ongoing issue affecting the Middle East region. Recovery efforts are ongoing, and overall progress continues to depend on AWS’s restoration of services in the affected region. At this time, there is no confirmed ETA for full service restoration. We appreciate your understanding and the next update will be provided in 6 hours, by 03‑Mar‑2026, 11:30 PM PST / 04‑Mar‑2026, 11:30 AM GST.

8. investigating Mar 04, 2026, 08:30 AM UTC

   Our engineering teams are continuing to make steady progress in restoring data within AWS data centers as part of the ongoing recovery efforts for the Middle East region. We remain closely aligned with AWS throughout the recovery process. While work is progressing, recovery timelines continue to depend on AWS’s restoration of services in the affected region, and a definitive ETA for full recovery is not yet available. The next update will be provided by 04‑Mar‑2026, 8:30 AM PST / 04‑Mar‑2026, 8:30 PM GST.

9. investigating Mar 04, 2026, 06:00 PM UTC

   Our engineering teams continue to work in close partnership with Amazon Web Services to restore data and services impacted in the Middle East data centers. In line with AWS guidance, we are actively evaluating options to recover and restore customer instances in an alternate, secure region outside the Middle East as part of our next recovery steps. While we are making steady progress, the overall recovery timeline remains dependent on the availability and accessibility of backups from the affected AWS region. We are closely monitoring developments, coordinating continuously with AWS, and prioritizing full restoration with the highest level of urgency. We understand the disruption this situation may cause to your operations and sincerely appreciate your continued patience and trust. Our teams remain fully engaged to expedite recovery and minimize further impact. The next update will be shared by 04-Mar-2026, 8:30 PM PST / 05-Mar-2026, 8:30 AM GST, or earlier if there is any significant progress to report.

10. investigating Mar 05, 2026, 06:30 AM UTC

    Our engineering teams remain fully engaged in the ongoing recovery efforts impacting the Middle East region. Restoration activities for the affected data and services within AWS data centers are currently in progress, with our teams working closely with AWS to accelerate recovery. In line with prior communications, we have activated established disaster recovery procedures based on AWS guidance and are evaluating the most suitable recovery solution to ensure services are restored in a reliable and efficient manner. We understand the disruption this situation may cause to your operations and appreciate your patience and continued support. Further updates will be shared as more information becomes available.

11. investigating Mar 06, 2026, 07:00 PM UTC

    Due to ongoing AWS infrastructure issues in the UAE, Freshworks is migrating impacted customer data to a secure European facility. For full details and next steps, visit our Community post: https://www.freshworks.com/medc-bcp/

12. investigating Mar 09, 2026, 01:30 PM UTC

    This update applies to all the customers affected by the ongoing service disruption in the UAE-based data center. As previously shared in our community post (https://www.freshworks.com/medc-bcp/), Freshworks teams are working around the clock with AWS to secure customer data backups and transfer them to a secure European facility, with the goal of restoring services from the European region. Our recovery efforts are currently focused across three key workstreams: Workstream 1: Accessing Data Backups from AWS (UAE Region) Engineering teams continue to work closely with AWS to secure access to backups from the impacted UAE data centers. Good progress has been made in accessing several critical data stores required for service restoration in the European region. However, some critical backups remain inaccessible at this time as recovery depends on AWS restoring access to the underlying physical storage infrastructure at the affected site. As a result, the timeline for full access to all backups remains fluid. Additionally, transferring such large volumes of data is a complex process, and transfer speeds currently depend on the pace of AWS’s ongoing recovery efforts. In parallel, teams are also evaluating alternative approaches to recover the remaining data required to restore services. Workstream 2: Migration of Data Backups to a Secure European Facility As backups are recovered from AWS, teams are simultaneously transferring and migrating the data stores to a secure European facility. This effort is progressing well in parallel with the recovery of backups. Workstream 3: Service Restoration Once the data transfer is complete, you will have the option to restore services from our European data center and resume normal business operations. Given the nature of the recovery efforts outlined above, this remains a complex and multi-phased process involving coordination across multiple systems and teams, including ongoing dependencies on AWS recovery activities. As a result, it is difficult to provide an exact timeline for full restoration at this stage. That said, our teams are making steady progress across all workstreams and continue to prioritize recovery with the highest urgency. We will share further updates as more clarity becomes available.

13. investigating Mar 10, 2026, 05:30 PM UTC

    This update applies to all the customers affected by the ongoing service disruption in the UAE-based data center. Action Required : Confirm if you would like services restored in the EU region While we continue working with AWS on recovering data backups and migrating recovered data to the Europe data center we have initiated parallel efforts to obtain customers confirmation for restoring services in the Europe region. Securing confirmations in advance will help expedite service restoration once the data becomes available and recovery activities are completed. If you are an account administrator, please check your email inbox for instructions about next steps to confirm “Yes” if you would like us to proceed with restoring your services in the EU region or reach out to [email protected]. As indicated previously, our recovery efforts are currently focused across three key workstreams: Workstream 1: Accessing Data Backups from AWS (UAE Region) Engineering teams continue to work closely with AWS to secure access to backups from the impacted UAE data centers. Good progress has been made in accessing several critical data stores required for service restoration in the European region. However, some critical backups remain inaccessible at this time as recovery depends on AWS restoring access to the underlying physical storage infrastructure at the affected site. As a result, the timeline for full access to all backups remains fluid. Additionally, transferring such large volumes of data is a complex process, and transfer speeds currently depend on the pace of AWS’s ongoing recovery efforts. In parallel, teams are also evaluating alternative approaches to recover the remaining data required to restore services. Workstream 2: Migration of Data Backups to a Secure European Facility As backups are recovered from AWS, teams are simultaneously transferring and migrating the data stores to a secure European facility. This effort is progressing well in parallel with the recovery of backups. Workstream 3: Service Restoration Once the data transfer is complete, you will have the option to restore services from our European data center and resume normal business operations. Given the nature of the recovery efforts outlined above, this remains a complex and multi-phased process involving coordination across multiple systems and teams, including ongoing dependencies on AWS recovery activities. As a result, it is difficult to provide an exact timeline for full restoration at this stage. That said, our teams are making steady progress across all workstreams and continue to prioritize recovery with the highest urgency. We will share further updates as more clarity becomes available.

14. in progress Mar 13, 2026, 06:30 PM UTC

    MEA Datacenter Recovery Note: We are pleased to share that significant progress has been made in restoring services following the recent UAE data center disruption. We have begun bringing services back online in the Europe region for affected accounts after securely migrating data to our EU region. The restoration is being carried out in phases based on technical parameters to ensure data integrity and security. What do I need to do? To return to normal operations, please review the following two actions (Please ignore if you have already responded): Confirm "yes": We cannot restore your services without this confirmation. If you have not yet done so, please respond on the below link to confirm "Yes" or email [email protected] to proceed with the restoration of your services in the EU region. http://www.freshworks.com/medc-bcp/consent/ If you have already confirmed "yes" in writing, no further action is required from you. Please review the below link to ensure readiness as your instance is restored in the Europe region. https://support.freshservice.com/support/solutions/articles/50000012022-mec-to-eun-migration-guide How will I know when my services are restored? You will hear from us as soon as your account has been restored and tested for successful operation. Whom do I contact with questions? If you have questions regarding the migration or technical requirements, please email [email protected] or reach out directly to your customer success manager. We appreciate your continued patience as we work to bring your systems back online as quickly and securely as possible.

15. resolved Apr 20, 2026, 01:30 PM UTC

    We understand how important service availability is to your operations, and we sincerely appreciate your patience during this time. This update is specifically for customers whose services are still impacted and remain non-operational in the Middle East Data Center. As part of our ongoing mitigation efforts, we have migrated the majority of impacted customers to the EU region. We are pleased to share that services for these customers are now stable and operating normally. For our remaining customers, we are here to support you through the final step of restoration. With your consent, we can complete your migration to the EU region and restore your services immediately. Please provide your approval by copying and pasting the following link into your browser: http://www.freshworks.com/medc-bcp/consent/ Once your services are restored, you will receive a confirmation email from us indicating that your account has been successfully activated in the new region. At this time, the restoration timeline for the original Middle East region remains uncertain, as our cloud provider, AWS, has not yet provided a confirmed ETA for full service recovery. If you have any questions or would like assistance with the migration process, our support team is available at [email protected]. You may also contact your Customer Success Manager, who is ready to help at every step. This mitigation remains in place as we prepare to resolve the incident on our status page. Thank you for your continued understanding and cooperation as we work to fully restore services for all customers as quickly and securely as possible.

Read the full incident report →

Started Mar 01, 2026, 12:51 PM UTC· resolved Mar 01, 2026, 03:44 PM UTC

1. investigating Mar 01, 2026, 12:51 PM UTC

   We are currently observing partial outage within our cloud provider’s Middle East region, which may potentially impact Freshworks services. At this time, the extent of the impact is still being assessed. Our team is actively working with the cloud provider to investigate and mitigate the issue. We will provide further updates as more information becomes available.

2. identified Mar 01, 2026, 02:00 PM UTC

   We are working closely with our third-party infrastructure provider as they perform restoration efforts. Our teams are actively taking mitigation steps to minimize the impact on our users and ensure service stability.

3. monitoring Mar 01, 2026, 03:00 PM UTC

   Resolution has been implemented, and we are currently in the monitoring phase. We continue to work with our third-party provider to confirm full service restoration and will keep you updated.

4. resolved Mar 01, 2026, 03:44 PM UTC

   Service stability has been restored by routing all traffic from the affected zone to healthy zones. All systems are currently operating normally. A subset of customers may have experienced delays in receiving campaign emails during this time. We continue to monitor the environment closely while awaiting the third-party provider's official resolution.

Read the full incident report →

Started Feb 17, 2026, 07:48 AM UTC· resolved Feb 17, 2026, 08:45 AM UTC

1. investigating Feb 17, 2026, 07:48 AM UTC

   We experienced an issue affecting portal access between 1:18 PM and 2:15 PM IST. The issue has been resolved, and all services are now operating normally.

2. resolved Feb 17, 2026, 08:45 AM UTC

Read the full incident report →

Started Jan 22, 2026, 07:05 PM UTC· resolved Jan 23, 2026, 07:45 AM UTC

1. investigating Jan 22, 2026, 07:05 PM UTC

   Some users may experience delays or failures when sending or receiving emails via Outlook due to an issue with a third-party service. We are actively working with the provider to investigate the issue and will share updates as more information becomes available.

2. investigating Jan 22, 2026, 08:15 PM UTC

   We are working closely with the third-party service provider to fix the issue and we will share further information as soon as it becomes available.

3. investigating Jan 22, 2026, 09:45 PM UTC

   Our team continues to work closely with the third-party service provider and will keep you informed of the progress toward service restoration.

4. monitoring Jan 22, 2026, 11:45 PM UTC

   We continue to collaborate closely with the third-party service provider and will update the progress shortly.

5. investigating Jan 23, 2026, 01:45 AM UTC

   The third-party service provider continues working to resolve the issue and will provide the next update at 9:00 AM IST. We will keep you informed of progress toward full service restoration.

6. monitoring Jan 23, 2026, 03:45 AM UTC

   We’re closely monitoring the situation in coordination with the third-party provider and actively tracking service recovery. We will continue to share timely updates as progress is made.

7. resolved Jan 23, 2026, 07:45 AM UTC

   The issue caused by the third-party provider has been fully resolved, and Email services are now operating normally. We will continue monitoring to ensure stability.

Read the full incident report →

Started Dec 19, 2025, 02:48 PM UTC· resolved Dec 20, 2025, 05:50 AM UTC

1. investigating Dec 19, 2025, 02:48 PM UTC

   We are observing intermittent network performance issues with our third‑party service provider. Our engineering team is actively working with the provider to investigate and resolve the issue. We will share further updates as more information becomes available.

2. investigating Dec 19, 2025, 04:30 PM UTC

   We are currently awaiting further updates from our third‑party service provider. Our team remains engaged and will share additional information as soon as it becomes available.

3. monitoring Dec 19, 2025, 05:30 PM UTC

   Our third‑party service provider has implemented a fix, and we are continuing to monitor system performance to ensure stability. We will provide further updates if any issues are observed.

4. monitoring Dec 19, 2025, 07:30 PM UTC

   Our team is actively monitoring the situation while awaiting updates from the third-party service provider.We will provide the next update once more details are available.

5. monitoring Dec 19, 2025, 09:30 PM UTC

   We are actively monitoring services with our third-party provider and will update once the issue is resolved.

6. monitoring Dec 20, 2025, 12:30 AM UTC

   We are continuing to monitor the services with our third-party provider. We will provide a final update as soon as the issue is fully resolved.

7. investigating Dec 20, 2025, 02:30 AM UTC

   All our services are currently operating normally, with no traffic issues observed at our end for the past 10 hours. However, this status page remains open as the third‑party service provider's status page has not yet been marked as fully resolved. We will close this incident once the issue is officially resolved on their end.

8. resolved Dec 20, 2025, 05:50 AM UTC

   Our systems have been stable since Dec 19, 2025, 23:10 IST, and monitoring dashboards continue to show normal performance. As a result, we are resolving this incident on our status page. We will continue to monitor closely while awaiting official confirmation of full resolution from our third‑party service provider. We appreciate your patience as we remain attentive and continue monitoring our systems.

Read the full incident report →

Started Dec 05, 2025, 08:48 AM UTC· resolved Dec 05, 2025, 09:11 AM UTC

1. investigating Dec 05, 2025, 08:48 AM UTC

   We are currently experiencing an issue with our third-party service provider that is affecting our product functionality. We are actively working with the provider to resolve the issue and will share further updates once they are recovered.

2. resolved Dec 05, 2025, 09:11 AM UTC

   The Issue with our third-party service provider has been resolved. All services are operating as expected, and we are monitoring closely to ensure full stability.

Read the full incident report →

Started Oct 20, 2025, 07:30 PM UTC· resolved Oct 21, 2025, 10:42 AM UTC

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

   Customers are experiencing lag in analytics due to issues that occurred earlier with the cloud service provider. Our engineers are treating this as a top priority and will update us soon on the progress.

2. investigating Oct 21, 2025, 12:30 AM UTC

   We're actively working on improvements, and progress is ongoing. We'll share another update once we have more details.

3. investigating Oct 21, 2025, 03:30 AM UTC

   The team continues to make progress on the ongoing improvements. We'll share the next update as soon as more information becomes available.

4. investigating Oct 21, 2025, 05:30 AM UTC

   Our team is diligently working to resolve the issue. We appreciate your continued patience and will provide updates as progress is made.

5. monitoring Oct 21, 2025, 08:30 AM UTC

   We have identified the issue and are working toward a resolution, while closely monitoring and taking steps to fix it.

6. monitoring Oct 21, 2025, 10:00 AM UTC

   We’re making progress, and full recovery is ongoing. Our team is working to restore all systems and will share updates as we proceed.

7. resolved Oct 21, 2025, 10:42 AM UTC

   The issue has been fully resolved. All systems are now stable and operating as expected.

Read the full incident report →

Started Oct 20, 2025, 07:11 AM UTC· resolved Oct 20, 2025, 08:30 PM UTC

1. investigating Oct 20, 2025, 07:11 AM UTC

   We are currently investigating issues affecting our services hosted on our cloud provider. Users may experience degraded performance or service interruptions during this time. Our team is actively working with the cloud provider team to identify the root cause and restore full functionality as quickly as possible. We will provide further updates as more information becomes available.

2. investigating Oct 20, 2025, 08:00 AM UTC

   We are still experiencing service issues and are closely working with our cloud provider to resolve them. Our teams continue to treat this as a high-priority incident and are actively working toward full recovery. Further updates will be shared as we make progress.

3. investigating Oct 20, 2025, 08:45 AM UTC

   The issue is being addressed by our cloud provider. We are actively monitoring the situation and staying in close contact for timely updates.

4. identified Oct 20, 2025, 09:30 AM UTC

   Our engineers and provider teams are continuing their work toward full recovery. We appreciate your patience and will share the next update as soon as we have more details

5. investigating Oct 20, 2025, 10:00 AM UTC

   We are seeing early signs of recovery. Our cloud provider is actively working toward full restoration. We will keep you updated on the status.

6. investigating Oct 20, 2025, 11:00 AM UTC

   Our cloud provider has nearly restored their services, and we are seeing recovery on our end as well. We are continuing to monitor the situation and will provide a next update once we receive confirmation from the provider.

7. monitoring Oct 20, 2025, 12:00 PM UTC

   Some dependent issues persist following the original outage at our cloud provider. We are monitoring the situation and will share updates as they become available.

8. investigating Oct 20, 2025, 01:30 PM UTC

   Our cloud provider is still working to resolve the remaining issues, which continue to impact some of our services. We will provide further updates as they become available.

9. investigating Oct 20, 2025, 03:00 PM UTC

   The remaining issues with our cloud provider are still being addressed, and some services continue to experience disruption. We'll provide the next update once we have further information.

10. investigating Oct 20, 2025, 04:00 PM UTC

    Our cloud provider has pinpointed the cause of the remaining service disruptions and is working to resolve them. We'll continue to monitor the situation and provide updates as they become available.

11. investigating Oct 20, 2025, 05:00 PM UTC

    The cloud provider has implemented additional measures to resolve the issue. We will keep monitoring the situation and provide updates as soon as they are available

12. investigating Oct 20, 2025, 06:00 PM UTC

    We are still experiencing issues due to the ongoing outage with our cloud provider. Their teams are actively working on resolution, and we continue to monitor the situation closely

13. investigating Oct 20, 2025, 07:00 PM UTC

    Our cloud provider is still working to resolve the issue. We are monitoring the situation closely and will provide the next update within the next two hours

14. monitoring Oct 20, 2025, 07:30 PM UTC

    Our cloud provider has implemented the fix, and all our services have been fully restored. We will continue to monitor the situation closely over the next few hours to ensure stability. The status page will be marked as resolved once we receive final confirmation from our service provider.

15. resolved Oct 20, 2025, 08:30 PM UTC

    The issue has been fully resolved, and all services are now operating normally. We appreciate your patience while we worked with our provider to restore full functionality.

Read the full incident report →

Started Aug 25, 2025, 06:34 PM UTC· resolved Aug 25, 2025, 06:49 PM UTC

1. investigating Aug 25, 2025, 06:34 PM UTC

   A subset of customers was seeing intermittent login failures between 12:04 AM and 12:19 AM IST. The issue is resolved now and login functionality working normal.

2. resolved Aug 25, 2025, 06:49 PM UTC

Read the full incident report →

Started Jul 21, 2025, 08:44 AM UTC· resolved Jul 21, 2025, 09:39 AM UTC

1. investigating Jul 21, 2025, 08:44 AM UTC

   We had a degraded performance in the Analytics module. Analytics module has been successfully resolved. All services are now operating normally.

2. resolved Jul 21, 2025, 09:39 AM UTC

Read the full incident report →

Started Jul 17, 2025, 03:30 PM UTC· resolved Jul 18, 2025, 05:00 AM UTC

1. investigating Jul 17, 2025, 03:30 PM UTC

   Customers encountered delays with Contact, Account, and Deal updates, as well as search functionalities and Workflows.Our engineers have resolved the issue, and all services have returned to normal.

2. resolved Jul 18, 2025, 05:00 AM UTC

Read the full incident report →