VanillaSoft Outage History

VanillaSoft is up right now

There were 8 VanillaSoft outages since February 4, 2026 totaling 40h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.vanillasoft.com

Major April 22, 2026

VoIP-Clarity Platform-Calls not Routing, Calls Not Transferring, Click to Dial not Functioning for some of our clients

Detected by Pingoru
Apr 22, 2026, 02:29 PM UTC
Resolved
Apr 22, 2026, 07:27 PM UTC
Duration
4h 58m
Affected: VanillaSoft VoIP/SMS
Timeline · 5 updates
  1. investigating Apr 22, 2026, 02:29 PM UTC

    We are currently investigating an issue impacting some clients on the Clarity platform. At this time, users may experience the following issues: Calls not routing to available agents Inability to transfer calls Click-to-dial functionality not working Our VoIP engineers are actively investigating the root cause and working to restore full service as quickly as possible. We apologize for the inconvenience this is causing and appreciate your patience and understanding. Please be assured this incident is being treated as a high priority.

  2. investigating Apr 22, 2026, 03:18 PM UTC

    Our VoIP engineers continue to actively investigate the issue impacting the Clarity platform. Clients may still experience the following issues: Calls not routing to available agents Inability to transfer calls Click-to-dial functionality not working At this time, we are still investigating the root cause and do not yet have an ETA for resolution. We sincerely apologize for the ongoing inconvenience and appreciate your continued patience and understanding. Please be assured this incident remains a high priority.

  3. investigating Apr 22, 2026, 05:23 PM UTC

    We would like to provide a further update regarding the ongoing issue impacting the Clarity platform. Call transfer and click-to-dial functionality have now been restored. Our teams are continuing to work on resolving the remaining issue affecting inbound call routing to available agents. We are actively investigating and working to restore full service as quickly as possible. At this time, there is still no confirmed ETA for full resolution. We apologize for the continued inconvenience and appreciate your patience and understanding. This incident remains a high priority.

  4. monitoring Apr 22, 2026, 06:33 PM UTC

    We are pleased to advise that inbound calls have now resumed and are flowing correctly. All previously reported service issues have now been addressed. Our teams will continue to closely monitor the platform to ensure stability. If you are still seeing issues with your inbound calls, please reach out to Customer Support so that we may address them real-time. We appreciate your patience and understanding throughout this incident and apologize for any inconvenience caused.

  5. resolved Apr 22, 2026, 07:27 PM UTC

    We are pleased to confirm that all previously reported issues impacting the Clarity platform have now been fully resolved. Services are operating normally, including inbound call routing, call transfers, and click-to-dial functionality. We sincerely apologize for the inconvenience caused and thank you for your patience and understanding throughout this incident.

Read the full incident report →

Critical April 15, 2026

Failed to Enable Error for some VoIP Users

Detected by Pingoru
Apr 15, 2026, 09:39 PM UTC
Resolved
Apr 16, 2026, 12:45 AM UTC
Duration
3h 6m
Affected: VanillaSoft VoIP/SMS
Timeline · 4 updates
  1. investigating Apr 15, 2026, 09:39 PM UTC

    We are currently investigating an issue where some clients may be experiencing failures when attempting to enable SIP on VS Connect, resulting in 408 timeout errors. Our engineering team is actively engaged and working to identify the root cause and implement a resolution as quickly as possible. We will provide updates as more information becomes available. In the meantime, if you are experiencing this issue or have additional details to share, please contact support.

  2. investigating Apr 15, 2026, 09:48 PM UTC

    Our engineering team is continuing to actively investigate the issue affecting SIP enablement on VS Connect, which may be resulting in 408 timeout errors for some clients. At this time, the issue remains under investigation, and our teams are working to determine the root cause and next steps toward resolution. We will share further updates as soon as more information becomes available. Thank you for your continued patience.

  3. monitoring Apr 15, 2026, 10:23 PM UTC

    We are seeing signs of recovery, and systems are beginning to come back online. Our team is currently monitoring performance closely to ensure stability as services are restored. We will continue to observe the situation and provide further updates as needed. Thank you for your patience.

  4. resolved Apr 16, 2026, 12:45 AM UTC

    The issues relating to Failed to Ena le and SIP errors are now resolved. Thank your for your patience and understanding. We apologize for any inconvenience this interruption may have caused.

