Why do Telkom-Internet block certain sites ?

Moto Guzzi

Moto Guzzi

Expert Member
Joined
Apr 24, 2004
Messages
2,562
Reaction score
660
Location
South Africa.
A site like www.robgalbraith.com is no longer reacheble, sure it worked last month.

tracert www.robgalbraith.com

Tracing route to www.robgalbraith.com [209.200.83.171]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms MyDslModem.local.lan []
2 40 ms 53 ms 49 ms dsl-241-160-01.telkomadsl.co.za []
3 * * * Request timed out.
4 * * * Request timed out.
5 * 63 ms 73 ms 196.43.33.2
6 67 ms 72 ms 76 ms 196.43.33.5
7 366 ms 371 ms 370 ms ash-ip-dir-equinix-pos-6-1.telkom-ipnet.co.za [196.43.9.146]
8 * * * Request timed out.
9 416 ms 425 ms * sbc-1.ar2.DCA3.gblx.net [64.208.110.30]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 391 ms * * 216.197.122.66
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * 389 ms 209.200.83.171

Trace complete.
 
Last edited:
It works for me ;)

Try this proxy: cache.saix.net port: 8080
 
Tracing route to www.robgalbraith.com [209.200.83.171]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.254
2 43 ms 43 ms 43 ms dsl-234-0-01.telkomadsl.co.za
3 * * * Request timed out.
4 * * * Request timed out.
5 * 46 ms 45 ms 196.43.33.2
6 45 ms 45 ms 44 ms 196.43.33.5
7 388 ms 386 ms 388 ms ash-ip-dir-equinix-pos-6-1.telkom-ipnet.co.za [1
96.43.9.146]
8 * 395 ms 395 ms so-3-0-1.ar1.DCA3.gblx.net [208.49.224.161]
9 396 ms 396 ms 397 ms sbc-1.ar2.DCA3.gblx.net [64.208.110.30]
10 348 ms 347 ms 349 ms dcx-core-01.inet.qwest.net [205.171.251.57]
11 * * * Request timed out.
12 * 374 ms 374 ms scd-edge-01.inet.qwest.net [205.171.12.46]
13 376 ms 374 ms 388 ms 63.148.218.166
14 374 ms 374 ms 378 ms cr-edge1-ge-2-0.crystaltech.com [216.119.107.21]

15 379 ms 377 ms 382 ms 216.197.122.66
16 375 ms 377 ms 377 ms 209.200.83.171

Trace complete.
 
It's most likely the site blocking you - or rather, the IP range for whatever odd reason they could possibly think of.

I know of some sites that block proxy servers... I mean, come on. :p
 
Or the data is stripped so it does not flow successfully, by which ever recent software used on servers..
 
can ping and tracert, but actuall access is another matter via a browser. Is this not related to the international issues?
 
Maybe this is the answer, but to get it fixed ?

The Domain Name Server (DNS) does not have a listing for the website's domain.

The site pings no problem.
How can Telkom fix this please ? Some other sites not reacheble either.

It worked perfectly about a month ago.

Like www.dnsstuff.com
 
Last edited:
www.robgalbraith.com works fine here.

Do you know that if you connect to a site it hops through different servers. NOW that servers could be blocking ICMP (witch ping reply). That is why you see all those ping timeouts.

Im using 2 ISP's with 3 accounts:

Server1:
traceroute to www.robgalbraith.com (209.200.83.171), 64 hops max, 40 byte packets
1 dsl-245-0-01.telkomadsl.co.za (41.245.0.1) 649.611 ms 223.713 ms 218.698 ms
2 * * *
3 * * *
4 196.43.33.2 (196.43.33.2) 756.299 ms 681.244 ms 544.421 ms
5 196.43.33.5 (196.43.33.5) 651.361 ms 721.403 ms 435.701 ms
6 196.43.18.66 (196.43.18.66) 921.179 ms 922.268 ms 1161.604 ms
7 so-3-0-1.ar1.DCA3.gblx.net (208.49.224.161) 1064.178 ms 924.435 ms 1183.605 ms
8 sbc-1.ar2.DCA3.gblx.net (64.208.110.30) 777.030 ms 1140.366 ms 995.505 ms
9 dcx-core-02.inet.qwest.net (205.171.251.61) 975.761 ms 980.254 ms 777.346 ms
10 * * *
11 scd-edge-01.inet.qwest.net (205.171.12.46) 381.835 ms 999.098 ms 377.632 ms
12 63.148.218.166 (63.148.218.166) 377.407 ms * 1224.665 ms
13 * cr-edge1-ge-2-0.crystaltech.com (216.119.107.21) 824.042 ms 894.502 ms
14 216.197.122.66 (216.197.122.66) 976.052 ms 491.492 ms 379.680 ms
15 209.200.83.171 (209.200.83.171) 975.087 ms 1107.429 ms 597.644 ms

