pingoru pingoru Bird App had 44 outages in the last 2 years totaling 155h 47m of downtime, averaging 1.8 incidents per month.
There were 44 Bird App outages since November 20, 2024 totaling 155h 47m of downtime. Each is summarised below. Incident details, duration, and resolution information.
A change has caused a disruption with the backend for the vehicles, this is currently recovering. Some vehicles will momentarily disconnect and reconnect.
Connections have recovered.
The Firebase SDK used by our iOS app shipped a crashing bug that is impacting all of our iOS App versions at the moment, causing repetitive crashes. We are awaiting a fix from the Google Firebase team to resolve the issue
We have reports that crash rates are going down but no confirmation yet from Firebase that a fix has been deployed
Received update that the Firebase change has been rolled back here: https://github.com/firebase/firebase-ios-sdk/issues/16728#issuecomment-5882457735 Waiting for final confirmation that rollback is complete...
Our crash rate for this issue has gone down to near zero for all app versions. Total impact was around 495 crash events affecting 490 users within the last ~40 minutes. Subsequent app opens appeared to not cause a crash for most users during this time.
We have been advised by Kore that there is an ongoing outage affecting approximately 15% of devices. Kore is actively investigating.
Connections seem to be close to back to normal, still monitoring
99.9% offlines are back online, closing this issue
Kore has identified an issue on Data sessions (https://korewireless.service-now.com/csm?id=service_status&service=cb4ae2ca479f0610ab11f92c016d43f1) Vodafone also seems to be having issues
2026-07-24 10:10 UTC / 2026-07-24 06:10 EDT ( UTC-4): We are seeing recovery, but the issue is not yet fully resolved. KORE Engineers continue to work with the IMSI Sponsor to investigate the root cause of the issue and restore service. We will provide another update in 2 hours or sooner once more information becomes available. no update from Vodafone
This incident has been resolved
We are currently investigating this issue.
The issue was confirmed to be a carrier roaming problem and has been resolved since 15/07/2026 14:30 (UTC)
We are currently investigating this issue.
We have implemented a stop-gap solution to temporarily disable Raven release recommendations to unblock releases in affected markets. As part of this, all nests will be visible and available for release regardless of quality. Unfortunately, it may take up to an hour for this to take effect.
The issue has been identified to be related to Raven v3. The aforementioned stop-gap solution was rolled back and a different stop-gap was implemented to switch all markets over to Raven v2 while we work towards resolution. The same timeline of up to an hour to take effect still applies.
The underlying job failure issue for Raven v3 has been resolved and we have reverted the applicable markets back to this version of the model. It will take up to an for this to take effect, and will will continue to monitor for stability.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
Code deployment rollback has been completed and our systems have begun to stabilize. We will continue to monitor.
This incident has been resolved.
We are currently investigating this issue.
We are seeing gradual recovery and the number of offline bounties is dropping, this may have been due to some deployment/scaling activity, continuing to monitor.
Vodafone has confirmed a global service degradation and is investigating.
Vodafone has implemented a change to restore service, they are continuing to monitor recovery.
Approximately half of affected devices have since reconnected, we are continuing to monitor. Asking local teams to reset devices that have not recovered.
From the telecom operator perspective the incident is resolved. We see the vast majority of devices have reconnected, it may be necessary to reset or troubleshoot any remaining offline vehicles.
We are currently investigating this issue.
Devices have mostly reconnected, we have escalated to our telecom partner, keeping this outage under monitoring until fully recovered.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are working with our external partners to determine root cause and a path towards resolution. We appreciate your continued patience.
Root cause has been identified. We are working with our external partners to determine a long term solution, but in the meantime, we will be rolling back certain code changes believed to be contributing to performance degradation and expect performance recovery shortly.
We have identified root cause and are implementing a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an outage with our rider database, which is impacting ride starts and ride ends. We are actively investigating the issue.
The system appears to be recovering as expected. We will continue to monitor.
The outage is confirmed to be fully resolved and all systems have returned to normal operation.
We are currently investigating this issue.
We have largely recovered and are monitoring the situation, we have escalated to Vodafone support
This incident has been resolved.
We are currently investigating a carrier outage impacting a limited number of vehicles (approximately 300-400) and are working with our carrier partner for next steps.
Our carrier partner has identified the issue and is working towards resolution. There is currently no known ETA.
Hologram is still reporting a partial outage on their FLO profile (G2) 89357* prefix SIMs might be affected we have only observed a very small amount of disconnects on our side
still no changes from Hologram Provider, pending update
Fix is now scheduled for deployment - tomorrow, November 21st at 10:00 AM UTC+2. During this maintenance window, devices will briefly disconnect as sessions are reset. Devices should automatically re-establish connectivity once the change is applied.
The upstream fix has now been deployed, and early checks look good. We’re monitoring session behavior closely as devices cycle through to make sure everything stays stable. We’ll post another update once the rollout is complete and validated. Posted 14 minutes ago. Nov 21, 2025 - 14:33 UTC
no further notifications from the provider data show this outage is now closed
We are currently investigating this issue.
We are continuing to investigate the issue and working with our cloud services provider to identify root cause.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. Full Root Cause Analysis and mitigating actions to reduce likelihood of reoccurrence to follow.
We're experiencing issues in service rider, due to database performance.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Engineering is currently investigating.
The incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
Issue causing Super SIM in the US to experience unstable connectivity is still under investigation. Next update expected in 2 hours.
We are waiting for news from our carrier partner, but have started to see some devices reconnecting.
We continue to see the number of connected devices increasing.
We continue to see the number of connected devices increasing, our service provider partner is continuing efforts to restore connectivity to all affected devices.
Our service provider partner has confirmed that they are restoring connectivity for the last 5% of devices on their network, we appear to have recovered nearly 100% of devices. The offline task pins have been re-enabled for our operations partners and we are not seeing a high number of bounties. We will continue to monitor and await our partner's confirmation that the issue is resolved.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.