Read the full incident report →

Major March 24, 2026

Intermittent Failed to Enable (SIP Error 500) for VoIP Users

Detected by Pingoru
Mar 24, 2026, 08:12 PM UTC
Resolved
Mar 24, 2026, 11:14 PM UTC
Duration
3h 1m
Affected: VanillaSoft VoIP/SMS
Timeline · 3 updates
  1. investigating Mar 24, 2026, 08:12 PM UTC

    We are currently investigating reports that some clients are experiencing a “Failed to Enable (SIP 500)” error when attempting to use their VoIP services. Our engineering team has been engaged and is actively working to identify the root cause. Additionally, some users may experience intermittent lag when navigating the portal. We will continue to provide updates as more information becomes available. Thank you for your patience and understanding.

  2. monitoring Mar 24, 2026, 08:45 PM UTC

    At this time, inbound and outbound calling services are operational and calls are flowing as expected. Portal navigation has stabilized and is performing normally. We will continue to monitor the situation and provide updates as more information becomes available. Should you have any questions or require assistance, please contact our Customer Support team. Thank you for your continued patience and understanding.

  3. resolved Mar 24, 2026, 11:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 17, 2026

Inbound and outbound calls issues

Detected by Pingoru
Mar 17, 2026, 07:27 PM UTC
Resolved
Mar 18, 2026, 07:50 PM UTC
Duration
1d
Affected: VanillaSoft VoIP/SMS
Timeline · 4 updates
  1. investigating Mar 17, 2026, 07:27 PM UTC

    We are currently experiencing an issue affecting both incoming and outgoing calls. Our voip team is actively investigating the root cause. Impacts: This issue may result in abnormal delays or an inability to initiate or receive calls. Additionally, users may encounter a 500 error when using VS Connect. We will provide updates as more information becomes available.

  2. monitoring Mar 17, 2026, 07:44 PM UTC

    Inbound and Outbound calls are now working. We will continue to monitor. If you encounter any issues, please reach out to customer support. Thank you for your patience and we apologize for any inconvenience this service outage may have caused.

  3. monitoring Mar 18, 2026, 12:04 AM UTC

    We are still monitoring our VoIP systems. Some clients are still reporting failed to enable instances when attempting to place or receive a call. We understand the importance of quickly addressing these issues and are working diligently towards a resolution. We will continue to provide updates as they become available. Thank you for your patience. Should you have any questions or concerns, please contact our Customer Support team during our operating hours or via email at [email protected]

  4. resolved Mar 18, 2026, 07:50 PM UTC

    This issues is now resolved. If you are still experiencing issues, please contact our customer support team at 972-200-0179 option 2 during business hours or by email at [email protected]. Thank you for your patience and we apologize for any inconveniences this may have caused.

Read the full incident report →

Major March 13, 2026

Inbound and Outbound Call Issue

Detected by Pingoru
Mar 13, 2026, 03:56 PM UTC
Resolved
Mar 13, 2026, 05:18 PM UTC
Duration
1h 22m
Affected: VanillaSoft VoIP/SMS
Timeline · 3 updates
  1. investigating Mar 13, 2026, 03:56 PM UTC

    We are currently experiencing an issue affecting incoming and outgoing calls due to an IP backbone issue. This could potentially cause abnormal delays or an inability to initiative or receive calls. Our engineers are working on resolving this as quickly as possible. We will continue to provide updates as they become available. We apologize for the inconvenience this is causing.

  2. monitoring Mar 13, 2026, 04:08 PM UTC

    Issues with inbound and outbound calls have been resolved. We will continue to monitor to ensure stability. Thank you for your patience, and we apologize for the inconvenience this has caused.

  3. resolved Mar 13, 2026, 05:18 PM UTC

    The affected IP backbone carrier has implemented a solution, and we are monitoring the results. Service is currently restored to normal operations.

Read the full incident report →

Critical February 11, 2026

