Incidents reported on status page for FoodBase https://status.foodbase.ng/ https://d1lppblt9t2x15.cloudfront.net/logos/66e8b9c24e43b7c9e1e31bc8cc21ecaa.png https://status.foodbase.ng/ en https://status.foodbase.ng/incident/935783 Fri, 26 Jun 2026 04:09:00 -0000 https://status.foodbase.ng/incident/935783#ac5960bd51226a9b806d29fdd380d4058e72052b8780432c9ec4f681a1a9d0fb We're rolling out support for multiple authentication methods (Email OTP, SMS OTP, PIN) for sensitive merchant actions. Currently, the bank details update and withdrawal request flows are still hardcoded to SMS OTP regardless of the method a merchant has selected. Merchants who choose Email OTP or PIN will still receive an SMS code instead. A fix to route these flows through the selected method is in progress. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 10:11:08 -0000 https://status.foodbase.ng/incident/884605#1bdbcf17a3016e16d223feb0b29e0797f038c6c71ba84abbea575b11b812cf5e Withdrawal Bank Resolution recovered. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 10:10:47 -0000 https://status.foodbase.ng/incident/884605#603b24ed7618416e5b4486df7c7f18f48976efd48a642e2977eacef92e9ede4a Withdrawal Bank Resolution went down. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 10:08:22 -0000 https://status.foodbase.ng/incident/884605#ac95fcd8b632615cb88655b44c6c2de1d22583aae8963e8fe303d4bf6f1b9f7d Withdrawal Bank Resolution recovered. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 10:06:13 -0000 https://status.foodbase.ng/incident/884605#254a5c6f83d7a3ff3f1db7953298a9c39aee48292dc9665bac1a5c1b3cbbff10 Withdrawal Bank Resolution went down. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 10:04:17 -0000 https://status.foodbase.ng/incident/884605#4c727d55ebe26320348b251824b077add532e6396b045f4448e13c1b7b4fe1d6 Withdrawal Bank Resolution recovered. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 10:04:03 -0000 https://status.foodbase.ng/incident/884605#82319036f9e8710dcd6768b2c2ccfcdd289162f10aca4c200544f1846319a203 Withdrawal Bank Resolution went down. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 10:02:17 -0000 https://status.foodbase.ng/incident/884605#9b95bea7563c71e57f766564be1e7bf66727a8b5587571ab2da3cbbabe1a4610 Withdrawal Bank Resolution and Bank Endpoint recovered. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 00:20:54 -0000 https://status.foodbase.ng/incident/884605#83d6473a56863f5d7b9ba6aae99aff0955af77cc864c036c6d3682c0c92d1b08 Withdrawal Bank Resolution went down. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 00:20:40 -0000 https://status.foodbase.ng/incident/884605#b74cc8bdc31b1dd572858bea2feb2c32fea91463c8f5b1e4c79d70910bf92485 Withdrawal Bank Resolution recovered. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 00:09:24 -0000 https://status.foodbase.ng/incident/884605#75c89f88bf0c57768b1d7a89c2484872ec06a461a6fbfeda9c9f8db12532061b Withdrawal Bank Resolution went down. https://status.foodbase.ng/incident/884605 Fri, 01 May 2026 00:08:35 -0000 https://status.foodbase.ng/incident/884605#67da2adb89a336d6c1d6b9651b3b8f639d88a7e679e0cd76ad80bad6b819f4e8 Withdrawal Bank Resolution recovered. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 21:59:51 -0000 https://status.foodbase.ng/incident/884605#7576a7cbc8455970143971fd3dafa5b8127a76ad4e9d55b4b7d57b6973b0f6ef Withdrawal Bank Resolution went down. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 21:59:00 -0000 https://status.foodbase.ng/incident/884605#b8185732fb133963f9337c9a99a2545cde50370193de5bcc58397bedd1646d8b Bank Endpoint went down. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 21:58:13 -0000 https://status.foodbase.ng/incident/884605#3442ebda4805fe9c94ba3e95cb713fb51df78c1f8ec7ff823e56a41359679331 Withdrawal Bank Resolution recovered. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 21:57:22 -0000 https://status.foodbase.ng/incident/884605#7c265f4222d0edafdf5fa98b71e26220c7d21eb1f6166be82f8882de80e4fb33 Bank Endpoint recovered. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 21:39:16 -0000 https://status.foodbase.ng/incident/884605#74a594a23830316ce8f0f8c6d3d89a02a50744323a1b796c3f1eaf5f95f28aea Withdrawal Bank Resolution went down. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 21:38:33 -0000 https://status.foodbase.ng/incident/884605#d449c7654dbde26f7f2f832f0a0283917a0b1591bcd0b12976b8042c8964ffa4 Withdrawal Bank Resolution recovered. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 21:38:12 -0000 https://status.foodbase.ng/incident/884605#ec66439522686bd2f508a9e941973e93d8e0658e94e5c1f48dbfc99530e195b2 Bank Endpoint went down. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 21:37:25 -0000 https://status.foodbase.ng/incident/884605#6c1818f3be4d6d269f85502f640ec3bea58b116a932ea7e423fa86b845a4b3f2 Bank Endpoint recovered. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 21:33:03 -0000 https://status.foodbase.ng/incident/884605#a80cbe1c829b2e9bcedb501cbeb37bab7dd26ad3bd8b857c152fcd089cc4ef52 Withdrawal Bank Resolution went down. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 21:32:32 -0000 https://status.foodbase.ng/incident/884605#f11d7250c29b0c4ce538eaf6c76fd63b1b2889fd29211cc7d4570c48c9bf33af Withdrawal Bank Resolution recovered. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 20:34:33 -0000 https://status.foodbase.ng/incident/884605#0b1439d13b15e41b6403986a236b0c9a14409d66b038cc1a12731271efe9588d Bank Endpoint went down. https://status.foodbase.ng/incident/884605 Thu, 30 Apr 2026 20:33:26 -0000 https://status.foodbase.ng/incident/884605#461d1231e927a7f44dc1c9803cab2955998caa2c46ac70fd4f218ce093875424 Withdrawal Bank Resolution went down. https://status.foodbase.ng/incident/883525 Thu, 30 Apr 2026 06:56:00 -0000 https://status.foodbase.ng/incident/883525#f4f7ca185628f96c78d8394d416f83b3b0ece721226a9145f868dc1674df4abb The issue affecting the transaction detail page within the Finance Dashboard has been fully resolved. Users can now successfully view transaction details without encountering errors after payment completion via Paystack. Our investigation identified the root cause as a frontend formatting error, which has now been fixed and deployed. We confirm that: All transactions processed during this period were successful and remain unaffected. No financial data was lost or altered. We appreciate your patience while we worked to resolve this issue. If you experience any further problems, please contact our support team. https://status.foodbase.ng/incident/883525 Wed, 29 Apr 2026 19:08:00 -0000 https://status.foodbase.ng/incident/883525#1d130218d481293736864905fc57a680582b4fbd8f718c70c8493891b6802efb We are currently investigating an issue affecting the Finance Dashboard where some users may encounter an error when accessing specific transaction details. This issue occurs after a transaction has been successfully completed via Paystack, but the transaction detail page fails to load properly, displaying a technical error message (ReferenceError: format is not defined). Please note that: All payments processed through Paystack remain successful and are not impacted. The issue is limited to the display of transaction details within the dashboard. Our engineering team is actively working to identify and resolve the root cause as quickly as possible. We appreciate your patience and will provide further updates as soon as a fix has been deployed. https://status.foodbase.ng/incident/882171 Tue, 28 Apr 2026 15:17:48 -0000 https://status.foodbase.ng/incident/882171#a314e2ac122c80dcb63e49cb087324cc8465ee19a0c3b5119a7be045016fba2e foodbase.ng and Api recovered. https://status.foodbase.ng/incident/882171 Tue, 28 Apr 2026 15:10:53 -0000 https://status.foodbase.ng/incident/882171#af40775525e1d172c0be1c23f1ab7c723c3b11c26167be3d4650f5b13782f3cb foodbase.ng and Api went down. https://status.foodbase.ng/incident/882171 Tue, 28 Apr 2026 15:07:30 -0000 https://status.foodbase.ng/incident/882171#b5ee71f389e7d7865b8c49da02a94026b01610637eaa046711a9dc74dee47fdf foodbase.ng and Api recovered. https://status.foodbase.ng/incident/882171 Tue, 28 Apr 2026 15:02:48 -0000 https://status.foodbase.ng/incident/882171#29242b91f051374d935c99c549d52e641faa2582b3861295734b85ec4eed5ab3 foodbase.ng and Api went down. https://status.foodbase.ng/incident/881597 Tue, 28 Apr 2026 14:45:00 -0000 https://status.foodbase.ng/incident/881597#3458b30647bc1c4499abe7577499acf7a901756f03bb0b213cc034b53fe30d8e The earlier issues affecting parts of Foodbase services following the recent domain migration have now been fully resolved. The disruption was traced to an internal configuration inconsistency affecting how active business data was selected across our systems, which led to mismatched records in business dashboards and financial operations. We have implemented a consistent business selection mechanism across all services, ensuring accurate data synchronization and stable performance across the platform. All affected features, including menu management, add-ons, drinks dashboard, and withdrawal processing, are now functioning normally. We will continue to monitor the system to ensure ongoing stability. https://status.foodbase.ng/incident/881597 Tue, 28 Apr 2026 06:54:00 -0000 https://status.foodbase.ng/incident/881597#79d949e9deac6d3ce71f25887190b3970068ca640e0ca18a9361ca77e055b99a We are currently experiencing issues affecting parts of Foodbase services following a recent domain migration from foodbase.vercel.app to foodbase.ng. Some business features including menu management, add-ons, drinks dashboard, and withdrawal processing may not function correctly at the moment. We have identified the issue as a configuration mismatch affecting internal API and balance validation systems. Our team is actively working on restoring full functionality.