SignalWire Outage History

Started Oct 23, 2026, 01:52 PM UTC· resolved Oct 23, 2026, 02:02 PM UTC

1. identified Oct 23, 2026, 01:52 PM UTC

   Analytics and usage charts in the SignalWire Dashboard are currently unavailable or may fail to load.

2. resolved Oct 23, 2026, 02:02 PM UTC

   Engineering has applied a fix, restoring the dashboard analytics.

Read the full incident report →

Started Oct 05, 2026, 04:05 PM UTC· resolved Oct 05, 2026, 04:19 PM UTC

1. investigating Oct 05, 2026, 04:05 PM UTC

   An underlying infrastructure issue resulted in a major interruption to all services beginning at 16:05 UTC.

2. resolved Oct 05, 2026, 04:19 PM UTC

   Engineers investigated and applied a fix to rectify the issue resulting in full restoration to all operations at 16:19 UTC.

Read the full incident report →

Started Aug 14, 2026, 07:38 PM UTC· resolved Aug 14, 2026, 09:37 PM UTC

1. investigating Aug 14, 2026, 07:38 PM UTC

   US West region nodes are experiencing high failure rates on outbound calls, including outbound fax and caller ID verification. Other regions are unaffected. SMS and MMS are unaffected in all regions. We have identified the cause and are restoring capacity.

2. investigating Aug 14, 2026, 08:43 PM UTC

   The issue has been identified, and resolution is in progress. Engineers are monitoring as updates roll out and services return to normal.

3. resolved Aug 14, 2026, 09:37 PM UTC

   The resolution has fully applied and the issue is resolved. US West is back to normal capacity and full functionality for outbound calling.

Read the full incident report →

Started Jun 10, 2026, 11:46 AM UTC· resolved Jun 10, 2026, 10:24 PM UTC

1. investigating Jun 10, 2026, 11:46 AM UTC

   We have identified an issue affecting the delivery of event data to the logging UI. As a result, the logging screens may not display lifecycle events for calls (such as “ringing,” “answered,” and “ended”) or messaging. Call and messaging functionality is not impacted. Calls are connecting...

2. resolved Jun 10, 2026, 10:24 PM UTC

   The issue affecting our logging pipeline has been resolved. Logs for calls and messages going forward are being ingested in real time. Backlogged entries from the affected window are still being processed and should appear shortly. We are monitoring progress closely.

Read the full incident report →

Started Jun 04, 2026, 02:00 AM UTC· resolved Jun 05, 2026, 04:04 PM UTC

1. identified Jun 04, 2026, 02:00 AM UTC

   A portion of requests to our AI-powered services are failing intermittently.

2. resolved Jun 05, 2026, 04:04 PM UTC

   Between 2026-06-04 02:00 to 2026-06-05 16:04 UTC, a portion of requests to our AI-powered services failed intermittently. The cause was a provider-side change to the authorization scope of the API credentials used by our integration with an upstream AI provider, which caused affected requests to...

Read the full incident report →

Started May 09, 2026, 01:55 PM UTC· resolved May 09, 2026, 05:35 PM UTC

1. identified May 09, 2026, 01:55 PM UTC

   We have identified an issue with adding a new verified caller id to spaces. When attempting to add a caller id via the dashboard or API, we are failing to send the phone call that allow you to verify your ownership of the number.

2. investigating May 09, 2026, 02:48 PM UTC

   The team has identified the issue and is applying a fix.

3. resolved May 09, 2026, 05:35 PM UTC

   This issue has been resolved.

Read the full incident report →

Started May 06, 2026, 03:27 PM UTC· resolved May 06, 2026, 06:28 PM UTC

1. identified May 06, 2026, 03:27 PM UTC

   Our DCA is reporting issues with DLR deliveries; a subset of Delivery Receipts for concatenated messages will receive an unknown state if submitted via the Conversation or REST APIs. This is currently being investigated by our DCA.

2. resolved May 06, 2026, 06:28 PM UTC

   Our DCA has reported the issue is resolved.

Read the full incident report →