FrontSpin Outage History

FrontSpin is up right now

FrontSpin had 14 outages in the last 2 years totaling 5h 56m of downtime — averaging 0.6 incidents per month.

There were 14 FrontSpin outages since March 25, 2026 totaling 5h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.frontspin.com

Major September 4, 2026

Calling unavailable on p2.f...

Detected by Pingoru
Sep 04, 2026, 02:45 PM UTC
Resolved
Sep 04, 2026, 03:08 PM UTC
Duration
23m
Affected: TitanX Dialer (Frontspin Page - Platform P2)TitanX Dialer (Titanx Dialer - Login P2)
Timeline · 2 updates
  1. investigating Sep 04, 2026, 03:00 PM UTC

    Calling is currently unavailable on https://p2.frontspin.com. The platform itself is available and all other functions are working normally. We are looking into it.

  2. resolved Sep 04, 2026, 03:08 PM UTC

    The Issue has been resolved. The team will continue to monitor the situation closely.

Read the full incident report →

Major August 29, 2026

P2 is unavailable

Detected by Pingoru
Aug 29, 2026, 02:05 PM UTC
Resolved
Aug 29, 2026, 02:59 PM UTC
Duration
54m
Affected: TitanX Dialer (Titanx Dialer - Login P2)
Timeline · 2 updates
  1. investigating Aug 29, 2026, 02:05 PM UTC

    The team is aware and working at resolving the issue.

  2. resolved Aug 29, 2026, 02:59 PM UTC

    P2 is available.

Read the full incident report →

Minor August 18, 2026

API and Salesforce sync del...

Detected by Pingoru
Aug 18, 2026, 02:56 PM UTC
Resolved
Aug 18, 2026, 03:10 PM UTC
Duration
14m
Affected: TitanX Dialer (Frontspin Page - Platform P2)
Timeline · 2 updates
  1. investigating Aug 18, 2026, 02:56 PM UTC

    We are investigating delayed API responses and delays in Salesforce data synchronization affecting customers on the P2 platform. Our team is working to identify the cause. We will post an update as soon as we know more.

  2. resolved Aug 18, 2026, 03:10 PM UTC

    This issue has been resolved. API responses and Salesforce synchronization on the P2 platform have returned to normal. Thank you for your patience.

Read the full incident report →

Minor July 13, 2026

Login issues for EU based u...

Detected by Pingoru
Jul 13, 2026, 08:03 PM UTC
Resolved
Jul 13, 2026, 08:03 PM UTC
Duration
Affected: TitanX Dialer (Titanx Dialer - Login APP)TitanX Dialer (Titanx Dialer - Login P2)
Timeline · 1 update
  1. investigating Jul 13, 2026, 08:03 PM UTC

    we're investigating an issue related to login from EU

Read the full incident report →

Major July 7, 2026

P2 Unavailable

Detected by Pingoru
Jul 07, 2026, 10:47 PM UTC
Resolved
Jul 07, 2026, 11:46 PM UTC
Duration
59m
Affected: TitanX Dialer (Frontspin Page - Platform P2)TitanX Dialer (Frontspin Swagger Page - Public Api - Platform P2)TitanX Dialer (Titanx Dialer - Login P2)
Timeline · 2 updates
  1. investigating Jul 07, 2026, 10:47 PM UTC

    P2 is currently unavailable. The Frontspin Team is investigating the issue

  2. resolved Jul 07, 2026, 11:46 PM UTC

    P2 is now available.

Read the full incident report →

Minor June 23, 2026

P2 Platform – Degraded Plat...

Detected by Pingoru
Jun 23, 2026, 01:17 PM UTC
Resolved
Jun 23, 2026, 04:14 PM UTC
Duration
2h 57m
Affected: TitanX Dialer (Frontspin Page - Platform P2)TitanX Dialer (Frontspin Swagger Page - Public Api - Platform P2)TitanX Dialer (Titanx Dialer - Login P2)
Timeline · 4 updates
  1. investigating Jun 23, 2026, 01:17 PM UTC

    We are investigating processing delays with p2.frontspin.com. We will provide updates as soon as possible.

  2. investigating Jun 23, 2026, 01:17 PM UTC

    We are investigating processing delays on p2.frontspin.com that are impacting customers' ability to use the platform. We will provide updates as soon as possible.

  3. resolved Jun 23, 2026, 02:22 PM UTC

    We working to implement a fix. Please note that call transcriptions are currently unavailable on P2. We will provide further updates soon.

  4. resolved Jun 23, 2026, 04:14 PM UTC

    All Frontspin systems are now operating as normal. Please reach out to [email protected] or [email protected] if you are continuing to experience any impacts. We identified the root cause of the issues occurring on Frontspin's P2 instance and our team has made a fix. The Frontspin team is continuing to monitor our systems to ensure there are no further impacts to our clients. Please note that following functionality was impacted on P2 during this from approximately 4:30am US ET through noon US ET: - Call transcriptions - Sending emails - Password resets - Phone number assignment - Admin panel and settings

Read the full incident report →

Minor June 6, 2026

P2 Login unresponsive

Detected by Pingoru
Jun 06, 2026, 02:15 PM UTC
Resolved
Jun 06, 2026, 02:21 PM UTC
Duration
6m
Affected: TitanX Dialer (Titanx Dialer - Login P2)
Timeline · 2 updates
  1. investigating Jun 06, 2026, 02:15 PM UTC

    The team is aware of the incident and investigating. Updates soon.

  2. resolved Jun 06, 2026, 02:21 PM UTC

    The issue has been resolved.

Read the full incident report →

Minor May 29, 2026

Calling issues US carrier

Detected by Pingoru
May 29, 2026, 05:17 PM UTC
Resolved
May 29, 2026, 05:40 PM UTC
Duration
23m
Affected: TitanX Dialer (Frontspin Page - Platform APP)TitanX Dialer (Frontspin Page - Platform P2)TitanX Dialer (Frontspin Swagger Page - Public Api - Platform App)TitanX Dialer (Frontspin Swagger Page - Public Api - Platform P2)TitanX Dialer (Titanx Dialer - Login APP)TitanX Dialer (Titanx Dialer - Login P2)
Timeline · 2 updates
  1. investigating May 29, 2026, 05:17 PM UTC

    We are investigating an issue related to the inability to make calls using the US carrier. We will post another update in 15mins. For any additional assistance, please reach out to [email protected]

  2. resolved May 29, 2026, 05:40 PM UTC

    Update: We identified an intermittent calling issue affecting our US carrier beginning at 1:04 PM EST. As of 1:30 PM EST, the issue appears to have resolved, but we are continuing to investigate with our carrier and will provide further updates as we have them. We apologize for any disruption this may have caused. If you continue to experience issues, please reach out to [email protected].

Read the full incident report →