Airtame Outage History

Airtame is up right now

Airtame had 2 outages in the last 2 years totaling 19h 52m of downtime — averaging 0.1 incidents per month.

There were 2 Airtame outages since September 24, 2025 totaling 19h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.airtame.com

Major October 27, 2025

Unable to Join call in Google Meet

Detected by Pingoru
Oct 27, 2025, 02:33 PM UTC
Resolved
Oct 27, 2025, 03:58 PM UTC
Duration
1h 25m
Affected: Airtame Rooms
Timeline · 2 updates
  1. identified Oct 27, 2025, 02:33 PM UTC

    We have identified an issue preventing users from joining Google Meet calls. Our team is actively working on resolving the problem, and a hotfix will soon be deployed.

  2. resolved Oct 27, 2025, 03:58 PM UTC

    The issue preventing users from joining Google Meet calls has been resolved following the deployment of a hotfix.

Read the full incident report →

Major September 24, 2025

Unable to connect to Virtual Airtame Android via Pairing Code

Detected by Pingoru
Sep 24, 2025, 08:09 PM UTC
Resolved
Sep 25, 2025, 02:36 PM UTC
Duration
18h 27m
Affected: Virtual Airtame Android
Timeline · 3 updates
  1. investigating Sep 24, 2025, 08:09 PM UTC

    We are currently investigating an issue affecting connections to Virtual Airtame on Android. Some users are experiencing problems when attempting to pair using the provided code. Our team is actively working to identify the cause and will share updates as soon as more information is available.

  2. monitoring Sep 25, 2025, 01:09 PM UTC

    We identified an issue affecting connections to Virtual Airtame on Android, where some users experienced problems pairing with the provided code. The problem was caused by the logic handling FCM notifications. We have applied a hotfix and are currently monitoring to ensure the issue remains resolved.

  3. resolved Sep 25, 2025, 02:36 PM UTC

    The issue affecting connections to Virtual Airtame on Android, where some users experienced problems pairing with the provided code, has been resolved. The root cause was identified in the logic handling FCM notifications, and a fix has been applied. We have monitored the situation and confirmed that the service is now fully operational.

Read the full incident report →