Podium Outage History

Podium is up right now

Podium had 48 outages in the last 2 years totaling 146h 1m of downtime — averaging 2 incidents per month.

There were 48 Podium outages since February 9, 2026 totaling 146h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.podium.com

Minor June 17, 2026

Taxes applying to invoices with no tax

Detected by Pingoru
Jun 17, 2026, 11:03 PM UTC
Resolved
Jun 17, 2026, 11:08 PM UTC
Duration
4m
Affected: Payments
Timeline · 2 updates
  1. identified Jun 17, 2026, 11:03 PM UTC

    We're seeing taxes being applied to invoices that were not supposed to have taxes applied. We're working on a fix now.

  2. resolved Jun 17, 2026, 11:08 PM UTC

    This issue has been resolved.

Read the full incident report →

Minor June 12, 2026

Potential delay in displaying payments/refunds

Detected by Pingoru
Jun 12, 2026, 05:19 PM UTC
Resolved
Jun 12, 2026, 07:38 PM UTC
Duration
2h 19m
Affected: Payments
Timeline · 4 updates
  1. investigating Jun 12, 2026, 05:19 PM UTC

    We are currently investigating an issue, and one of the symptoms is a potential delay in payments/refunds displaying in Podium. Note that this is just a delay in the viewing of the information, not the actual processing of the transactions.

  2. identified Jun 12, 2026, 06:01 PM UTC

    We are continuing to work on a fix for this incident.

  3. monitoring Jun 12, 2026, 06:18 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Jun 12, 2026, 07:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 12, 2026

Facebook outage

Detected by Pingoru
Jun 12, 2026, 02:00 PM UTC
Resolved
Jun 12, 2026, 09:12 PM UTC
Duration
7h 11m
Affected: Messaging
Timeline · 3 updates
  1. identified Jun 12, 2026, 02:00 PM UTC

    We are seeing 500 errors from Facebooks API, we believe this is being caused by a Facebook outage, and will continue to monitor Meta's status.

  2. monitoring Jun 12, 2026, 02:52 PM UTC

    Meta has confirmed an outage on their status page, we have seen improvements in our logs, but are still seeing errors. We will continue to monitor the status page and our logs and will update when the outage is fully resolved.

  3. resolved Jun 12, 2026, 09:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 11, 2026

3rd party outage causing instability with AI Products

Detected by Pingoru
Jun 11, 2026, 10:29 PM UTC
Resolved
Jun 11, 2026, 11:15 PM UTC
Duration
46m
Affected: AI Employee
Timeline · 2 updates
  1. investigating Jun 11, 2026, 10:29 PM UTC

    3rd party outages are causing intermittent failures on API calls. Investigating the source and monitoring

  2. resolved Jun 11, 2026, 11:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 11, 2026

Voice AI transfers will occasionally drop the call and send straight to Voicemail

Detected by Pingoru
Jun 11, 2026, 03:21 PM UTC
Resolved
Jun 11, 2026, 04:10 PM UTC
Duration
48m
Affected: Phones
Timeline · 2 updates
  1. investigating Jun 11, 2026, 03:21 PM UTC

    When our Voice AI agent attempts to transfer to another person or call group, we're seeing the call occasionally drop and send the caller straight to Voicemail. We're actively investigating this issue and working on a fix.

  2. resolved Jun 11, 2026, 04:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 10, 2026

Dropped calls

Detected by Pingoru
Jun 10, 2026, 03:16 PM UTC
Resolved
Jun 10, 2026, 04:40 PM UTC
Duration
1h 24m
Affected: Phones
Timeline · 3 updates
  1. investigating Jun 10, 2026, 03:16 PM UTC

    We are currently investigating an issue causing calls to intermittently drop. We'll provide an update soon

  2. monitoring Jun 10, 2026, 04:31 PM UTC

    We implemented a fix and are currently monitoring the calls.

  3. resolved Jun 10, 2026, 04:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 5, 2026

Android users unable to log into Podium app

