international browsing down?

[Vlad]

can't access most international sites, although some, like google and cnn do work

 

[nic777]

Same problem here, but I'm on iBurst in Cape Town.

 

[Vlad]

hmm, so far once it might not be sentech's fault.
i still can't access certain sites, i wonder how long it is going to take before anyone notices that something is not right

seems like a DNS problem because it's only browsing that is affected

 

[alloytoo]

hmm, so far once it might not be sentech's fault.
i still can't access certain sites, i wonder how long it is going to take before anyone notices that something is not right

seems like a DNS problem because it's only browsing that is affected

I'm sure it's a DNS problem, if I use my Dial-up-connection I can access those sites. (in mycase Livejournal)

 

[andreasrothe]

I'm sure it's a DNS problem, if I use my Dial-up-connection I can access those sites. (in mycase Livejournal)

I also am quite sure its a DNS problem. Does anybody know how - if at all - one can get our connections to point to different DNS servers. I have been given a whole list of ones I could use, plus there are many to be found on www.saix.net/cgi-bin/saix_dns.pl
If only we could figure out how to use alternatives, we would be up and running.

 

[vmachine]

trace route

It seems to be an international problem. The trace just dies after 195.66.224.51 ( linx1.teleglobe.net - bogus rDNS)

 

[alloytoo]

It seems to be resolved this morning.

Just one thing though.

When I phoned Sucktech yesterday to book a ticket I explained the problem, telling him that some International sites were inaccessable. So the lad says he's going to escalate the problem.

Then he wants to know signal strength etc....Hello.....I'm connected..........ARRRRGGGGGGGGGHHHHH where's that Iburst number

 

[Claymore]

I'm sure it's a DNS problem, if I use my Dial-up-connection I can access those sites. (in mycase Livejournal)

I have the same issue with Livejournal on ADSL... *sigh*

 

[keithr]

Not on ADSL!

 

[cryptic1]

Int. is down again this morning & according to Nowire Call Centre, Sentech is busy attending to the prolem.

 

[StillOnSent]

This is getting very annoying

Common Telkom, connect my ADSL so Ican get out of this hellhole for good

 

[bdt]

I've been having "fun" all.bloody.night(&morning) with straight up time-outs and DNS failures - fixable by heavy (ab)use of F5/the browser refresh button ..eventually, after several re-re-retries I typically get to what I'm after.

 

[asilva]

problem continues

Yes, international is down, again, it is intermitent though, ping google with -t option and let it run, you will see. The following sample repeats itself over and over.

Reply from 64.233.183.99: bytes=32 time=502ms TTL=240
Reply from 64.233.183.99: bytes=32 time=501ms TTL=240
Reply from 64.233.183.99: bytes=32 time=480ms TTL=240
Reply from 64.233.183.99: bytes=32 time=519ms TTL=240
Reply from 64.233.183.99: bytes=32 time=499ms TTL=240
Reply from 64.233.183.99: bytes=32 time=498ms TTL=240
Reply from 64.233.183.99: bytes=32 time=476ms TTL=240
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.183.99: bytes=32 time=468ms TTL=240
Reply from 64.233.183.99: bytes=32 time=488ms TTL=240
Reply from 64.233.183.99: bytes=32 time=505ms TTL=240
Reply from 64.233.183.99: bytes=32 time=504ms TTL=240
Reply from 64.233.183.99: bytes=32 time=502ms TTL=240
Reply from 64.233.183.99: bytes=32 time=458ms TTL=240
Reply from 64.233.183.99: bytes=32 time=457ms TTL=240

 

[cryptic1]

This is really frustrating, what the hell could be wrong that takes this f@&#g long to fix . I wonder.... maybe they are trying to figure out the instruction manual.

 

[StillOnSent]

. I wonder.... maybe they are trying to figure out the instruction manual.

Maybe they are trying to download it, but it keeps timing out

 

[cryptic1]

Maybe they are trying to download it, but it keeps timing out

LOL

 

[cryptic1]

Well it's back on for now

 

[StillOnSent]

still off here

 

[ejbengine]

I'm getting timeouts on google.com and gmail.com

 

[Vlad]

it comes and goes every few minutes...

aren't you glad these are the people that are going to make sure that the next worldcup is going to be beamed around the world.