http://adsl.telkomsa.net broken?

[bekdik]

When I try and access http://adsl.telkomsa.net I get page unavailable. Is this the same for anyone else?

 

[Swazi]

I get to the page ok

 

[bekdik]

Thanks Swazi.


FYI - It's blocked unless you explicitly use Telkom's proxy - dsl-cache.saix.net:8080

 

[rpm]

Unavailable to me as well.

 

[VQuest]

Connection to server adsl.telkomsa.net failed (The server is not responding.)

 

[bekdik]

Adding proxy got me to login page - I can't progress further.

 

[mikkelz_za]

Since when do you have to use that proxy to view that site?

 

[bekdik]

Only the toes knows

All I can say is that without it I don't get the logon page.

 

[rburley]

nope not workin

 

[Clipse]

userstats.adsl.saix.net is the new radius login for your accounts, go there.

 

[mikkelz_za]

0 Bytes after two and a half days - that Saix user statistics website has never displayed my TelkomInternet usage.

 

[VQuest]

Same here Manson - I've never been able to get my stats from the Saix website.

 

[Clipse]

userstats.adsl.saix.net works for me LOL

 

[bekdik]

The page shows no data!

Do you belong to s SAIX VISP? You can log onto this site with any valid ADSL Username, but stats will only be displayed for SAIX hosted users. If you belong to an external ISP, e.g. Telkom Internet or MWEB, you will have to use the tools provided by your ISP.

 

[dabean]

userstats.adsl.saix.net has always displayed zero usage for telkomsa accounts.

http://adsl.telkomsa.net is working again by the way.

 

[mikkelz_za]

userstats.adsl.saix.net is the new radius login for your accounts, go there.

For which accounts?

 

[Turtle]

http://adsl.telkomsa.net is working again by the way.

I can log in, but it's not tracking my usage! It says I've uploaded/downloaded zero MB on both 1 and 2 July - the graph is there, it's just flat. Anyone else have this?

 

[bekdik]

I got something on 1st, but 0 after that.

 

[Turtle]

Does this mean I can go nuts downloading, without getting capped!?

edit OK, I e-mailed their support, and they escalated the query to the tech guys, and now it has been fixed.