Bird App Outage History

Started Oct 06, 2026, 11:49 PM UTC· resolved Oct 07, 2026, 01:54 AM UTC

1. monitoring Oct 06, 2026, 11:49 PM UTC

   A change has caused a disruption with the backend for the vehicles, this is currently recovering. Some vehicles will momentarily disconnect and reconnect.

2. resolved Oct 07, 2026, 01:54 AM UTC

   Connections have recovered.

Read the full incident report →

Started Sep 29, 2026, 02:26 AM UTC· resolved Sep 29, 2026, 02:42 AM UTC

1. identified Sep 29, 2026, 02:26 AM UTC

   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

2. monitoring Sep 29, 2026, 02:28 AM UTC

   We have reports that crash rates are going down but no confirmation yet from Firebase that a fix has been deployed

3. monitoring Sep 29, 2026, 02:30 AM UTC

   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...

4. resolved Sep 29, 2026, 02:42 AM UTC

   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.

Read the full incident report →

Started Sep 13, 2026, 07:26 AM UTC· resolved Sep 13, 2026, 10:40 AM UTC

1. identified Sep 13, 2026, 07:26 AM UTC

   We have been advised by Kore that there is an ongoing outage affecting approximately 15% of devices. Kore is actively investigating.

2. monitoring Sep 13, 2026, 09:31 AM UTC

   Connections seem to be close to back to normal, still monitoring

3. resolved Sep 13, 2026, 10:40 AM UTC

   99.9% offlines are back online, closing this issue

Read the full incident report →

Started Jul 24, 2026, 09:56 AM UTC· resolved Jul 25, 2026, 03:44 AM UTC

1. investigating Jul 24, 2026, 09:56 AM UTC

   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

2. investigating Jul 24, 2026, 10:49 AM UTC

   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

3. resolved Jul 25, 2026, 03:44 AM UTC

   This incident has been resolved

Read the full incident report →

Started Jul 15, 2026, 02:35 PM UTC· resolved Jul 15, 2026, 04:20 PM UTC

1. investigating Jul 15, 2026, 02:35 PM UTC

   We are currently investigating this issue.

2. resolved Jul 15, 2026, 04:20 PM UTC

   The issue was confirmed to be a carrier roaming problem and has been resolved since 15/07/2026 14:30 (UTC)

Read the full incident report →

Started Jul 05, 2026, 02:01 PM UTC· resolved Jul 05, 2026, 04:36 PM UTC

1. investigating Jul 05, 2026, 02:01 PM UTC

   We are currently investigating this issue.

2. investigating Jul 05, 2026, 02:20 PM UTC

   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.

3. identified Jul 05, 2026, 02:38 PM UTC

   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.

4. monitoring Jul 05, 2026, 03:28 PM UTC

   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.

5. resolved Jul 05, 2026, 04:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 04, 2026, 08:57 AM UTC· resolved Jul 04, 2026, 11:23 AM UTC

1. investigating Jul 04, 2026, 08:57 AM UTC

   We are currently investigating this issue.

2. identified Jul 04, 2026, 08:58 AM UTC

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

3. monitoring Jul 04, 2026, 10:47 AM UTC

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

4. resolved Jul 04, 2026, 11:23 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 10, 2026, 07:09 PM UTC· resolved Jun 10, 2026, 07:31 PM UTC

1. identified Jun 10, 2026, 07:09 PM UTC

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

2. monitoring Jun 10, 2026, 07:17 PM UTC

   Code deployment rollback has been completed and our systems have begun to stabilize. We will continue to monitor.

3. resolved Jun 10, 2026, 07:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 21, 2026, 03:21 PM UTC· resolved May 21, 2026, 09:33 PM UTC

1. investigating May 21, 2026, 03:21 PM UTC

   https://korewireless.service-now.com/csm?id=services_status

2. investigating May 21, 2026, 04:50 PM UTC

   What Description: Since approximately 11:27 UTC KORE systems have detected an increase in devices reattaching to the network using the Super SIM and Omni SIM US products. Devices are receiving a higher than expected rate of failures to attach. The issue is only with establishing new data sessions. Established data sessions are not impacted. Engineers are actively working to resolve the issue. We will provide another update in 1 hour or sooner if more information becomes available. UPDATE 2 2026-05-21 16:10 UTC / 12:10 EDT (UTC-4): The issue causing Super SIM connectivity issues to one of our partners has been identified. A carrier has confirmed to be experiencing an issue with IP announcements on the carrier network, causing routing issues, currently affecting approximately 35% of data traffic. Our team is actively working to restore the service with our partner. We will provide another update in 2 hours or sooner once more information becomes available. UPDATE 1 2026-05-21 15:09 UTC / 11:09 EDT (UTC-4): We are currently experiencing Super SIM connectivity issues where approximately 25% of data sessions are impacted. Our engineering team is actively working to resolve the issue. We will provide another update in 2 hours or sooner once more information becomes available. Previous update mentioned OmniSIM US as impacted but since then it has been verified by our engineers that the impact is limited to Super SIM.

