iFood outages and problems
User reports, last 24 hours
216 reports in total, counted in 15-minute windows
In the last hour, 2 problem reports came in for iFood, against about 3 at this time on a usual day. Over the last 24 hours there were 216 reports. The last spike in reports was 13 h ago and lasted 22 min. These are user reports from Brazil, where most people report iFood problems.
- NormalClose to the usual level23 h 30 min · 97 reports
- ElevatedMore than 1.5 times the usual levelNone in this chart
- OutageMore than twice the usual level and far above the day's average30 min · 119 reports
- Usual levelWhat a usual day sees at that timeAbout 3 an hour now
In the past 24 hours, 216 user reports came in for iFood. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 97.92% uptime for the day.
The most recent spike big enough to count as an outage was 13 hours ago. The busiest 15-minute window of the day had 107 reports, about 15 hours ago.
-
Outage
Ended 13 h agoLasted 15 min12peak reports
-
Outage
Ended 15 h agoLasted 15 min107peak reports
iFood in November 2026
- Problem reports in November (since 3 November)
- 221
Monthly report for November 2026
People who report a problem with iFood to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:
- Website
- Login
- Aplicativo Celular
- Finalização de compras
- Rastreamento de pedidos
iFood problem spikes, last 30 days
Since 3 November, iFood had 2 outage spikes. The longest lasted 36 min, on 4 November.
-
Outage
Wed 4 Nov, 14:09–14:31Lasted 22 min14peak reports
-
Outage
Lasted 36 min109peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 3 November 2026. Monthly reports for all services
How to fix iFood not working
iFood is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach ifood.com.br over your own connection, right now. Nothing is sent to us or stored.
Reopen the iFood app
Close the app fully and open it again, because a stuck session can leave the menu, cart, or checkout spinning. On iPhone, swipe up from the bottom, pause, then swipe iFood up; on Android, tap Recents and swipe the app away.
Switch iFood connections
Turn Wi-Fi off and try mobile data, or do the reverse, then load the restaurant page again. On iPhone use Settings > Wi-Fi and Settings > Cellular; on Android use Settings > Network & internet > Internet.
Fix iFood location access
If restaurants do not load near your address, check the location permission. On iPhone, go to Settings > Privacy & Security > Location Services > iFood > While Using the App. On Android, go to Settings > Apps > iFood > Permissions > Location > Allow only while using the app.
Clear iFood cache or reinstall
On Android, go to Settings > Apps > iFood > Storage and cache > Clear cache, then reopen the app. On iPhone, go to Settings > General > iPhone Storage > iFood > Offload App, then tap Reinstall App. If the same screen keeps failing after that, delete the app and install it again from the App Store or Google Play.
While iFood is down: what to use instead
- Rappi Use it for restaurants, markets, and pharmacy orders in many Brazilian cities when the iFood app will not load or checkout hangs.
- aiqfome It can cover local restaurants in many smaller Brazilian cities, so check it if your usual place is listed there.
- Restaurant direct order Call or message the restaurant on WhatsApp, because many places take orders outside the app and can confirm payment and delivery options.
- iFood website If only the mobile app is failing, try the website in a browser and sign in with the same account.
Problems at the same time as iFood
Since 3 November, all 2 of iFood's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- Freenet2 times
- Klarmobil2 times
- Postbank2 times
- Sainsbury’s2 times
- NS&I (National Savings)2 times
- Banco do Brasil2 times
How many of iFood's spikes overlapped one of theirs.
During the latest spike
iFood: Wed 4 Nov, 14:09 to 14:31
- Klarmobil, outage,05:57 to 23:27
- Postbank, outage,07:12 to 21:27
- Sainsbury’s, outage,07:42 to 5 Nov 00:12
- NS&I (National Savings), outage,09:27 to 14:27
- Banco do Brasil, outage,09:42 to 18:57
- GOV.BR, outage,10:12 to 23:27
- ITV, outage,10:12 to 17:57
- USPS, outage,10:42 to 5 Nov 01:57
65 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report iFood problems
The busiest hour for reports about iFood is 11:00 to 12:00 Central European time, and the busiest day is Wednesday.
By hour of the day
- 00:00 to 01:00: 0.28 reports on an average day
- 01:00 to 02:00: 0.32 reports on an average day
- 02:00 to 03:00: 0.09 reports on an average day
- 03:00 to 04:00: 0.07 reports on an average day
- 04:00 to 05:00: 0.04 reports on an average day
- 05:00 to 06:00: 0 reports on an average day
- 06:00 to 07:00: 0.04 reports on an average day
- 07:00 to 08:00: 0 reports on an average day
- 08:00 to 09:00: 0 reports on an average day
- 09:00 to 10:00: 0 reports on an average day
- 10:00 to 11:00: 0.02 reports on an average day
- 11:00 to 12:00: 1.9 reports on an average day
- 12:00 to 13:00: 0.18 reports on an average day
- 13:00 to 14:00: 0.09 reports on an average day
- 14:00 to 15:00: 0.31 reports on an average day
- 15:00 to 16:00: 0.36 reports on an average day
- 16:00 to 17:00: 0.24 reports on an average day
- 17:00 to 18:00: 0.1 reports on an average day
- 18:00 to 19:00: 0.17 reports on an average day
- 19:00 to 20:00: 0.14 reports on an average day
- 20:00 to 21:00: 0.1 reports on an average day
- 21:00 to 22:00: 0.1 reports on an average day
- 22:00 to 23:00: 0.07 reports on an average day
- 23:00 to 00:00: 0.3 reports on an average day
By day of the week
- Monday: 0 reports on an average Monday
- Tuesday: 0 reports on an average Tuesday
- Wednesday: 31 reports on an average Wednesday
- Thursday: 4.7 reports on an average Thursday
- Friday: 0 reports on an average Friday
- Saturday: 0 reports on an average Saturday
- Sunday: 0 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 29 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when iFood goes down
iFood is a Brazilian delivery app and website for ordering meals and market items from local merchants, mostly through its Android and iPhone apps. If it goes down, customers may lose checkout or courier tracking, and restaurants can miss incoming orders.
Problems tend to show up first in the app feed or checkout, where store lists fail to load, menus appear blank, saved addresses disappear, or the cart refuses to finish an order. Payment can be the next break: cards or Pix may sit on a loading screen or return a generic failure, with the order left waiting for confirmation. Placed orders may still move, though the map can freeze and in-app help can stop opening. Outages are not always sitewide because a city issue, a payment path, merchant order systems, or courier dispatch can break while another area still works.
iFood IP address, servers and network
Checking ifood.com.br from our server…
iFood FAQ
Is iFood down right now?
Why is the iFood app not showing restaurants near my address?
Why can't I finish a payment with Pix or a card?
Why did my iFood coupon disappear at checkout?
What should I do if my order status is stuck after the restaurant accepted it?
Service updates from @ifood
No posts about problems from @ifood in the last 14 days. The latest is from .
Contact iFood support
Tip: iFood doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
How we track iFood
The status on this page comes from user-submitted problem reports for iFood, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for iFood, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. iFood doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.