Skip to content
Back to GenesysIncident Postmortem
Genesys logo

Genesys

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Genesys: vendor-reported critical incident on September 18 (tracked 3d 22h)

Sep 18, 07:42 PM → Sep 22, 05:45 PM · 3d 22h · high

Genesys reported a critical-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 3d 22h, from Fri, 18 Sep 2026 19:42:41 GMT to Tue, 22 Sep 2026 17:45:16 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
3d 22h
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 18, 07:42 PM

    The vendor reported a critical-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 18, 07:42 PM

    Status updated: possible issue

  3. Sep 22, 05:45 PM

    PulseWatch closed the incident

Official updates

  1. Sep 18, 07:42 PM

    Genesys reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: fallback