CallRail Outage History

15 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live CallRail status100.00% uptime history

Every Recorded CallRail Incident

CallRail incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 23, 2026Incident at Unbounce affecting operability to the integration.The incident has been resolved.6h 30mResolved
Sep 1, 2026Vendour Outage Causing Degraded Call Performance and Recording AvailibilityThis incident has been resolved.6h 23mResolved
Aug 28, 2026Issue Rendering the Call or Form Log on the CallRail iOS Mobile ApplicationThis incident has been resolved. To implement the fix, please update your CallRail Mobile application to version 6.12.1 or later.5h 10mResolved
Aug 20, 2026Integrations Connection ErrorThis incident has been resolved.41 minResolved
Aug 20, 2026Transcriptions API TimeoutThis incident has been resolved.1h 12mResolved
Aug 17, 2026PCI Insights DelayThis incident has been resolved, and PCI Insights should be processing normally.56 minResolved
Jun 23, 2026Scheduled maintenance for CallRail ApplicationsThe scheduled maintenance has been completed.2h 0mScheduled
May 8, 2026Lead Center incoming call notification issue on iOSThis incident has been resolved.17h 5mResolved
Apr 8, 2026Scheduled maintenance for CallRail ApplicationsThe scheduled maintenance has been completed.30 minScheduled
Mar 2, 2026Degraded Performance in Report Export PipelineThis incident has been resolved and the report backlog is now empty.12h 51mResolved
Feb 24, 2026Systemwide Scheduled MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Feb 3, 2026Intermittent Call Failover to Voice MailThis issue has been resolved with the vendor, and systems are now operating normally.19 minResolved
Jan 29, 2026Latency in transcript deliveryWe are no longer seeing transcript latency. This issue has been resolved.1h 44mResolved
Jan 29, 2026SMS and MMS Provider DelaysThe remaining areas of messaging impact have been resolved.23h 19mResolved
Dec 4, 2025Systemwide Scheduled MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next CallRail incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This CallRail Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before CallRail acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single CallRail outage in this window ran 23h 19m, against a mean recovery of 5h 43m. If you depend on CallRail in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.