Skip to content
Back to Sage IntacctIncident Postmortem
Sage Intacct logo

Sage Intacct

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Sage Intacct: vendor-reported incident on September 22 (tracked 3d 0h)

Sep 22, 03:55 PM → Sep 25, 03:59 PM · 3d 0h · medium

Sage Intacct reported an 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 0h, from Tue, 22 Sep 2026 15:55:37 GMT to Fri, 25 Sep 2026 15:59:22 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
3d 0h
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 22, 03:55 PM

    The vendor reported an incident on its own status page; PulseWatch began tracking it

  2. Sep 24, 11:39 PM

    Status updated: possible issue

  3. Sep 25, 03:59 PM

    PulseWatch closed the incident

Official updates

  1. Sep 22, 03:55 PM

    Sage Intacct 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