3. identified May 21, 2026, 06:02 PM UTC

   UPDATE 3 2026-05-21 17:50 UTC / 13:50 EDT (UTC-4): After identifying the issue earlier, the traffic load on devices reattaching is being managed to slowly allow devices to recover without overwhelming downstream systems. KORE products reached a loss of 60% of traffic around 16:15 UTC. That has now recovered to approximately 27% missing. Our team is actively working to restore the service with our partner. We will provide another update in 2 hours or sooner once more information becomes available.

4. monitoring May 21, 2026, 07:05 PM UTC

   A fix has been implemented and we are monitoring the results, most major markets are indicating next to full recovery.

5. resolved May 21, 2026, 09:33 PM UTC

   This incident has been resolved, Kore has confirmed technical resolution and we have recovered the number of connected devices to a level prior to this outage. Any remaining offline vehicles should be attended to individually.

Read the full incident report →

Started May 06, 2026, 10:00 PM UTC· resolved May 07, 2026, 04:06 AM UTC

1. investigating May 06, 2026, 10:00 PM UTC

   We are currently investigating this issue.

2. monitoring May 06, 2026, 10:38 PM UTC

   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.

3. identified May 06, 2026, 10:51 PM UTC

   Vodafone has confirmed a global service degradation and is investigating.

4. monitoring May 07, 2026, 12:04 AM UTC

   Vodafone has implemented a change to restore service, they are continuing to monitor recovery.

5. monitoring May 07, 2026, 02:35 AM UTC

   Approximately half of affected devices have since reconnected, we are continuing to monitor. Asking local teams to reset devices that have not recovered.

6. resolved May 07, 2026, 04:06 AM UTC

   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.

Read the full incident report →

Started Apr 09, 2026, 03:57 AM UTC· resolved Apr 09, 2026, 06:01 AM UTC

1. investigating Apr 09, 2026, 03:57 AM UTC

   We are currently investigating this issue.

2. monitoring Apr 09, 2026, 04:46 AM UTC

   Devices have mostly reconnected, we have escalated to our telecom partner, keeping this outage under monitoring until fully recovered.

3. resolved Apr 09, 2026, 06:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 26, 2026, 08:08 PM UTC· resolved Mar 26, 2026, 08:59 PM UTC

1. identified Mar 26, 2026, 08:08 PM UTC

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

2. identified Mar 26, 2026, 08:12 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Mar 26, 2026, 08:43 PM UTC

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

4. resolved Mar 26, 2026, 08:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 08, 2026, 07:38 AM UTC· resolved Mar 08, 2026, 02:23 PM UTC

1. investigating Mar 08, 2026, 07:38 AM UTC

   We are currently investigating this issue.

2. resolved Mar 08, 2026, 02:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 06, 2026, 12:02 AM UTC· resolved Mar 06, 2026, 01:04 AM UTC

1. investigating Mar 06, 2026, 12:02 AM UTC

   We are currently investigating this issue.

2. investigating Mar 06, 2026, 01:04 AM UTC

   We are continuing to investigate this issue.

3. resolved Mar 06, 2026, 01:04 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 20, 2026, 06:13 PM UTC· resolved Feb 21, 2026, 12:52 AM UTC

1. investigating Feb 20, 2026, 06:13 PM UTC

   We are currently investigating this issue.

2. investigating Feb 20, 2026, 07:28 PM UTC

   We are continuing to investigate this issue.

3. investigating Feb 20, 2026, 09:03 PM UTC

   We are working with our external partners to determine root cause and a path towards resolution. We appreciate your continued patience.

4. identified Feb 20, 2026, 09:54 PM UTC

   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.

5. identified Feb 20, 2026, 11:38 PM UTC

   We have identified root cause and are implementing a fix.

6. monitoring Feb 21, 2026, 12:33 AM UTC

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

7. resolved Feb 21, 2026, 12:52 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 06, 2026, 08:02 PM UTC· resolved Feb 06, 2026, 08:12 PM UTC

1. investigating Feb 06, 2026, 08:02 PM UTC

   We are currently investigating an outage with our rider database, which is impacting ride starts and ride ends. We are actively investigating the issue.