Detected by Pingoru
Jun 05, 2026, 03:39 PM UTC
Resolved
Jun 10, 2026, 04:04 PM UTC
Duration
5d
Affected: Mobile
Timeline · 4 updates
  1. investigating Jun 05, 2026, 03:39 PM UTC

    We're seeing users unable to log into the Podium app on Android devices by using their password. If you're running into this issue, going through the "Forgot Password" flow and requesting a One-Time Password is still functional

  2. identified Jun 05, 2026, 04:52 PM UTC

    We've identified the issue affecting users who can't log into Podium using the Android app. We're working on pushing a new version with the fix to the Google Play Store as soon as possible. In the meantime, users are still able to log into the app using a one-time password (by going through the "Forgot Password" flow) or by signing in using Google or Apple sign-in options

  3. monitoring Jun 05, 2026, 06:57 PM UTC

    We've pushed out the app version, 2026.10.0, that contains the fix for this issue and are currently waiting for the Google Play Store to finish their review. This can take a number of hours but we'll update this incident once the update is widely available

  4. resolved Jun 10, 2026, 04:04 PM UTC

    This incident has been resolved. Users should update to 2026.10.0 to resolve this issue.

Read the full incident report →

Minor June 5, 2026

AI Employee responses are delayed

Detected by Pingoru
Jun 05, 2026, 03:10 PM UTC
Resolved
Jun 05, 2026, 03:46 PM UTC
Duration
35m
Affected: AI Employee
Timeline · 2 updates
  1. investigating Jun 05, 2026, 03:10 PM UTC

    We are currently investigating this incident.

  2. resolved Jun 05, 2026, 03:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 3, 2026

Calendar view causing an Uh-Oh Error

Detected by Pingoru
Jun 03, 2026, 07:55 PM UTC
Resolved
Jun 03, 2026, 08:03 PM UTC
Duration
8m
Affected: Web Application
Timeline · 2 updates
  1. identified Jun 03, 2026, 07:55 PM UTC

    We've identified an issue where some customers are seeing an Uh Oh error when viewing the Calendar Page within Podium.

  2. resolved Jun 03, 2026, 08:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026

Xtime Service Degraded

Detected by Pingoru
May 20, 2026, 06:46 PM UTC
Resolved
May 20, 2026, 06:46 PM UTC
Duration
Timeline · 1 update
  1. resolved May 20, 2026, 06:46 PM UTC

    Type: Incident Duration: 40 minutes Affected Components: Automations May 20, 18:46:58 GMT+0 - Identified - We are experiencing intermittent failures when attempting to reach Xtime. They have acknowledged an outage on their end and are working on a fix. Our scheduling service should return to full functionality as soon as their issue has been resolved. This is only affecting Xtime customers and is not a full outage. May 20, 19:26:50 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor May 20, 2026

VinSolutions Leads may not be pulling into Podium

Detected by Pingoru
May 20, 2026, 02:23 PM UTC
Resolved
May 20, 2026, 02:23 PM UTC
Duration
Timeline · 1 update
  1. resolved May 20, 2026, 02:23 PM UTC

    Type: Incident Duration: 3 hours and 30 minutes Affected Components: Marketplace May 20, 17:53:39 GMT+0 - Resolved - This incident has been resolved. May 20, 14:23:11 GMT+0 - Investigating - We're investigating elevated reports of Vinsolutions Leads not pulling into Podium.

Read the full incident report →

Minor May 18, 2026

Leads Synced from Third-Party CRMs may not be pulling into Podium

Detected by Pingoru
May 18, 2026, 07:53 PM UTC
Resolved
May 18, 2026, 07:53 PM UTC
Duration
Timeline · 1 update
  1. resolved May 18, 2026, 07:53 PM UTC

    Type: Incident Duration: 24 minutes Affected Components: Marketplace May 18, 19:53:29 GMT+0 - Investigating - We're investigating elevated reports of leads not pulling into Podium from third-party integrations. May 18, 20:17:13 GMT+0 - Resolved - This incident has been resolved. Leads should be pulling in from third-party CRM's through integrations.

Read the full incident report →

Minor May 18, 2026

AU Phones - Calls not ringing through to users and going straight to voicemail

