Freshservice Outage History

Freshservice in the Asia Pacific (Sydney) region entered a scheduled maintenance window, impacting 15 components including API, Authentication, Login, Sandbox, Freddy AI Agent, Chat, Search, Third Party Services, Custom Objects, Workflow, Activities & Audit Log, Freshcaller, Reporting, Ticket - Service Request, and Mobile App. Users in Sydney may have experienced limited access or degraded capability during the window.

It began at Feb 27, 2026 1:31 PM UTC and concluded at Feb 27, 2026 2:31 PM UTC, lasting about 1 hour. The Sydney maintenance was acknowledged on the Freshservice status page, with components transitioning from up to maintenance and back to up once the window ended. The impact was regional (Sydney) and did not indicate a global outage.

Freshservice scheduled a maintenance window affecting four components in US East (NORTH VIRGINIA): Login, Activities & Audit log, Search, and Custom Objects. The maintenance lasted about one hour, from Feb 21, 2026 2:31 AM UTC to Feb 21, 2026 3:31 AM UTC, during which those features were temporarily unavailable or degraded. The Freshservice status updates indicated the changes, with the components moving from up to maintenance and then back to up, after which normal operation resumed.

Freshservice conducted a scheduled maintenance window in the Middle East and Africa (MEA) region, placing dozens of components across Web App, API, Email, and Mobile Apps into maintenance. This likely caused temporary limitations accessing features such as Sandbox, Login, Billing, Projects, Tickets, and related services during the window. The maintenance lasted from 8:31 AM UTC to 9:31 AM UTC and services returned to normal afterward. Freshservice posted two official status updates during the incident. The activity was regional to MEA with no indicated global impact.

Freshservice conducted a scheduled regional maintenance window affecting 8 components across INDIA (MUMBAI) and EU CENTRAL (FRANKFURT). Affected components included Activities & Audit log, Login, Search, and Custom Objects in both regions. The maintenance window began on 2:31 AM UTC and was resolved by 4:31 AM UTC, lasting about 2 hours. During the window, Mumbai components returned to normal operation by 3:31 AM UTC, while Frankfurt components remained under maintenance until 4:31 AM UTC.

Freshservice conducted a scheduled maintenance window affecting the Web App and Billing components. The maintenance window began at 4:31 AM UTC and concluded at 9:31 AM UTC, lasting approximately five hours. During the window, the Web App and Billing features were listed as maintenance on the status page. Freshservice issued two official updates to communicate the maintenance: one announcing the start at Feb 8, 2026 4:31 AM UTC and another confirming the completion at Feb 8, 2026 9:31 AM UTC.

Freshservice in the Asia Pacific (Sydney) region underwent a planned maintenance window that affected four components: Custom Objects, Login, Activities & Audit log, and Search. The window began at 11:31 AM UTC and ended at 12:31 PM UTC, lasting about 1 hour. The incident was communicated via two status updates on the Freshservice status page, first noting the start of maintenance and later confirming that all affected components were back online. The maintenance was localized to the Sydney region, with services restored after the window.

A scheduled maintenance window for Freshservice began at 11:31 AM UTC and concluded at 12:31 PM UTC. During this hour, 10 Web App and MEA region components were placed into maintenance, including Web App / Project Management, Web App / Marketplace, Web App / Billing, Web App / Tickets, Web App / Dashboard, Web App / Analytics, MEA / Login, MEA / Custom Objects, MEA / Activities & Audit log, and MEA / Search. The maintenance window was followed by a return to normal operation with two status updates posted on the Freshservice status page.

Freshservice reported a degradation of Freddy AI Agent in the EU Central (Frankfurt) region caused by a third-party service provider outage. The incident began at Jan 27, 2026 11:21 AM UTC and affected Freddy AI Agent operations in EUC, potentially impacting automated tasks and agent assistance for users in that region.

Two official status updates were issued during the incident, and the issue was resolved by Jan 27, 2026 5:56 PM UTC, with the Freddy AI Agent returning to normal operation in EUC. The outage lasted 6 hours 35 minutes and was localized to the EU Central (Frankfurt) region; there was no reported global impact.

Freshservice experienced an outage affecting custom mail servers using Office 365, disrupting both incoming and outgoing email for users. The incident began at 9:11 PM UTC and was resolved by 8:21 AM UTC, lasting roughly 11 hours and 10 minutes. Users reported delays and failures in sending and receiving messages during the event.

The service page reflected a degraded mail service during the incident, with 3 official updates issued to communicate progress and resolution. The updates spanned the initial notice, a follow-up clarification, and the eventual restoration.

Freshservice experienced performance degradation in the Mumbai region starting at 10:41 AM UTC due to issues with a third-party service. The degradation affected 16 Mumbai components across the Web App and API layers, including API, Authentication, Mobile App, Chat, Search, Ticket - Service Request, Workflow, Activities & Audit log, Freshcaller, Freddy AI Agent, On-Call Management, Custom Objects, Reporting, and Login, among others. Users likely faced slower responses and intermittent access during the incident. The outage lasted until 12:36 PM UTC, a total duration of about 1 hour 55 minutes.