Aircall: Public API returning 500 error

What to do

Check whether you use Aircall API & Webhooks. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 33m it lasted.
Anything that failed between 2025-12-17 10:27 UTC and 2025-12-17 11:00 UTC may need a replay.
Subscribe to Aircall's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=aircall works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingDec 17, 2025, 10:27 AM UTC
We are investigating an error on our public API returning 500 error. The issue has been identified and we are working on a corrective release.
provider
identifiedDec 17, 2025, 10:28 AM UTC
The issue has been identified and a fix is being implemented.
provider
monitoringDec 17, 2025, 10:48 AM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedDec 17, 2025, 11:00 AM UTC
Our public API is now working as expected, this incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Aircall still down?

No, this incident was resolved 2025-12-17 11:00 UTC. For Aircall's live state, see https://down.guide/aircall.

How long did it last?

33m, from 2025-12-17 10:27 UTC to 2025-12-17 11:00 UTC, by the times Aircall posted.

What was affected?

Aircall named API & Webhooks.

What caused it?

Aircall hasn't published a root cause. If it does, it shows here.

Where does this come from?

Aircall's official status page, https://status.aircall.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.