Detected by Pingoru
May 18, 2026, 01:00 AM UTC
Resolved
May 18, 2026, 01:17 PM UTC
Duration
12h 17m
Affected: Phones
Timeline · 3 updates
  1. investigating May 18, 2026, 01:00 AM UTC

    We are currently investigating this incident.

  2. monitoring May 18, 2026, 01:55 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 18, 2026, 01:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 15, 2026

Xtime Timing Out

Detected by Pingoru
May 15, 2026, 04:41 PM UTC
Resolved
May 15, 2026, 04:41 PM UTC
Duration
Timeline · 1 update
  1. resolved May 15, 2026, 04:41 PM UTC

    Type: Incident Duration: 51 minutes Affected Components: Marketplace May 15, 16:41:36 GMT+0 - Investigating - We're experiencing elevated errors with service integrations using Xtime which may impact ability for appointments to be set. May 15, 17:32:59 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor May 11, 2026

Contact details are not loading

Detected by Pingoru
May 11, 2026, 05:09 PM UTC
Resolved
May 11, 2026, 05:09 PM UTC
Duration
Timeline · 1 update
  1. resolved May 11, 2026, 05:09 PM UTC

    Type: Incident Duration: 23 hours and 52 minutes Affected Components: Contacts May 11, 17:09:03 GMT+0 - Investigating - We're receiving a large number of failures when attempting to load contact details. We're actively investigating the root cause May 12, 17:01:01 GMT+0 - Resolved - This incident has been resolved. May 11, 18:41:57 GMT+0 - Identified - We believe we've identified the root cause of this issue and are working on the best approach to resolution May 11, 19:57:59 GMT+0 - Identified - We're still working on implementing the fix for this issue. We appreciate your patience

Read the full incident report →

Minor May 8, 2026

AI Agent may not be responding

Detected by Pingoru
May 08, 2026, 09:10 PM UTC
Resolved
May 08, 2026, 09:10 PM UTC
Duration
Timeline · 1 update
  1. resolved May 08, 2026, 09:10 PM UTC

    Type: Incident Duration: 5 minutes Affected Components: AI Employee May 8, 21:10:07 GMT+0 - Investigating - We're investigating elevated errors with our AI Agent that may prevent it from responding May 8, 21:14:42 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

Notifications and status updates delayed

Detected by Pingoru
May 08, 2026, 06:33 PM UTC
Resolved
May 08, 2026, 06:33 PM UTC
Duration
Timeline · 1 update
  1. resolved May 08, 2026, 06:33 PM UTC

    Type: Incident Duration: 27 minutes Affected Components: Messaging May 8, 18:33:41 GMT+0 - Identified - We are seeing errors with notifications and status updates on conversations being delayed. We are currently investigating the issue and will add an update when more information available. May 8, 19:00:13 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Major May 8, 2026

Most integrations are down

Detected by Pingoru
May 08, 2026, 04:55 PM UTC
Resolved
May 08, 2026, 04:55 PM UTC
Duration
Timeline · 1 update
  1. resolved May 08, 2026, 04:55 PM UTC

    Type: Incident Duration: 24 minutes Affected Components: Automations May 8, 17:19:07 GMT+0 - Resolved - We have seen integrations return to a normal state. Thank you for your patience May 8, 16:55:17 GMT+0 - Identified - Our partner for integrations is having an outage. While not all integrations are inactive, a large number are. We're actively working with our partners to prioritize the return of our functionality May 8, 17:05:04 GMT+0 - Monitoring - We're starting to see functionality return to normal. We'll continue to monitor to ensure full functionality

Read the full incident report →

Minor May 4, 2026

Increased Errors loading the platform

Detected by Pingoru
May 04, 2026, 03:59 PM UTC
Resolved
May 04, 2026, 03:59 PM UTC
Duration
Timeline · 1 update
  1. resolved May 04, 2026, 03:59 PM UTC

    Type: Incident Duration: 11 minutes Affected Components: Web Application May 4, 15:59:04 GMT+0 - Investigating - We're investigating increased errors where users are unable to load the platform May 4, 16:02:58 GMT+0 - Resolved - This incident has been resolved. May 4, 16:05:29 GMT+0 - Monitoring - We implemented a fix and seeing errors drop. Still monitoring to ensure we are completely resolved. May 4, 16:09:45 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor April 24, 2026

