Skip to content
Back to AircallIncident Postmortem
Aircall logo

Aircall

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Aircall: vendor-reported major incident on October 1 (tracked 1h 29m)

Oct 1, 05:50 AM → Oct 1, 07:20 AM · 1h 29m · high

Aircall reported a major-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 1h 29m, from Thu, 01 Oct 2026 05:50:33 GMT to Thu, 01 Oct 2026 07:20:28 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
1h 29m
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. Oct 1, 05:50 AM

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

  2. Oct 1, 05:50 AM

    Status updated: possible issue

  3. Oct 1, 07:20 AM

    PulseWatch closed the incident

Official updates

  1. Oct 1, 05:50 AM

    Aircall 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