Bird App Outage History

Started Aug 18, 2025, 06:40 AM UTC· resolved Aug 18, 2025, 11:18 AM UTC

1. investigating Aug 18, 2025, 06:40 AM UTC

   We are currently investigating this issue.

2. identified Aug 18, 2025, 08:40 AM UTC

   Kore Provider has identified the issue and vehicles are getting back online we are currently at 30% recovered

3. identified Aug 18, 2025, 09:06 AM UTC

   we are approx 60% recovered

4. monitoring Aug 18, 2025, 10:14 AM UTC

   we seem to be fully recovered

5. resolved Aug 18, 2025, 11:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 07, 2025, 06:06 PM UTC· resolved Aug 07, 2025, 06:20 PM UTC

1. investigating Aug 07, 2025, 06:06 PM UTC

   We are currently investigating this issue.

2. identified Aug 07, 2025, 06:07 PM UTC

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

3. monitoring Aug 07, 2025, 06:14 PM UTC

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

4. resolved Aug 07, 2025, 06:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 28, 2025, 03:47 PM UTC· resolved Jul 29, 2025, 12:29 AM UTC

1. investigating Jul 28, 2025, 03:47 PM UTC

   We have received notification of an outage affecting some Hologram G1 SIM cards. Hologram is investigating with it's upstream partners.

2. identified Jul 28, 2025, 03:48 PM UTC

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

3. monitoring Jul 28, 2025, 06:34 PM UTC

   Hologram has not yet confirmed resolution but we do see most devices have reconnected.

4. resolved Jul 29, 2025, 12:29 AM UTC

   This incident is resolved.

Read the full incident report →

Started Jul 02, 2025, 12:27 AM UTC· resolved Jul 02, 2025, 01:25 AM UTC

1. investigating Jul 02, 2025, 12:27 AM UTC

   We are currently investigating this issue.

2. resolved Jul 02, 2025, 01:25 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 06:51 PM UTC· resolved Jun 12, 2025, 09:38 PM UTC

1. investigating Jun 12, 2025, 06:51 PM UTC

   We are seeing an outage to our bird.co website and possibly other functions across the app.

2. monitoring Jun 12, 2025, 08:22 PM UTC

   From Google: Date Time Description 12 Jun 2025 13:16 PDT We have identified the root cause and applied appropriate mitigations. Our infrastructure has recovered in all regions except us-central1. Google Cloud products that rely on the affected infrastructure are seeing recovery in multiple locations. Our engineers are aware of the customers still experiencing issues on us-central1 and multi-region/us and are actively working on full recovery. We do not have an ETA for full recovery. We will provide an update by Thursday, 2025-06-12 16:00 PDT with current details.

3. resolved Jun 12, 2025, 09:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 10, 2025, 10:16 PM UTC· resolved Jun 10, 2025, 10:50 PM UTC

1. identified Jun 10, 2025, 10:16 PM UTC

   Bounties cannot currently be created or updated (only closed) - fix should be deployed by 4pm PT.

2. resolved Jun 10, 2025, 10:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 04, 2025, 06:51 PM UTC· resolved Jun 04, 2025, 07:20 PM UTC

1. investigating Jun 04, 2025, 06:51 PM UTC

   We are currently investigating this issue.

2. resolved Jun 04, 2025, 07:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 04, 2025, 07:46 AM UTC· resolved Jun 04, 2025, 11:10 AM UTC

1. investigating Jun 04, 2025, 07:46 AM UTC

   We are currently investigating this issue.

2. resolved Jun 04, 2025, 11:10 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 16, 2025, 08:17 PM UTC· resolved Apr 16, 2025, 09:07 PM UTC

1. identified Apr 16, 2025, 08:17 PM UTC

   We identified an issue where Android users aren't able to use newly added cards.

2. resolved Apr 16, 2025, 09:07 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 16, 2025, 08:00 PM UTC· resolved Apr 16, 2025, 11:01 PM UTC

1. identified Apr 16, 2025, 08:00 PM UTC

   Some service degradation is expected and potentially some loss of service (1.5% of devices potentially impacted). Partner is investigating.

2. monitoring Apr 16, 2025, 10:15 PM UTC

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

3. resolved Apr 16, 2025, 11:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 02, 2025, 03:31 PM UTC· resolved Apr 02, 2025, 09:43 PM UTC

1. investigating Apr 02, 2025, 03:31 PM UTC

   We are currently investigating this issue.

2. identified Apr 02, 2025, 07:55 PM UTC

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

3. resolved Apr 02, 2025, 09:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 31, 2025, 12:09 AM UTC· resolved Mar 31, 2025, 07:52 AM UTC

1. investigating Mar 31, 2025, 12:09 AM UTC

   We are currently investigating this issue.

2. investigating Mar 31, 2025, 05:26 AM UTC

   We are continuing to investigate this issue.

3. identified Mar 31, 2025, 05:27 AM UTC

   Kore Update: UPDATE 4 2025-03-31 04:11 UTC / 2025-03-31 00:11 EDT (UTC-4): Our engineering team has stabilized the impacted database involved in the attachment process. Our mobile core is continuing to report errors though to our connectivity partners who are continuing to restrict attachments until systems normalize. Our engineering team is continuing to investigate. We will provide the next update within an hour or earlier if new information becomes available.

4. monitoring Mar 31, 2025, 06:01 AM UTC

   A fix has been implemented and we are monitoring

5. resolved Mar 31, 2025, 07:52 AM UTC

   KORE: Our engineering team has observed recovery to near pre-incident levels. Online device metrics have nearly recovered to pre-incident levels as all devices are able to register again. Given this sustained improvement, we are considering this incident resolved and we will continue to monitor the situation to ensure stability.

Read the full incident report →