2. monitoring Feb 06, 2026, 08:09 PM UTC

   The system appears to be recovering as expected. We will continue to monitor.

3. resolved Feb 06, 2026, 08:12 PM UTC

   The outage is confirmed to be fully resolved and all systems have returned to normal operation.

Read the full incident report →

Started Jan 15, 2026, 04:46 AM UTC· resolved Jan 15, 2026, 05:55 AM UTC

1. investigating Jan 15, 2026, 04:46 AM UTC

   We are currently investigating this issue.

2. monitoring Jan 15, 2026, 05:40 AM UTC

   We have largely recovered and are monitoring the situation, we have escalated to Vodafone support

3. resolved Jan 15, 2026, 05:55 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 06:52 PM UTC· resolved Nov 21, 2025, 05:14 PM UTC

1. investigating Nov 18, 2025, 06:52 PM UTC

   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.

2. identified Nov 19, 2025, 02:10 AM UTC

   Our carrier partner has identified the issue and is working towards resolution. There is currently no known ETA.

3. identified Nov 19, 2025, 09:52 AM UTC

   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

4. identified Nov 19, 2025, 02:07 PM UTC

   still no changes from Hologram Provider, pending update

5. identified Nov 20, 2025, 07:06 PM UTC

   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.

6. monitoring Nov 21, 2025, 02:47 PM UTC

   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

7. resolved Nov 21, 2025, 05:14 PM UTC

   no further notifications from the provider data show this outage is now closed

Read the full incident report →

Started Nov 17, 2025, 10:23 PM UTC· resolved Nov 18, 2025, 02:21 AM UTC

1. investigating Nov 17, 2025, 10:23 PM UTC

   We are currently investigating this issue.

2. investigating Nov 17, 2025, 11:21 PM UTC

   We are continuing to investigate the issue and working with our cloud services provider to identify root cause.

3. identified Nov 18, 2025, 12:08 AM UTC

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

4. monitoring Nov 18, 2025, 12:12 AM UTC

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

5. resolved Nov 18, 2025, 02:21 AM UTC

   This incident has been resolved. Full Root Cause Analysis and mitigating actions to reduce likelihood of reoccurrence to follow.

Read the full incident report →

Started Nov 11, 2025, 10:05 PM UTC· resolved Nov 11, 2025, 10:44 PM UTC

1. identified Nov 11, 2025, 10:05 PM UTC

   We're experiencing issues in service rider, due to database performance.

2. monitoring Nov 11, 2025, 10:11 PM UTC

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

3. resolved Nov 11, 2025, 10:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 05, 2025, 07:15 PM UTC· resolved Nov 05, 2025, 09:28 PM UTC

1. investigating Nov 05, 2025, 07:15 PM UTC

   We are currently investigating this issue.

2. monitoring Nov 05, 2025, 08:34 PM UTC

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

3. resolved Nov 05, 2025, 09:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 17, 2025, 08:51 AM UTC· resolved Oct 17, 2025, 09:03 AM UTC

1. investigating Oct 17, 2025, 08:51 AM UTC

   Engineering is currently investigating.

2. resolved Oct 17, 2025, 09:03 AM UTC

   The incident has been resolved.

Read the full incident report →

Started Oct 16, 2025, 04:08 PM UTC· resolved Oct 16, 2025, 04:44 PM UTC

1. identified Oct 16, 2025, 04:08 PM UTC

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

2. resolved Oct 16, 2025, 04:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 09, 2025, 04:19 PM UTC· resolved Oct 10, 2025, 06:09 AM UTC

1. investigating Oct 09, 2025, 04:19 PM UTC

   We are currently investigating this issue.

2. investigating Oct 09, 2025, 06:29 PM UTC

   Issue causing Super SIM in the US to experience unstable connectivity is still under investigation. Next update expected in 2 hours.

3. investigating Oct 09, 2025, 08:56 PM UTC

   We are waiting for news from our carrier partner, but have started to see some devices reconnecting.

4. investigating Oct 09, 2025, 10:37 PM UTC

   We continue to see the number of connected devices increasing.

5. investigating Oct 10, 2025, 12:18 AM UTC

   We continue to see the number of connected devices increasing, our service provider partner is continuing efforts to restore connectivity to all affected devices.

6. monitoring Oct 10, 2025, 02:40 AM UTC

   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.

7. resolved Oct 10, 2025, 06:09 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 21, 2025, 11:52 PM UTC· resolved Aug 22, 2025, 02:19 AM UTC

1. investigating Aug 21, 2025, 11:52 PM UTC

   We are currently investigating this issue.

2. resolved Aug 22, 2025, 02:19 AM UTC

   This incident has been resolved.

Read the full incident report →