AI-powered ITSM solution for streamlined IT operations.
There were 83 Freshservice outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
Not working for you?
Minor
: Freshservice workflow and email delivery issues in US East
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(15 hours and 20 minutes)
Freshservice reported issues with workflow execution, including web request and orchestration nodes in its US East (North Virginia) region, beginning at . The incident later included email delivery issues. Freshservice marked the affected workflow and orchestration components recovered at , while incoming and outgoing email were restored by .
Minor
: Freshservice email delivery and workflow execution issues
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 day, 13 hours and 39 minutes)
Freshservice reported degraded incoming and outgoing email delivery starting . The email issues remained listed while a separate problem affected Workflow web request and orchestration nodes in the US East (North Virginia) region from . Freshservice marked the workflow and orchestration components recovered later that day, while email delivery was restored by .
Minor
: Freshservice experiences brief email service degradation
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(3 hours)
Freshservice reported an issue affecting email functionality, impacting users relying on email-based notifications and workflows. The incident began at when the status page moved from up to warn with the note 'Issue with Email in Freshservice', and the degraded state persisted for about three hours until when the service returned to normal.
During the incident, Freshservice provided status updates acknowledging the email issue and confirmed remediation, with the service restored to normal later the same day. The disruption appeared isolated to the Email component and did not indicate broader impact to other Freshservice features.
Minor
: Freshservice US East (North Virginia) performance degraded
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 30 minutes)
Freshservice experienced degraded performance in the US East (North Virginia) region beginning at . Users across a broad set of features reported slower responses and intermittent issues, with affected components including Login, Chat, API, Approvals, Activities & Audit log, Freshcaller, Freddy AI Agent, Search, and more. The impact spanned core workflows such as signing in, managing tickets, and using automation and integrations. The issue persisted for roughly two and a half hours before recovery, with services returning to normal by .
Minor
: Freshservice experiences brief email issue
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(45 minutes)
Freshservice reported a brief issue affecting email functionality, resulting in degraded email-related features for a short window. The incident began when the status page moved from up to warn at , and service operation returned to normal by as engineers resolved the issue. The problem primarily impacted email delivery and notifications within Freshservice; the service has since returned to full operation.
Minor
: Freshservice: Freddy AI Agent degraded in EU Central Frankfurt
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 10 minutes)
Freshservice experienced brief degraded performance affecting the Freddy AI Agent in EU Central (Frankfurt). The issue began at and was resolved by , lasting roughly an hour and ten minutes. During this window, users in the region may have encountered slower responses or limited Freddy AI functionality while the component recovered to normal.
Freshservice faced a transient issue impacting its email functionality for about 1 hour and 45 minutes. The incident began at and was resolved by , with the status page describing the event as "Issue with Email in Freshservice." During the window, users may have experienced delays or failures in sending and receiving email notifications and other email-related features. Service return to normal after the issue was resolved.
Minor
: Freshservice regional maintenance affects US EAST (NORTH VIRGINIA) services
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour)
Freshservice conducted a scheduled maintenance window affecting multiple services in the US EAST (NORTH VIRGINIA) region. During the window, several components were placed under maintenance, including API, Login, Approval, Activities & Audit log, Freshcaller, Chat, Freddy AI Agent, Third Party Services, Search, Sandbox, Ticket - Service Request, Workflow, Mobile App, Authentication, Reporting, and Custom Objects. The maintenance started at and concluded at .
During the window, users in the affected area may have experienced temporary access limitations to those services; all components returned to normal operation after the maintenance window.
Minor
: Freshservice global search issues affect Sydney search and Freddy AI Agent
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 10 minutes)
Freshservice reported a temporary issue with Global search, impacting the Sydney region's Search component and the Freddy AI Agent in Sydney and Frankfurt. The problem began at and degraded search-related functionality for a period. By , Freddy AI Agent in Sydney and Frankfurt had returned to normal, and the Sydney Search component had recovered by . The incident appeared localized to search-related features with no wider impact.
Minor
: Freshservice global search degraded; AI Agent issues in Sydney & Frankfurt
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 20 minutes)
Freshservice experienced degraded performance beginning at , with the global search feature and Freddy AI Agent showing issues. The impact was observed in the Asia Pacific (Sydney) and Europe Central (Frankfurt) regions, where search results and AI-assisted actions were affected.
The issues persisted as engineers investigated and updates were issued, with recovery progressing over the next couple of hours. All affected components were restored to normal by .