Started Mar 17, 2025, 09:00 PM UTC· resolved Mar 18, 2025, 09:23 AM UTC

1. investigating Mar 17, 2025, 09:00 PM UTC

   It has been confirmed there is a connectivity issue with Claro in both Guatemala and Puerto Rico. Our upstream partner is aware and working with the provider to troubleshoot further.

2. resolved Mar 18, 2025, 09:23 AM UTC

   Roaming Team has informed us that the problem lies with the Local Carrier and is affecting customers roaming under Claro operators from Argentina, Brazil, Chile, Colombia, Costa Rica, Ecuador, El Salvador, Guatemala, Honduras, Nicaragua, Paraguay, Peru, Dominican Republic, Uruguay, and Mexico. The Local Carrier confirmed that a circuit connecting much of the traffic from Claro Affiliate's signaling provider to them is faulty. A manual workaround was applied to reroute the traffic, which restored Vodafone IoT customers service at 18:20 UTC and has remained stable since.

Read the full incident report →

Started Mar 12, 2025, 04:46 PM UTC· resolved Mar 13, 2025, 11:13 AM UTC

1. investigating Mar 12, 2025, 04:46 PM UTC

   Vodafone is suffering an outage affecting multiple markets worldwide

2. investigating Mar 12, 2025, 05:30 PM UTC

   Message from Vodafone: We acknowledge that you experience issues with our service and we apologize for the inconvenience. We engaged our Network Engineering Team to further investigate the incident. We will get back to yoiu as soon as we receive a meaningful update.

3. resolved Mar 13, 2025, 11:13 AM UTC

   Dear Vodafone Enterprise IoT Customer, We would like to inform you that the following incident has now been resolved: Executive Summary Customers configured on Big IP experienced data degradation Incident Summary IoT Ops Service Support, through ongoing monitoring, identified that customers utilizing the Big IP platform were experiencing significant issues due to unresolved DNS queries. This issue was notably impacting traffic and causing substantial packet loss. In response, a bridge was established with all relevant teams for further investigation. To mitigate the immediate impact, traffic was switched from SPE7 (Milan) to SPE2 (Ratingen). However, despite this effort, packet loss continued to persist. Upon further troubleshooting, it was determined that the root cause of the problem was attributed to a F5 customer configured on MCC113. Once with the isolation of F5 traffic on MCC113, the Big IP platform stabilized. The remaining customers, except those configured on MCC113, were fully recovered at this point. To restore services for the customers on MCC113, a failover to MCC121 was performed. This led to service restoration for F5 customers configured on this MCC, in addition to those that were already working properly. Resolution Failover performed from MCC113 to MCC121 We apologise for the inconvenience.

Read the full incident report →

Started Feb 26, 2025, 06:36 PM UTC· resolved Feb 27, 2025, 05:59 PM UTC

1. investigating Feb 26, 2025, 06:36 PM UTC

   We are currently experiencing a connectivity incident affecting sims with an active G1 (89445*) profile. The issue has been identified, and our upstream partner is working with high urgency to resolve it. Impact: • SIM cards may experience sporadic data issues, including interrupted sessions and inconsistent connectivity. We are actively monitoring the situation and will provide regular updates as more information becomes available. Thank you for your patience as we work to restore full service. For any questions or further assistance, please reach out to our support team.

2. monitoring Feb 27, 2025, 07:17 AM UTC

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

3. resolved Feb 27, 2025, 05:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 11, 2025, 11:01 PM UTC· resolved Feb 12, 2025, 04:01 AM UTC

1. investigating Feb 11, 2025, 11:01 PM UTC

   We are currently investigating this issue.

2. monitoring Feb 12, 2025, 02:51 AM UTC

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

3. resolved Feb 12, 2025, 04:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 23, 2025, 03:19 PM UTC· resolved Jan 23, 2025, 06:03 PM UTC

1. investigating Jan 23, 2025, 03:19 PM UTC

   Hologram FLO outage

2. identified Jan 23, 2025, 03:39 PM UTC

   Earlier this morning, we experienced an emergency maintenance event on one of our core network packet gateways (Flo), which in turn impacted G2 (89357*) SIMs and led to issues with existing and new data sessions.

3. identified Jan 23, 2025, 03:58 PM UTC

   Hologram has opened an incident on their portal: https://status.hologram.io/incidents/ndjf2s73vbkq

4. monitoring Jan 23, 2025, 04:15 PM UTC

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

5. identified Jan 23, 2025, 04:27 PM UTC

   changing back to identified as the issue still seems to be ongoing

6. monitoring Jan 23, 2025, 05:35 PM UTC

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

7. resolved Jan 23, 2025, 06:03 PM UTC

   issue has been resolved, please flag if any issues remain

Read the full incident report →

Started Jan 16, 2025, 04:12 PM UTC· resolved Jan 17, 2025, 04:52 AM UTC

1. investigating Jan 16, 2025, 04:12 PM UTC

   Twilio is having connectivity issues -- https://korewireless.service-now.com/csm?id=service_status&service=cb4ae2ca479f0610ab11f92c016d43f1

2. monitoring Jan 16, 2025, 10:57 PM UTC

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

3. resolved Jan 17, 2025, 04:52 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 20, 2024, 08:57 PM UTC· resolved Nov 20, 2024, 10:04 PM UTC

1. investigating Nov 20, 2024, 08:57 PM UTC

   We are currently investigating this issue.

2. monitoring Nov 20, 2024, 08:57 PM UTC

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

3. investigating Nov 20, 2024, 09:31 PM UTC

   We are currently investigating this issue.

4. monitoring Nov 20, 2024, 09:37 PM UTC

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

5. resolved Nov 20, 2024, 10:04 PM UTC

   This incident has been resolved.

Read the full incident report →