Contact names aren't appearing properly

Detected by Pingoru
Apr 24, 2026, 07:06 PM UTC
Resolved
Apr 24, 2026, 07:06 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 24, 2026, 07:06 PM UTC

    Type: Incident Duration: 2 days, 20 hours and 23 minutes Affected Components: Contacts Apr 24, 20:54:29 GMT+0 - Monitoring - We have found and resolved the root cause of contact names not saving. We discovered other contact changes may also not have saved, like Status changes. We're continuing to investigate the scope of this incident and any other downstream effects caused by it. Apr 27, 15:28:44 GMT+0 - Resolved - We're marking this incident as resolved. We appreciate your patience. Apr 24, 19:06:03 GMT+0 - Investigating - Throughout the app, a contact's name is appearing inconsistently or not appearing at all. We're actively investigating the issue to find a fix

Read the full incident report →

Minor April 23, 2026

New call recordings are not displaying

Detected by Pingoru
Apr 23, 2026, 03:30 PM UTC
Resolved
Apr 23, 2026, 03:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 23, 2026, 03:30 PM UTC

    Type: Incident Duration: 3 hours and 3 minutes Affected Components: Phones Apr 23, 15:30:03 GMT+0 - Investigating - We are currently investigating an issue causing call recordings to not display for new recorded calls. Apr 23, 18:32:59 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor April 22, 2026

AI Agent for Medspa EMR customers not booking events

Detected by Pingoru
Apr 22, 2026, 10:12 PM UTC
Resolved
Apr 22, 2026, 10:12 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 22, 2026, 10:12 PM UTC

    Type: Incident Duration: 15 hours and 8 minutes Affected Components: AI Employee Apr 23, 13:20:39 GMT+0 - Resolved - This incident has been resolved. Apr 22, 22:12:48 GMT+0 - Identified - For Medspa EMR customers using our playbooks agent, the agent is currently unable to book events. The agent is able to take all other actions. Engineering is currently investigating a fix. Apr 22, 22:59:49 GMT+0 - Identified - A fix is currently being investigated.

Read the full incident report →

Minor April 20, 2026

Widespread platform errors

Detected by Pingoru
Apr 20, 2026, 05:43 PM UTC
Resolved
Apr 20, 2026, 05:43 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 20, 2026, 05:43 PM UTC

    Type: Incident Duration: 9 minutes Affected Components: Web Application Apr 20, 17:43:43 GMT+0 - Identified - We're seeing a variety of errors across our platform. We've identified the issue and are working on a fix. We expect these issues to be resolved shortly, but will provide an update once the issue is resolved Apr 20, 17:52:48 GMT+0 - Resolved - We've resolved the issue and our platform is stable once again. Thank you for your patience

Read the full incident report →

Minor April 17, 2026

Issue Processing Data from Third-Party Integrations

Detected by Pingoru
Apr 17, 2026, 05:43 PM UTC
Resolved
Apr 17, 2026, 05:43 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 17, 2026, 05:43 PM UTC

    Type: Incident Duration: 14 minutes Affected Components: Marketplace Apr 17, 17:43:21 GMT+0 - Identified - We’ve identified an issue affecting the processing of data from several third-party integrations. Impacted systems may include CDK, Dealertrack, Tekion, Reynolds & Reynolds, and Shopify. Apr 17, 17:57:40 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor April 17, 2026

Messages getting stuck in "Sending...."

Detected by Pingoru
Apr 17, 2026, 04:10 PM UTC
Resolved
Apr 17, 2026, 04:10 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 17, 2026, 04:10 PM UTC

    Type: Incident Duration: 1 hour and 47 minutes Affected Components: Messaging Apr 17, 16:10:35 GMT+0 - Investigating - we are investigating an issue where messages are getting stuck in "Sending" status. The messages are successfully sending, this is just a visual issue. We will send updates as more information becomes available. Apr 17, 16:17:18 GMT+0 - Monitoring - We rolled back a change that resolved the issue, we will continue to monitor and review to ensure message statuses update properly. Apr 17, 17:57:58 GMT+0 - Resolved - This incident has been resolved. Apr 17, 21:12:33 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →