And again today.
It happened to me last night in Goodwood, signal strength -65dBm, cell ID 40541, and also yesterday afternoon near Fisantekraal, signal strength -73dBm, cell ID 42551.It hasn't happened to me in Goodwood for a long time, but I guess that might just be due to the constant disconnects.
For the past few days mine seemed more stable (one disconnect in about 3-4 days)
Finally got a call back from Cell C today, asking if I am still experiencing the issues. She could not tell me whether something has changed or not, but only said that I should contact customer care if I do experience it again. Hope the rest of you guys are sorted too?
Same here - last 2 nights I've been able to stay connected overnight and the connection was still live in the morning![]()
But yea, if this sticks, then !!! THANK YOU CELL C !!! for whatever it was that you didn't say you did to fix the problem that you never said there was ;D
Official response from cell c:
If a user was inactive but attached for 60min the connection was dropped by the IT systems but not by the network so the user stays attached but cannot browse but maybe able to browse the free CellC.co.za site.
This issue was resolved via a fix. Please report if users are still experiencing this.
The response doesn't seem to fit the symptoms that people have described but hopefully the fix does solve the problem regardless. So if the issue still persists need to look into other alternatives.
Seems the problem is still being experienced.
http://mybroadband.co.za/vb/showthread.php/310911-Connected-but-no-throughput
Not the same problem. They cannot access www.cellc.co.za either.
Official response from cell c:
If a user was inactive but attached for 60min the connection was dropped by the IT systems but not by the network so the user stays attached but cannot browse but maybe able to browse the free CellC.co.za site.
This issue was resolved via a fix. Please report if users are still experiencing this.
The response doesn't seem to fit the symptoms that people have described but hopefully the fix does solve the problem regardless. So if the issue still persists need to look into other alternatives.
I'm still on the same session since 14th Feb 20:21. Certainly is looking like Cell C have squashed this bug as well...