Podia Outage History

Podia is up right now

Pingoru has recorded 10 incidents for Podia: 8 in the last 12 months and 0 in the last 90 days.

Source: status.podia.tech

10incidents recorded
8last 12 months
0last 90 days
2 daystypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Podia in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202629 of 720 (1%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202615 of 744 (1%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 578 (0%)

Incidents, newest first

Minor July 26, 2026 PDF certificates and invoices unavailable 4h 49m App

Started Jul 26, 2026, 09:44 AM UTC· resolved Jul 26, 2026, 02:33 PM UTC

  1. investigating Jul 26, 2026, 09:44 AM UTC

    We’ve identified that PDF generation for invoices and certifications is currently offline and are actively investigating. We’ll share updates here as soon as we have them. We apologize for any trouble this causes.

  2. monitoring Jul 26, 2026, 11:07 AM UTC

    We’ve fixed the issue, and are monitoring our systems as they return to normal. Thank you for your patience!

  3. resolved Jul 26, 2026, 02:33 PM UTC

    We’ve successfully fixed this issue, and all systems are back online. Thank you for your patience!

Read the full incident report →

Minor April 21, 2026 Application errors loading pages 8h 59m App

Started Apr 21, 2026, 12:49 PM UTC· resolved Apr 21, 2026, 09:48 PM UTC

  1. investigating Apr 21, 2026, 12:49 PM UTC

    We’ve identified that some creators are experiencing time-out errors navigating the app, and are actively investigating. We’ll share updates here as soon as we have them. We apologize for any trouble this causes.

  2. investigating Apr 21, 2026, 01:54 PM UTC

    We’re working hard to identify the root cause causing some creators to experience time-out errors while navigating the app. Thanks for your patience and apologies for any trouble.

  3. identified Apr 21, 2026, 02:36 PM UTC

    We’ve identified a potential root cause that’s causing some creators to experience time-out errors across the app. We are working on a remediation.

  4. identified Apr 21, 2026, 07:15 PM UTC

    Some creators are are experiencing time-out errors when navigating the app. We’re actively implementing updates to improve performance.

  5. monitoring Apr 21, 2026, 09:26 PM UTC

    We’re monitoring our systems as they return to normal. Thank you for your patience!

  6. resolved Apr 21, 2026, 09:48 PM UTC

    We’ve successfully fixed this issue, and all systems are back online. Thank you for your patience!

Read the full incident report →

Minor January 9, 2026 "Something went wrong" error editing courses 25m

Started Jan 09, 2026, 09:39 PM UTC· resolved Jan 09, 2026, 10:04 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor December 20, 2025 Security Update: Reminder to Watch for Phishing Emails 15d 17h

Started Dec 20, 2025, 07:43 PM UTC· resolved Jan 05, 2026, 01:04 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical December 5, 2025 App and sites offline 13m

Started Dec 05, 2025, 09:13 AM UTC· resolved Dec 05, 2025, 09:26 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor November 18, 2025 Elevated error rates 1h 46m

Started Nov 18, 2025, 01:12 PM UTC· resolved Nov 18, 2025, 02:59 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical October 21, 2025 Background processing offline 12m

Started Oct 21, 2025, 03:05 PM UTC· resolved Oct 21, 2025, 03:18 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor October 20, 2025 Chat support performance issues 6h 17m

Started Oct 20, 2025, 02:35 PM UTC· resolved Oct 20, 2025, 08:52 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →