Incidents reported on status page for Foodzilla https://status.foodzilla.io/ https://d1lppblt9t2x15.cloudfront.net/logos/5ee2f2fbcfcf731a59a4851100c21d67.png https://status.foodzilla.io/ en https://status.foodzilla.io/ Wed, 15 Jul 2026 07:57:36 +0000 https://status.foodzilla.io/#4cce510e77f988bc74542edd232ec219b0ef8140771ad52b1be6d2eeeb06c478 Foodzilla Email Service recovered https://status.foodzilla.io/ Wed, 15 Jul 2026 07:52:15 +0000 https://status.foodzilla.io/#4cce510e77f988bc74542edd232ec219b0ef8140771ad52b1be6d2eeeb06c478 Foodzilla Email Service went down https://status.foodzilla.io/incident/900313 Wed, 20 May 2026 02:31:00 -0000 https://status.foodzilla.io/incident/900313#7655f4fed55c7f2a2ec45ee1af9b31b94dbceffa0a157e271fc0acd3d5a01e21 We're currently dealing with a major outage at Railway, one of our infrastructure providers. The issue began at 22:29 UTC on May 19 and is still ongoing on their end. You can track their status directly at status.railway.com. What this means for you: roughly one third of our customers are seeing login failures, and some requests are not completing as expected. If you're affected, this is why. Our team has switched over to our backup provider so the platform stays accessible while Railway works through their incident. We're monitoring both sides closely and will keep this page updated as things change. We know reliability matters, and we'll share a full post-incident write-up once everything is fully restored, including what happened and what we're doing to reduce exposure to single-provider outages going forward. https://status.foodzilla.io/incident/877738 Thu, 23 Apr 2026 02:11:00 -0000 https://status.foodzilla.io/incident/877738#662aa5b41d2ceddd7ee1b3c3e06f7497fb3d19ce22d7018107a2f3e43fcd3804 Summary On April 21 and 22, a partial outage at one of our upstream providers prevented roughly 30% of customers from logging in or accessing the platform. The issue has been fully resolved. Impact Affected services: Platform and API Unaffected services: Website and customer support Scope: ~30% of traffic Duration: Three incidents of ~45 minutes each — two on April 21 and one on April 22 Cause An outage at one of our infrastructure providers disrupted a subset of our traffic, causing login and platform access failures for customers routed through the affected segment. Resolution & preventative measures The underlying issue was resolved on April 22. To reduce the likelihood and blast radius of similar incidents, we have: Scaled our servers to 6 replicas for greater redundancy Added improved detection to catch provider-level issues sooner Introduced fallback processes that isolate failures to a specific API, rather than impacting all customers on an affected server We apologise for the disruption and appreciate your patience.