Buddy Punch Outage History

Buddy Punch is up right now

Pingoru has recorded 28 incidents for Buddy Punch: 3 in the last 12 months and 0 in the last 90 days.

Source: status.buddypunch.com

28incidents recorded
3last 12 months
0last 90 days
6 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Buddy Punch 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 202600 of 720 (0%)
May 202614 of 744 (1%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 524 (0%)

Incidents, newest first

Minor May 22, 2026 Elevated Errors 4h 6m Web Application (app.buddypunch.com), API

Started May 22, 2026, 07:42 PM UTC· resolved May 22, 2026, 11:48 PM UTC

  1. investigating May 22, 2026, 07:42 PM UTC

    We're experiencing an elevated level of errors and are currently looking into the issue.

  2. monitoring May 22, 2026, 10:10 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 22, 2026, 11:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2025 Cloudflare outage impacting Buddy Punch 5h 4m Main Web Site and Blog (buddypunch.com), Web Application (app.buddypunch.com), API

Started Nov 18, 2025, 12:56 PM UTC· resolved Nov 18, 2025, 06:01 PM UTC

  1. monitoring Nov 18, 2025, 12:56 PM UTC

    Our partner Cloudflare has identified the problem and mentions that the issues are being worked on. We’re monitoring the situation. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  2. monitoring Nov 18, 2025, 01:01 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Nov 18, 2025, 03:46 PM UTC

    Cloudflare has posted an update, they are still mitigating several issues after their latest fix https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  4. monitoring Nov 18, 2025, 05:26 PM UTC

    Cloudflare has seen errors and latency return to normal levels, but hasn’t marked its issue as resolved yet. We will continue to monitor the situation, but we expect the issue to be fully resolved shortly.

  5. resolved Nov 18, 2025, 06:01 PM UTC

    Cloudflare services are currently operating normally. We are no longer observing elevated errors.

Read the full incident report →

Minor October 29, 2025 Partial Outage — Static Assets via Azure CDN 8h 57m Web Application (app.buddypunch.com)

Started Oct 29, 2025, 04:14 PM UTC· resolved Oct 30, 2025, 01:11 AM UTC

  1. identified Oct 29, 2025, 04:14 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Oct 29, 2025, 04:40 PM UTC

    A fix has been implemented and we're monitoring the results

  3. resolved Oct 30, 2025, 01:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 12, 2025 Website down (mobile and web apps still available) 1h 42m Main Web Site and Blog (buddypunch.com)

Started Jun 12, 2025, 06:33 PM UTC· resolved Jun 12, 2025, 08:15 PM UTC

  1. identified Jun 12, 2025, 06:33 PM UTC

    There is an issue with our web host that they are resolving. This affects buddypunch.com, but not app.buddypunch.com or any of our mobile apps. Users can still use our apps without issue. This is just our marketing site, buddypunch.com, that is affected.

  2. resolved Jun 12, 2025, 08:15 PM UTC

    Our website is back up and running.

Read the full incident report →

Notice June 5, 2025 Website down (app not affected) 1h 6m Main Web Site and Blog (buddypunch.com)

Started Jun 05, 2025, 01:04 PM UTC· resolved Jun 05, 2025, 02:10 PM UTC

  1. identified Jun 05, 2025, 01:04 PM UTC

    There is an issue with our web host that they are resolving. This affects buddypunch.com, but not app.buddypunch.com or any of our mobile apps. Users can still use our apps without issue. This is just our marketing site, buddypunch.com, that is affected.

  2. resolved Jun 05, 2025, 02:10 PM UTC

    This incident has been resolved.

Read the full incident report →