ServiceTitan incident

Phones Pro Issues

Notice Resolved View vendor source →

ServiceTitan experienced a notice incident on June 12, 2025 affecting Telephony Platform: Inbound Calling, lasting 2h 49m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2025, 07:12 PM UTC
Resolved
Jun 12, 2025, 10:01 PM UTC
Duration
2h 49m
Detected by Pingoru
Jun 12, 2025, 07:12 PM UTC

Affected components

Telephony Platform: Inbound Calling

Update timeline

  1. investigating Jun 12, 2025, 07:12 PM UTC

    We are currently experiencing issues with Phones Pro, so ServiceTitan Phones Pro users may be unable to receive inbound calls or make outbound calls. Our 3rd party provider is currently investigating the cause. We will update the status page here as soon as more information becomes available. Thank you for your patience!

  2. investigating Jun 12, 2025, 07:17 PM UTC

    We are currently experiencing issues with Phones Pro, so ServiceTitan Phones Pro users may be unable to receive inbound calls or make outbound calls. Our 3rd party provider is currently investigating the cause. For users affected by the issue, please enable the Call Continuity feature: https://help.servicetitan.com/how-to/how-to-phones-pro-dialpad-outage-procedure#turn-on-call-continuity until services are fully restored. We will update the status page here as soon as more information becomes available. Thank you for your patience!

  3. identified Jun 12, 2025, 07:28 PM UTC

    Our provider has identified the issue and a fix is being implemented. We will update the status page here as soon as more information becomes available. Thank you for your patience!

  4. monitoring Jun 12, 2025, 08:52 PM UTC

    Our provider has implemented a fix and we are monitoring the results. To disable the Call Continuity feature, please see: https://help.servicetitan.com/how-to/how-to-phones-pro-dialpad-outage-procedure#disable-the-continuity-number We will update the status page here as soon as more information becomes available. Thank you for your patience!

  5. resolved Jun 12, 2025, 10:01 PM UTC

    This incident has been resolved.