Freshservice outage history

Freshservice experienced degraded performance in its Web App / Tickets, affecting the Tickets and List views. Users likely faced slower responses, longer load times, and delays when opening or listing tickets. The degradation began at 9:06 AM UTC and persisted for most of the day until a recovery was observed by 6:22 PM UTC.

Status updates described ongoing performance degradation in List view and Tickets, with the Web App / Tickets component returning to normal as the final recovery was observed at 6:22 PM UTC.

Freshservice users experienced degraded automation as the Workflow Automator generated HTTP 400 errors in US EAST (NORTH VIRGINIA) and EU CENTRAL (FRANKFURT). Automated workflow tasks tied to the Workflow component were blocked or failed during the incident. Impact began at 2:56 PM UTC in the two regions and was resolved by 7:17 PM UTC, lasting a little over four hours.

Freshservice conducted a scheduled maintenance window in the US East (NORTH VIRGINIA) region, placing a broad set of components into maintenance mode. Affected areas included Activities & Audit log, API, Approval, Authentication, Chat, Custom Objects, Freddy AI Agent, Freshcaller, Login, Mobile App, Reporting, Sandbox, Search, Third Party Services, Ticket - Service Request, and Workflow. During this window, users could experience limited access or degraded functionality when performing key tasks such as logging in, making API calls, managing tickets, or using chat and reporting features.

The maintenance began at 4:31 AM UTC and concluded at 5:31 AM UTC, with all components returning to normal operation. Freshservice confirms services are back to full functionality following the window.

Freshservice conducted a planned maintenance window in the EU Central (Frankfurt) region, during which a broad set of core components were temporarily placed under maintenance. The window began at 2:31 AM UTC and concluded by 3:31 AM UTC, with services such as Login, API, Search, Ticket - Service Request, Freshcaller, Chat, Freddy AI Agent, Authentication, and Mobile App temporarily affected. The maintenance was regionally scoped to Frankfurt, and all impacted components were returned to normal by the end of the window.

During a scheduled maintenance window in the EU Central (Frankfurt) region, a broad set of Freshservice components including Approval, Activities & Audit log, Login, Freshcaller, Chat, Freddy AI Agent, Third Party Services, Authentication, Search, Ticketing, Mobile App, API, Reporting, Workflow, Custom Objects, and Sandbox were taken offline or operated with degraded functionality. Users may have experienced difficulties with logging in, accessing tickets, utilizing the API, or using the mobile app and chat features during the window. The maintenance began at 2:31 AM UTC and completed by 3:31 AM UTC, with services returning to normal afterward.

Freshservice conducted a scheduled maintenance window in the INDIA (MUMBAI) region, impacting a broad set of components including Web App IT Asset Management, API, Login, Approval, Freshcaller, Freddy AI Agent, Chat, Search, Ticket - Service Request, Sandbox, Workflow, Mobile App, and Reporting. Users in the region may have experienced intermittent access or degraded functionality across these areas during the window.

The maintenance began at 5:31 PM UTC and concluded by 6:31 PM UTC. All listed components returned to normal operation after the maintenance completed.

Freshservice experienced a partial outage affecting the ability to create service requests from catalog items. The issue began in the Asia Pacific Sydney region at 2:46 PM UTC and expanded as related components moved into maintenance, impacting multiple regions. Users were unable to initiate new requests via catalog items during the incident.

Freshservice in the Mumbai (INDIA) region entered maintenance mode at 1:31 AM UTC and completed about an hour later at 2:31 AM UTC. The maintenance affected a broad set of components, including Approval, Activities & Audit log, Login, Freshcaller, Freddy AI Agent, Chat, Third Party Services, Search, Ticket - Service Request, Sandbox, Workflow, Mobile App, API, Authentication, Reporting, and Custom Objects. During the window, users experienced limited access to authentication, login, ticketing, search, and related services, including Freshcaller, API usage, and the mobile app.

Freshservice experienced a regional maintenance event in US East (North Virginia) that briefly disrupted access to core modules. On Sep 13, 2026 2:31 AM UTC, multiple components, including Chat, Workflow, Login, Approval, API, Ticketing, and Mobile App, were placed into maintenance, which led to user-visible interruptions and degraded access to essential workflows. The affected components returned to normal by 3:32 AM UTC, restoring typical functionality in about an hour. A separate maintenance cycle on 9:51 AM UTC briefly moved services from down to up, with full stabilization following soon after.

Freshservice experienced several incidents in September, starting with email delivery issues to Microsoft recipients on 10:41 AM UTC, during which the Email / Outgoing email component entered a degraded state and deliveries were affected until 4:26 PM UTC. A separate incident on 9:56 AM UTC impacted Analytics, with Data Exports missing and a temporary degradation of Web App / Analytics, resolved by 1:06 PM UTC. An additional issue affecting the Resolution Note tab appeared around 3:26 PM UTC and was noted through 3:41 PM UTC.

Then, starting at 2:31 AM UTC, Freshservice in the US East (NORTH VIRGINIA) region entered a maintenance window that affected a broad set of components, including Chat, Workflow, Approval, Login, Activities & Audit log, Freshcaller, Freddy AI Agent, Third Party Services, Search, API, Sandbox, Ticket - Service Request, Mobile App, Authentication, Reporting, and Custom Objects. The maintenance moved to a healthy state by 3:32 AM UTC, with the environment considered stabilized by 9:51 AM UTC. Updates on the status page documented the progression of the window.