Airtame Outage History
Airtame is up right nowPingoru has recorded 12 incidents for Airtame: 1 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 518 (0%) |
Incidents, newest first
Major October 27, 2025 Unable to Join call in Google Meet 1h 25m Airtame Rooms
Started Oct 27, 2025, 02:33 PM UTC· resolved Oct 27, 2025, 03:58 PM UTC
- 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.
- 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.
Major September 24, 2025 Unable to connect to Virtual Airtame Android via Pairing Code 18h 27m Virtual Airtame Android
Started Sep 24, 2025, 08:09 PM UTC· resolved Sep 25, 2025, 02:36 PM UTC
- 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.
- 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.
- 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.