Server2:
traceroute to www.robgalbraith.com (209.200.83.171), 64 hops max, 40 byte packet s
1 * * *
2 dsl-245-0-01.telkomadsl.co.za (41.245.0.1) 544.957 ms * 387.582 ms
3 196.38.73.169 (196.38.73.169) 20.784 ms * *
4 * * *
5 196.43.33.2 (196.43.33.2) 295.220 ms 450.856 ms 443.915 ms
6 cdsl2-rba.isdsl.net (196.36.80.162) 851.373 ms
196.43.33.5 (196.43.33.5) 214.077 ms 379.125 ms
7 196.36.80.165 (196.36.80.165) 352.100 ms
196.43.18.66 (196.43.18.66) 776.293 ms 1072.959 ms
8 so-3-0-1.ar1.DCA3.gblx.net (208.49.224.161) 781.794 ms * 677.242 ms
9 sbc-1.ar2.DCA3.gblx.net (64.208.110.30) 1139.052 ms * 989.229 ms
10 POS1-1.IG4.NYC4.ALTER.NET (208.192.177.201) 1297.447 ms
dcx-core-02.inet.qwest.net (205.171.251.61) 690.995 ms 485.665 ms
11 * * *
12 0.ge-6-0-0.BR3.NYC4.ALTER.NET (152.63.18.5) 733.055 ms
scd-edge-01.inet.qwest.net (205.171.12.46) 381.417 ms *
13 63.148.218.166 (63.148.218.166) 909.693 ms 562.461 ms *
14 ewr-core-02.inet.qwest.net (205.171.17.33) 1355.842 ms 938.318 ms
cr-edge1-ge-2-0.crystaltech.com (216.119.107.21) 513.235 ms
15 * 216.197.122.66 (216.197.122.66) 914.246 ms *
16 209.200.83.171 (209.200.83.171) 746.981 ms * 632.564 ms
 
Yes, I know th latency is high. I'm uploading.

And that doubles in the routes is because of load balancing with "keep state"
 
Opens fine my side when using proxy cache.saix.net:8080

Tracing route to www.robgalbraith.com [209.200.83.171]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 10 ms dsl-240-64-01.telkomadsl.co.za [41.240.64.1]
3 17 ms 9 ms 9 ms 196.43.35.57
4 16 ms 9 ms 10 ms 196.43.35.57
5 31 ms 38 ms 30 ms 196.43.33.2
6 37 ms 30 ms 28 ms 196.43.33.5
7 412 ms 409 ms 409 ms ash-ip-dir-equinix-pos-5-5.telkom-ipnet.co.za [196.43.18.54]
8 384 ms 378 ms 379 ms so-3-0-1.ar1.DCA3.gblx.net [208.49.224.161]
9 411 ms 408 ms 409 ms sbc-1.ar2.DCA3.gblx.net [64.208.110.30]
10 397 ms 384 ms 428 ms dcx-core-01.inet.qwest.net [205.171.251.57]
11 * * * Request timed out.
12 379 ms 383 ms 383 ms scd-edge-01.inet.qwest.net [205.171.12.42]
13 388 ms 376 ms 375 ms 63.148.218.166
14 380 ms 386 ms 380 ms cr-edge1-ge-2-0.crystaltech.com [216.119.107.21]

15 396 ms 376 ms 386 ms 216.197.122.66
16 381 ms 377 ms 378 ms 209.200.83.171

Trace complete.
 
It isn't Telkom. More often than not, this type of thing is due to a website refusing your IP, or taking issue with your apparent IP changing all the time.

Try using a proxy to browse. cache.saix.co.za:8080 works nicely, or 196.25.253.13:8080.
 
Why should I use a proxcy, never did before and it always worked. I put my cock on a block it's Telkom.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X