After we received the first report about connection problems yesterday at 1:35 PM, we started looking into what could be causing it.
One single report usually doesn’t mean a hardware failure on our side, because that would normally affect entire buildings.
During the night, two more people contacted us, so we were able to do more testing this morning.
From one of them, we couldn’t get any useful info because their hardware is very old, and the third person didn’t reply anymore.
At around 3:00 PM today, something seems to have happened that made the issue worse. Luckily, more people have reached out since then, so we now believe there really is a problem in Hohenheim.
While I’m writing this, we’re running different tests, and we’re getting ready to drive from Tübingen to replace the device if needed.
If your Wi-Fi issues are caused by your own old hardware, you’re welcome to live with it.
Everyone else shouldn’t have any problems – please always contact us right away if you do, so we can fix it.
Around 5:30 PM, replaced an old fiber module in Egilolfstraße just to be sure.
Did some more tests, but no results.
Probably witnessed an outage, but not sure.
Installed hardware for diagnostics.
Will run tests overnight and check again tomorrow.
Update Saturday 6 pm:
The diagnosis took the whole day.
We can confirm the outages on all 13 connections that were reported.
All our devices say they are working fine. The older part we replaced yesterday was probably not the cause, because the problem is still there.
That’s frustrating.
We are getting ready to go on site in Hohenheim tomorrow morning. We will either try to find the problem by checking everything again or replace all the equipment in building 49/51 and the connection to building 53.
Update Sunday 8:30 am: Planned arrival in Hohenheim at 10:30 am.
Update from the car on the way to Tübingen (Sunday 5:00 PM):
We replaced all possible hardware.
Egilolfstraße 49 and 51 now have gigabit internet.
Feel free to try our speed test: https://netz-ak.de/intern-speedtest/
We hope this fixed the problem – even though we couldn’t find the exact cause.