Deskbird Outage History

Deskbird is up right now

Deskbird had 4 outages in the last 2 years totaling 7h 26m of downtime — averaging 0.2 incidents per month.

There were 4 Deskbird outages since June 4, 2024 totaling 7h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.deskbird.com

Minor March 2, 2026

Temporary Email Service Imp...

Detected by Pingoru
Mar 02, 2026, 02:30 PM UTC
Resolved
Mar 02, 2026, 06:30 PM UTC
Duration
4h
Affected: Current status by service (api.deskbird.com)Current status by service (app.deskbird.com)
Timeline · 2 updates
  1. investigating Mar 02, 2026, 02:30 PM UTC

    Today between 15:30 and 19:30 CET, email delivery from our production application was temporarily impaired. During this period, system-generated emails (booking confirmations, check-in reminders, etc.) may not have been delivered.

  2. resolved Mar 02, 2026, 06:30 PM UTC

    The email service impairment issue has been identified and resolved, and email functionality is operating normally again. We do not expect any ongoing impact on email deliverability. We apologize for the disruption and appreciate your patience.

Read the full incident report →

Minor September 22, 2025

Service degradation on app....

Detected by Pingoru
Sep 22, 2025, 07:10 AM UTC
Resolved
Sep 22, 2025, 09:00 AM UTC
Duration
1h 50m
Affected: Current status by service (api.deskbird.com)Current status by service (app.deskbird.com)
Timeline · 2 updates
  1. investigating Sep 22, 2025, 07:10 AM UTC

    deskbird is currently investigating an issue causing service degradation on both app.deskbird.com and api.deskbird.com. At this time we do not have an ETA to resolution, but are actively working on identifying and resolving the issue. We will provide an update on the situation once we have additional details.

  2. resolved Sep 22, 2025, 09:00 AM UTC

    From 9:00 to 9:20am Monday, September 22nd deskbird experienced a severe degradation of service on app.deskbird.com and api.deskbird.com. From approximately 9:20 to 10:55am the degradation of service because progressively less severe as deskbird technical staff stabilized the system and implemented a number of real time remediation steps. The root cause was due to a database locking issue within the newly released floor plan service paired with high customer demand for this service, resulting in load that exceeded internal pre-release testing transaction volume. Steps have been taken to prevent further occurrences of this issue in the future.

Read the full incident report →

Major July 22, 2025

Service disruptions on api....

Detected by Pingoru
Jul 22, 2025, 04:06 PM UTC
Resolved
Jul 22, 2025, 05:27 PM UTC
Duration
1h 21m
Affected: Current status by service (api.deskbird.com)Current status by service (app.deskbird.com)
Timeline · 2 updates
  1. investigating Jul 22, 2025, 04:06 PM UTC

    deskbird is currently investigating an issue impacting our application, resulting in api.deskbird.com and app.deskbird.com being unavailable. Our team is actively working to restore full functionality as quickly as possible. Thanks for your patience!

  2. resolved Jul 22, 2025, 05:27 PM UTC

    The previously reported issue impacting api.deskbird.com and app.deskbird.com has been resolved and full functionality has been restored. The root cause of this issue has been identified as an excessively resource intensive database migration. As a result we’ll be updating our pre-release database migration testing procedures to better identify and prevent these issues in the future. Thank you for your patience and understanding.

Read the full incident report →

Minor June 4, 2024

Backend unresponsive

Detected by Pingoru
Jun 04, 2024, 04:03 PM UTC
Resolved
Jun 04, 2024, 04:18 PM UTC
Duration
15m
Affected: Current status by service (api.deskbird.com)Current status by service (app.deskbird.com)
Timeline · 2 updates
  1. investigating Jun 04, 2024, 04:03 PM UTC

    There was a 15min interruption of service during an app update

  2. resolved Jun 04, 2024, 04:18 PM UTC

    The issue was resolved

Read the full incident report →