- Detected by Pingoru
- Oct 15, 2026, 09:46 AM UTC
- Resolved
- Oct 15, 2026, 12:37 PM UTC
- Duration
- 2h 51m
Affected: Email
Timeline · 3 updates
-
investigating Oct 15, 2026, 09:46 AM UTC
Some customers are experiencing issues where incoming emails are not being converted into tickets, Our engineering team is actively investigating the issue and working to restore normal functionality as quickly as possible.
-
identified Oct 15, 2026, 11:15 AM UTC
Our team is actively working on a fix, and we will provide another update shortly.
-
resolved Oct 15, 2026, 12:37 PM UTC
Our engineering team has restored the issue, Incoming email processing is now operating normally. Emails received during the incident have been processed. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Sep 18, 2026, 07:00 PM UTC
- Resolved
- Sep 19, 2026, 12:27 PM UTC
- Duration
- 17h 27m
Affected: Social
Timeline · 4 updates
-
investigating Sep 18, 2026, 07:00 PM UTC
We are currently investigating an issue affecting some customers in the US region. Customers may experience delays in receiving messages from social channels, including WhatsApp, Facebook, and Instagram. As a result, some customers may also experience delays in ticket creation through these channels. Our team is actively working to identify the root cause and restore normal service as quickly as possible. We will provide another update as soon as more information becomes available.
-
investigating Sep 19, 2026, 06:30 AM UTC
Our engineering team is working to resolve the issue as a high priority. We will keep you informed and share further updates as soon as more information becomes available.
-
in progress Sep 19, 2026, 11:30 AM UTC
Our engineering team has identified the issue and is actively working on mitigation to restore normal processing of incoming messages from social channels in the US region. Further updates will be shared as progress is made.
-
resolved Sep 19, 2026, 12:27 PM UTC
The issue affecting incoming messages from social channels in the US region has been resolved. Message processing and ticket creation are now functioning normally. We have been monitoring the service to confirm stability.
Read the full incident report →
- Detected by Pingoru
- Sep 16, 2026, 10:35 AM UTC
- Resolved
- Sep 16, 2026, 01:18 PM UTC
- Duration
- 2h 43m
Affected: Ticketing CoreTicketing CoreTicketing CoreTicketing CoreTicketing Core
Timeline · 2 updates
-
investigating Sep 16, 2026, 10:35 AM UTC
We identified an issue affecting the rendering of the Tickets page, which caused parts of the user interface to display incorrectly or become unavailable. This issue has been resolved and the Tickets page is now operating normally.
-
resolved Sep 16, 2026, 01:18 PM UTC
Read the full incident report →
- Detected by Pingoru
- Sep 15, 2026, 01:44 AM UTC
- Resolved
- Sep 15, 2026, 07:46 AM UTC
- Duration
- 6h 2m
Affected: Integrations: Freshcaller, Freshservice, Slack & Others
Timeline · 4 updates
-
investigating Sep 15, 2026, 01:44 AM UTC
We are currently experiencing an issue affecting incoming and outgoing calls for a subset of customers. Our engineering team is actively investigating and working to resolve this as a top priority. We will share another update as soon as more information becomes available.
-
identified Sep 15, 2026, 06:30 AM UTC
Our engineering team has identified the issue affecting both incoming and outgoing calls and is actively working toward a resolution. We will continue to provide updates as progress is made.
-
monitoring Sep 15, 2026, 07:30 AM UTC
A fix has been deployed, and we are currently monitoring the service to ensure stability. We will continue to share updates as needed.
-
resolved Sep 15, 2026, 07:46 AM UTC
The issue affecting incoming and outgoing calls for a subset of customers has been resolved. Our team will continue to monitor the service to ensure ongoing stability.
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2026, 12:02 AM UTC
- Resolved
- Sep 09, 2026, 12:43 AM UTC
- Duration
- 41m
Affected: Chat & Messaging
Timeline · 2 updates
-
investigating Sep 09, 2026, 12:02 AM UTC
We experienced a performance issue impacting Chat & Messaging from 5:32 AM IST to 6:13 AM IST on September 9, 2026. Our engineering team identified the root cause and implemented a fix. Chat & Messaging is now functioning as expected.
-
resolved Sep 09, 2026, 12:43 AM UTC
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2026, 07:45 AM UTC
- Resolved
- Sep 04, 2026, 02:47 PM UTC
- Duration
- 7h 2m
Affected: EmailEmailEmailEmailEmail
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Sep 02, 2026, 05:18 PM UTC
- Resolved
- Sep 03, 2026, 09:00 AM UTC
- Duration
- 15h 42m
Affected: Agent PortalCustomer PortalEmailChat & MessagingSocialSLARouting & Agent AvailabilityWorkflow & AutomationsAI Agents & BotsTicketing CoreContact & Account ManagementCustom ObjectsAnalytics & ReportingCSATLoginMarketplaceSearchThird Party ServicesIntegrations: Freshcaller, Freshservice, Slack & OthersAPIBillingSandboxAgent PortalCustomer PortalEmailChat & MessagingSocialSLARouting & Agent AvailabilityWorkflow & AutomationsAI Agents & BotsTicketing CoreContact & Account ManagementCustom ObjectsAnalytics & ReportingCSATLoginMarketplaceSearchThird Party ServicesIntegrations: Freshcaller, Freshservice, Slack & OthersAPIBillingSandboxAgent PortalCustomer PortalEmailChat & MessagingSocialSLARouting & Agent AvailabilityWorkflow & AutomationsAI Agents & BotsTicketing CoreContact & Account ManagementCustom ObjectsAnalytics & ReportingCSATLoginMarketplaceSearchThird Party ServicesIntegrations: Freshcaller, Freshservice, Slack & OthersAPIBillingSandboxAgent PortalCustomer PortalEmailChat & MessagingSocialSLARouting & Agent AvailabilityWorkflow & AutomationsAI Agents & BotsTicketing CoreContact & Account ManagementCustom ObjectsAnalytics & ReportingCSATLoginMarketplaceSearchThird Party ServicesIntegrations: Freshcaller, Freshservice, Slack & OthersAPIBillingSandboxAgent PortalCustomer PortalEmailChat & MessagingSocialSLARouting & Agent AvailabilityWorkflow & AutomationsAI Agents & BotsTicketing CoreContact & Account ManagementCustom ObjectsAnalytics & ReportingCSATLoginMarketplaceSearchThird Party ServicesIntegrations: Freshcaller, Freshservice, Slack & OthersAPIBillingSandboxIncoming MessagesIncoming MessagesIncoming MessagesIncoming MessagesIncoming Messages
Timeline · 3 updates
-
investigating Sep 02, 2026, 05:18 PM UTC
We are investigating service disruptions caused by a third-party service provider, impacting a subset of customers in the Manila, Philippines region. The third-party provider has acknowledged the issue and we are actively working on a fix and will provide updates as they become available. As a workaround, affected customers can try accessing Freshdesk using a different VPN region.
-
in progress Sep 03, 2026, 08:30 AM 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.
-
resolved Sep 03, 2026, 09:00 AM UTC
The issue has been resolved by our third-party provider. All our services are now fully operational.
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2026, 04:15 PM UTC
- Resolved
- Sep 01, 2026, 03:21 AM UTC
- Duration
- 11h 6m
Affected: EmailEmailEmailEmailEmail
Timeline · 4 updates
-
investigating Aug 31, 2026, 04:15 PM UTC
We’re facing issue with incoming emails for customers who are using Microsoft custom mail server. Users may be unable to authenticate their mailboxes or sync incoming emails.
-
monitoring Aug 31, 2026, 07:30 PM 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.
-
monitoring Aug 31, 2026, 10:00 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.
-
resolved Sep 01, 2026, 03:21 AM UTC
The third-party service provider has resolved the issue. Mailbox authentication and email syncing are now fully operational.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 10:45 AM UTC
- Resolved
- Aug 20, 2026, 11:19 AM UTC
- Duration
- 34m
Affected: Agent PortalAgent Portal
Timeline · 2 updates
-
investigating Aug 20, 2026, 10:45 AM UTC
We experienced intermittent issues while accessing the Freshdesk portal, impacting a subset of customers. The issue has been resolved, and the portal is now operating normally.
-
resolved Aug 20, 2026, 11:19 AM UTC
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2026, 11:28 PM UTC
- Resolved
- Aug 13, 2026, 03:10 AM UTC
- Duration
- 3h 42m
Affected: AI Agents & Bots
Timeline · 2 updates
-
investigating Aug 12, 2026, 11:28 PM UTC
A subset of customers experienced an issue with loading chatbot. The issue has been resolved, and all services are now operating normally.
-
resolved Aug 13, 2026, 03:10 AM UTC
Read the full incident report →
- Detected by Pingoru
- Aug 10, 2026, 09:30 AM UTC
- Resolved
- Aug 10, 2026, 01:15 PM UTC
- Duration
- 3h 45m
Affected: Agent PortalSLAWorkflow & Automations
Timeline · 4 updates
-
investigating Aug 10, 2026, 09:30 AM UTC
We are currently experiencing an issue affecting SLA calculations for tickets. This may impact automatic ticket assignment and automation workflows. Saved list views are also affected for a subset of customers.Our engineering team is actively working to restore full functionality for all affected tickets.
-
identified Aug 10, 2026, 11:00 AM UTC
Our team has identified the issue and is actively working on a fix. We will provide an update once the issue is resolved.
-
identified Aug 10, 2026, 01:05 PM UTC
Our engineering team has identified and fixed the issue affecting new tickets. For the tickets impacted during the affected window, we are currently processing the pending events and working to complete the recovery.
-
resolved Aug 10, 2026, 01:15 PM UTC
The issue affecting SLA calculations, automatic ticket assignment, automation workflows, and saved list views has been resolved. All systems have been restored to normal operation. Our team will continue to monitor closely to ensure continued stability.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2026, 08:39 PM UTC
- Resolved
- Aug 04, 2026, 08:51 PM UTC
- Duration
- 12m
Affected: Ticketing CoreContact & Account Management
Timeline · 2 updates
-
investigating Aug 04, 2026, 08:39 PM UTC
All contact related operations got failed & ticket creation would have been affected. Our engineering team is working on it with high priority and we will keep you posted with further updates.
-
resolved Aug 04, 2026, 08:51 PM UTC
Our engineering team has identified and fixed the issue and all services are back to normal
Read the full incident report →
- Detected by Pingoru
- Aug 03, 2026, 12:10 PM UTC
- Resolved
- Aug 03, 2026, 12:17 PM UTC
- Duration
- 7m
Affected: Agent PortalCustomer PortalEmailChat & MessagingSocialSLARouting & Agent AvailabilityWorkflow & AutomationsAI Agents & BotsTicketing CoreContact & Account ManagementCustom ObjectsAnalytics & ReportingCSATLoginMarketplaceSearchThird Party ServicesIntegrations: Freshcaller, Freshservice, Slack & OthersAPIBillingSandboxIncoming Messages
Timeline · 2 updates
-
investigating Aug 03, 2026, 12:10 PM UTC
Freshdesk experienced service disruption during which the application was inaccessible. The issue has now been resolved, and services have been fully restored.
-
resolved Aug 03, 2026, 12:17 PM UTC
Read the full incident report →
- Detected by Pingoru
- Jul 19, 2026, 07:40 AM UTC
- Resolved
- Jul 19, 2026, 09:23 AM UTC
- Duration
- 1h 43m
Affected: SocialSocialSocialSocial
Timeline · 2 updates
-
investigating Jul 19, 2026, 07:40 AM UTC
We experienced a service disruption affecting WhatsApp message delivery due to an issue with a third-party service provider. During the incident window, Agent and Bot messages sent through the WhatsApp channel may have experienced delays or failed to deliver. The third-party provider has since resolved the underlying issue, and message delivery has been fully restored. Our teams monitored the recovery to ensure services returned to normal operation.
-
resolved Jul 19, 2026, 09:23 AM UTC
Read the full incident report →
- Detected by Pingoru
- Jun 21, 2026, 07:41 AM UTC
- Resolved
- Jun 21, 2026, 08:06 AM UTC
- Duration
- 25m
Affected: Analytics & Reporting
Timeline · 2 updates
-
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.
-
resolved Jun 21, 2026, 08:06 AM UTC
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 04:06 PM UTC
- Resolved
- Jun 17, 2026, 10:59 PM UTC
- Duration
- 6h 53m
Affected: SocialSocialSocialSocialSocial
Timeline · 2 updates
-
investigating Jun 17, 2026, 04:06 PM UTC
We are currently investigating an issue affecting WhatsApp onboarding integrations, where customers may encounter failures while adding new numbers to WhatsApp. At this time, existing WhatsApp conversations continue to function normally. The impact is currently limited to onboarding new numbers. Our team is actively working with the service provider to determine the root cause and restore normal onboarding functionality as quickly as possible.
-
resolved Jun 17, 2026, 10:59 PM UTC
The issue impacting WhatsApp onboarding integrations has been resolved. The onboarding process is now functioning as expected. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 04:30 AM UTC
- Resolved
- Jun 17, 2026, 01:20 PM UTC
- Duration
- 8h 50m
Affected: AI Agents & Bots
Timeline · 2 updates
-
investigating Jun 17, 2026, 04:30 AM UTC
A subset of customers experienced degraded Freshchat performance that may have caused some conversations to be transferred to live agents; the issue has been resolved, services are operating normally.
-
resolved Jun 17, 2026, 01:20 PM UTC
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 06:36 PM UTC
- Resolved
- Jun 15, 2026, 10:51 PM UTC
- Duration
- 4h 15m
Affected: SocialSocialSocialSocialSocial
Timeline · 4 updates
-
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.
-
investigating 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.
-
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.
-
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 →
- Detected by Pingoru
- Jun 15, 2026, 07:40 AM UTC
- Resolved
- Jun 15, 2026, 09:40 AM UTC
- Duration
- 2h
Affected: Agent PortalSocialContact & Account Management
Timeline · 2 updates
-
investigating Jun 15, 2026, 07:40 AM UTC
We are currently experiencing intermittent issues with note creation, replying from tickets to other channels, and creating, updating, or listing contacts and companies (including deletion). Our engineering team is actively working to resolve these issues with high priority.
-
resolved Jun 15, 2026, 09:40 AM UTC
The issue has been resolved, and services are operating normally. Our team will continue to monitor the system to ensure stability.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 01:38 PM UTC
- Resolved
- Jun 12, 2026, 05:00 PM UTC
- Duration
- 3h 22m
Affected: SocialSocialSocialSocialSocial
Timeline · 4 updates
-
investigating Jun 12, 2026, 01:38 PM UTC
Customers using meta channels for sending / receiving messages will be impacted. Initial investigation points to a disruption with our third-party provider, Meta. Our team is actively monitoring the situation and working closely with the provider. Further updates will be shared as they become available.
-
investigating Jun 12, 2026, 03:00 PM UTC
We've noticed a decrease in error rates and actively monitoring the situation with meta. We'll provide further updates as they become available.
-
investigating Jun 12, 2026, 04:00 PM UTC
we are awaiting further updates from the third-party service provider while they continue their investigation into the root cause. We will share additional updates as more information becomes available.
-
resolved Jun 12, 2026, 05:00 PM UTC
The issue affecting message sending and receiving across Meta channels has been resolved. All impacted services are now operating normally. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 02:00 PM UTC
- Resolved
- Jun 10, 2026, 06:00 PM UTC
- Duration
- 4h
Affected: Agent PortalSocialContact & Account Management
Timeline · 3 updates
-
investigating Jun 10, 2026, 02:00 PM UTC
We are currently experiencing intermittent issues with note creation, replying from tickets to other channels, and creating, updating, or listing contacts and companies (including deletion). Our engineering team is actively working to resolve these issues with high priority.
-
investigating Jun 10, 2026, 03:30 PM UTC
Our team continues to work on implementing and validating the fix for the identified issue. We are closely monitoring the situation and will provide further updates as progress is made.
-
resolved Jun 10, 2026, 06:00 PM UTC
The issue has been resolved, and services are operating normally. Our team will continue to monitor the system to ensure stability.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 12:15 PM UTC
- Resolved
- Jun 05, 2026, 12:46 PM UTC
- Duration
- 31m
Affected: Routing & Agent Availability
Timeline · 2 updates
-
investigating Jun 05, 2026, 12:15 PM UTC
We experienced temporary latency in automatic ticket assignment. Our engineering team investigated the issue, identified the root cause, and implemented a fix. All systems are now operating normally.
-
resolved Jun 05, 2026, 12:46 PM UTC
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 08:00 AM UTC
- Resolved
- May 27, 2026, 03:06 PM UTC
- Duration
- 7h 6m
Affected: Integrations: Freshcaller, Freshservice, Slack & OthersIntegrations: Freshcaller, Freshservice, Slack & OthersIntegrations: Freshcaller, Freshservice, Slack & OthersIntegrations: Freshcaller, Freshservice, Slack & OthersIntegrations: Freshcaller, Freshservice, Slack & Others
Timeline · 3 updates
-
investigating May 27, 2026, 08:00 AM UTC
We are currently experiencing issues impacting some of our services. Our engineering teams are actively investigating the situation and working towards resolution.We will share further updates as more information becomes available.
-
identified May 27, 2026, 11:30 AM UTC
The issue has been identified and our team is currently working on mitigation and recovery steps. Further updates will be shared as progress is made.
-
resolved May 27, 2026, 03:06 PM UTC
The issue has been successfully mitigated, and services have remained stable following the implemented recovery measures. Continuous monitoring is in place to ensure sustained system stability.
Read the full incident report →
- Detected by Pingoru
- May 23, 2026, 12:00 AM UTC
- Resolved
- May 26, 2026, 10:34 PM UTC
- Duration
- 3d 22h
Affected: SocialSocialSocialSocialSocial
Timeline · 5 updates
-
investigating May 23, 2026, 12:00 AM UTC
We are currently investigating an issue affecting the Instagram media comments inflow, where end users attaching media in comments will not be visible in product. There is no impact to the text messages being sent as comments. Our team is actively working with the service provider to determine the root cause. We’ll keep you informed of any updates.
-
investigating May 23, 2026, 06:00 AM UTC
We continue to actively investigate the Instagram media comments issue with Meta on priority. At this time, we are awaiting further updates from Meta while they continue their investigation into the root cause. We will share additional updates as more information becomes available.
-
investigating May 24, 2026, 06:00 AM UTC
Our investigation into the Instagram media comments inflow issue is ongoing in coordination with the service provider. We are continuing to work closely with the service provider to identify the root cause and restore normal functionality. Further updates will be shared as more information becomes available.
-
investigating May 26, 2026, 05:55 AM UTC
We are still actively engaged with the service provider regarding the Instagram media comments inflow issue. Joint efforts are ongoing to further assess the situation and determine the underlying cause. Normal functionality has not yet been fully restored, and we will continue to share updates as progress is made.
-
resolved May 26, 2026, 10:34 PM UTC
The issue impacting Instagram media comments inflow has been resolved. Media attachments in Instagram comments are now working as expected. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 03:03 PM UTC
- Resolved
- May 20, 2026, 03:15 PM UTC
- Duration
- 12m
Affected: Third Party Services
Timeline · 2 updates
-
investigating May 20, 2026, 03:03 PM UTC
We are currently experiencing an issue with our third-party service provider that is affecting our product functionality. Our engineering team is currently investigation the issue and will share the updates as soon as available.
-
resolved May 20, 2026, 03:15 PM 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 →