Failed to Enable SIP 408 Error

Detected by Pingoru
Feb 11, 2026, 03:37 PM UTC
Resolved
Feb 11, 2026, 06:44 PM UTC
Duration
3h 7m
Affected: VanillaSoft VoIP/SMS
Timeline · 5 updates
  1. investigating Feb 11, 2026, 03:37 PM UTC

    We are currently investigating Failed to Establish SIP 408 errors. This is affecting all inbound and outbound dialing. This will also impact VM Drop deliverability. We understand the impacts that is causing you and we are working quickly to resolve. For more information, please follow our status page https://status.vanillasoft.com/ Thank you for your patience.

  2. investigating Feb 11, 2026, 03:53 PM UTC

    Our VOIP engineers are investigating an issue with their network provider in one of their data centers. We will provide more updates as they become available. Thank you for your patience, and we apologize for any inconveniences this is causing.

  3. identified Feb 11, 2026, 04:13 PM UTC

    Our VOIP engineers have identified the issue and are working to resolve. We will provide additional updates as soon as they become available. Thanking you all for your patience and understanding. Please continue to engage our status page for real-time updates https://status.vanillasoft.com/

  4. monitoring Feb 11, 2026, 04:52 PM UTC

    The resolution has been fully implemented, and we are moving the incident into a monitoring state. We will continue to monitor for one to two hours. Please contact the Customer Support if you continue to experience issues. Thank you for your patience and we apologize for any inconvenience this has caused.

  5. resolved Feb 11, 2026, 06:44 PM UTC

    This incident is considered resolved. If you encounter further issues relating to SIP Error 408, please reach out to our customer support team. Thank you for your patience and understanding.

Read the full incident report →

Notice February 5, 2026

Voip Failed to Establish Error-Outbound Dialing

Detected by Pingoru
Feb 05, 2026, 03:57 PM UTC
Resolved
Feb 05, 2026, 04:12 PM UTC
Duration
15m
Affected: VanillaSoft VoIP/SMS
Timeline · 2 updates
  1. investigating Feb 05, 2026, 03:57 PM UTC

    We are showing a recurrence with the Failed to Establish Error for outbound dialing. Our engineers are fully engaged and are looking into the cause. We will provide an update as soon as possible

  2. resolved Feb 05, 2026, 04:12 PM UTC

    Outbound calls are now working. We will continue to monitor to ensure stability. If you experience any issues, please contact our Customer Support Team. Thank you.

Read the full incident report →

Major February 5, 2026

Voip Failed to Establish Error

Detected by Pingoru
Feb 05, 2026, 03:16 PM UTC
Resolved
Feb 05, 2026, 03:50 PM UTC
Duration
33m
Affected: VanillaSoft VoIP/SMS
Timeline · 4 updates
  1. investigating Feb 05, 2026, 03:16 PM UTC

    We are aware of an outage affecting the ability to dial on our VOIP service. Clients are reporting when attempting to dial out, they are receiving a "Failed to Establish Call" error message. Our engineers are currently investigating the root cause and working to address this as quickly as possible. We appreciate your patience. We apologize for the inconvenience this is causing.

  2. investigating Feb 05, 2026, 03:16 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Feb 05, 2026, 03:41 PM UTC

    Our engineers have identified the issue as being the Clarity Freeswitch gateways. Our voip engineers have implemented a fix and services are resuming and showing as operational. We will continue to monitor to ensure stability. If you are still encountering issues, please reach out to our Customer Support Team at 1-972-200-0179 option 2. Thank you for your understanding.

  4. resolved Feb 05, 2026, 03:50 PM UTC

    The Failed to Establish Call errors on Outbound calls is now resolved. Clients are confirming that they can now place outbound calls successfully. Thank you for your patience and understanding. We apologize for any inconvenience this may have caused. If you have any further questions or you are still experiencing issues, please contact our Customer Support Team. Thank you.

Read the full incident report →

Looking to track VanillaSoft downtime and outages?

Pingoru polls VanillaSoft's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when VanillaSoft reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track VanillaSoft alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring VanillaSoft for free

5 free monitors · No credit card required