Vendor reports: degradedResolved · vendor status “resolved”Official status API

Freshdesk: Degradation in tickets UI

Reported by Freshworks · Customer Support · source last read just now

Official source (opens in a new tab)
Vendor start
Sep 16, 2026, 10:35 UTC
Vendor's clock
Resolved
Sep 16, 2026, 13:18 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:42 UTC
Statuswall's clock
Duration
2 h 43 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Freshworks reports degraded: "Freshdesk: Degradation in tickets UI".[E1, E2]
  • The vendor marked it resolved at 2026-09-16 13:18 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 02:42 UTC · summary s1, evidence c5b30e27569debbe

Evidence (8)
  1. E1Freshworks reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Freshdesk: Degradation in tickets UI". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-09-16 10:35 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-09-16 13:18 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 02:42 UTC. (Statuswall)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

Freshworks is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Sep 16, 2026, 10:35 UTCVendor-reported startVendor time
  2. Sep 16, 2026, 13:18 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:42 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall