The database is almost certainly fine. Until 25 August 2026 the Teacher App showed that one message for every problem it could not otherwise name, so it was rarely about a database. In every case measured on 25 August 2026 — 222 of them in a single day's log — the real cause was the same:
the app was asking the wrong EDUBase server for your school.
Each school lives on one server. The app looks yours up the first time you sign in and then remembers it. If your school has since been moved to a different server, the app keeps asking the old one, that server has never heard of your school, and every screen that needs your data fails — Diary, Mark In / Mark Out, class lists, marks.
The website keeps working throughout, because the browser looks the school up every time. That is why "the site is fine but the app is broken" is the usual shape of this.
Fix it on the phone, in under a minute
- Open the Teacher App and sign out.
- Sign in again with your institute code, username and password.
- Open the screen that was failing.
Signing in makes the app look your school up again and store the correct server. Everything works from then on, on that phone.
If several teachers at your school are affected, each of them needs to do it on their own phone — the stored server is per device.
What you will see now instead
From 25 August 2026 the message tells you what to do:
This school is not hosted on this server. Sign out and sign in again so the app picks up the right server, or contact EDUBase support.
If you still see the old "DB Connection Failure!" text, the app hit something else and EDUBase support can now read exactly what it was from the server log — send them your institute code and roughly when it happened.
When signing out does not fix it
Contact EDUBase support with your institute code and the screen that fails. Support can see immediately which server your school is on and which one your app is asking for, and can correct it centrally. Do not reinstall the app first — it makes no difference to this, and you will only have to sign in again anyway.