iFood encounters technical issues, leaving thousands of users unable to access the app this Saturday, June 21, 2025, across various Brazilian cities. The glitch, starting around 11:12 AM (Brasília time), prevents the app from opening or causes it to crash, frustrating consumers during lunchtime. Reports on social media and Downdetector indicate over 2,800 complaints within an hour. The company acknowledged the bug, mainly affecting Android devices, and stated its technical team is working to resolve it. The outage triggered widespread dissatisfaction, with users seeking alternatives to place orders.
The disruption caught many by surprise, especially on a high-traffic day for delivery services. Users reported difficulties accessing the app, facing error messages or constant crashes. The issue led to a surge in Google Trends searches for terms like “iFood down” and “iFood not opening.”
- Main reported issues:
- App fails to open or closes automatically.
- Ongoing orders disappear from the app.
- Issues persist despite reinstallation or cache clearing.
The glitch coincided with peak demand, amplifying consumer and restaurant frustration. While the app malfunctioned, iFood’s website remained operational, serving as an alternative for placing orders.
Technical glitch hits Android
The iFood outage primarily affected Android device users. Reports suggest the issue emerged after a recent app update, possibly introducing a critical bug. Users tried clearing cache, uninstalling, and reinstalling the app, but the problems persisted. In an official statement, iFood confirmed the issue relates to Android-specific instability and assured that its technical team is addressing it.
The situation underscored users’ reliance on the app for daily meals, particularly in urban centers. Partner restaurants also faced disruptions, as the glitch halted new orders via the app. Some businesses directed customers to the website or alternative contact methods, like WhatsApp, to sustain sales.
Social media backlash
Frustration with iFood’s outage quickly spread across social media, with users sharing experiences and demanding solutions. Many expressed dismay at the issue occurring on a Saturday, a peak time for deliveries. Posts tagged iFood’s official account, seeking updates and a timeline for service restoration.
Some users reported unusual issues, like paid orders not appearing in the system. Others noted difficulties reaching support, as the app’s chat feature was also affected. The hashtag #iFoodDown trended, with memes and complaints gaining traction.
Workarounds during the outage
With the app down, iFood’s website became the primary alternative for users. Those who uninstalled the app and accessed the platform via web browsers placed orders successfully, per reports. However, this workaround wasn’t widely known, causing confusion among less tech-savvy customers.
- Tips to bypass the outage:
- Access iFood’s official website via mobile or desktop browser.
- Check internet connection before retrying.
- Contact restaurants directly via WhatsApp or phone.
- Consider alternative delivery apps like Rappi or Uber Eats.
The app’s reliance highlighted the need for restaurants to diversify sales channels. Businesses with independent order systems or profiles on other delivery platforms faced less disruption during the outage.
History of iFood issues
This isn’t iFood’s first technical hiccup. In 2020, a bug exposed users’ order histories and addresses, raising privacy concerns. The 30-minute glitch was swiftly fixed, with iFood assuring no unauthorized account or payment access occurred.
In 2021, an Amazon Web Services (AWS) server failure took down iFood alongside apps like Disney+ and Netflix. That incident disrupted order and payment processing, sparking thousands of complaints. These events highlight the challenges of maintaining a seamless delivery platform, especially during high-demand periods.
Impact on partner restaurants
Restaurants on iFood faced significant challenges during the outage. Many reported a sharp drop in orders, as the app is a primary sales channel for numerous businesses. Small establishments, heavily reliant on delivery, were hit hardest, with some facing financial losses.
To mitigate losses, some restaurants turned to social media and messaging apps to accept orders directly. Others encouraged customers to use iFood’s website, though the transition wasn’t seamless for all. The situation emphasized the need for businesses to have varied strategies to handle technical disruptions.
Company’s official response
iFood issued a statement acknowledging the outage and apologizing to users. The company said the issue is being treated urgently and support channels remain open. However, the lack of a clear timeline for resolution drew criticism, with users demanding more transparency.
iFood also noted that affected orders are being monitored to ensure customers aren’t harmed. Refunds and chargebacks were promised for incomplete orders. Despite the response, the delay in fixing the issue remained a sore point for users.
Demand for robust tech solutions
The iFood outage reignites discussions about the need for reliable systems in delivery platforms. With millions of users and restaurants relying on the app, any disruption has significant ripple effects. Experts stress that software updates require rigorous testing, especially for large-scale apps.
The glitch also highlights the importance of redundant tech infrastructure to handle usage spikes and minimize failures. For iFood, Brazil’s leading delivery platform, maintaining user and partner trust is critical to its operations.
Growth of Brazil’s delivery market
Brazil’s delivery sector has grown exponentially, driven by convenience and shifting consumer habits. Industry data shows the food delivery market generates billions annually, with iFood as the dominant player. This popularity, however, intensifies pressure for flawless operations, as users expect speed and reliability.
Today’s outage serves as a reminder of the challenges tech companies face in a competitive market. Rivals like Rappi and Uber Eats could gain ground if iFood fails to swiftly address technical issues and regain user confidence.
Next steps for normalization
iFood’s technical team continues to investigate the bug’s cause and restore app functionality. The company advised users to use the website for orders and contact support for assistance. While normalization is expected today, the absence of a firm deadline keeps users on edge.
Restaurants and delivery workers also await resolution, as the outage directly impacts their operations. Proactive communication via social media and other channels has helped some businesses maintain customer relations during the crisis.
