Wednesday, July 19, 2006

Blogspot blocked in India??

Since sometime yesterday, I'm not able to open any Blogger blogs from Airtel Broadband. Seems like they have blocked it. Here is my analysis as of now. (I'm able to open blogger.com. That's how I'm posting this.)

#dig vinay-ys.blogspot.com

; <<>> DiG 9.3.2 <<>> xxxyyyzzz.blogspot.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 816
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 0

;; QUESTION SECTION:
;xxxyyyzzz.blogspot.com. IN A

;; ANSWER SECTION:
xxxyyyzzz.blogspot.com. 344544 IN CNAME blogspot.blogger.com.
blogspot.blogger.com. 1703 IN A 66.102.15.101

;; AUTHORITY SECTION:
blogger.com. 344614 IN NS ns4.google.com.
blogger.com. 344614 IN NS ns1.google.com.
blogger.com. 344614 IN NS ns2.google.com.
blogger.com. 344614 IN NS ns3.google.com.

;; Query time: 40 msec
;; SERVER: 125.xxx.yyy.zzz#53(125.xxx.yyy.zzz)
;; WHEN: Wed Jul 19 14:51:16 2006
;; MSG SIZE rcvd: 165

Then I do a tracert to that address.

#tracert blogspot.blogger.com

Tracing route to blogspot.blogger.com [66.102.15.101]
over a maximum of 30 hops:

1 46 ms 41 ms 43 ms dsl-KK-xxx.yyy.zzz.ccc.touchtelindia.net [xxx.yyy.zzz.ccc]
2 39 ms 38 ms 41 ms dsl-KK-234.63.101.203.airtelbroadband.in [203.101.63.234]
3 38 ms 35 ms 36 ms 59.145.6.85
4 40 ms 39 ms 41 ms 59.145.11.137
5 59.145.11.73 reports: Destination host unreachable.

Trace complete.

Where as other traces complete just fine.
#tracert google.com

Tracing route to google.com [64.233.167.99]
over a maximum of 30 hops:

1 40 ms 37 ms 36 ms dsl-KK-xxx.yyy.zzz.ccc.touchtelindia.net [xxx.yyy.zzz.ccc]
2 38 ms 39 ms 38 ms dsl-KK-238.63.101.203.airtelbroadband.in [203.101.63.238]
3 36 ms 32 ms 34 ms 59.145.6.85
4 40 ms 40 ms 44 ms 59.145.11.129
5 40 ms 41 ms 44 ms 59.145.11.69
6 284 ms 285 ms 291 ms 203.208.147.81
7 287 ms 288 ms 281 ms 203.208.149.57
8 271 ms 277 ms 272 ms 203.208.168.250
9 275 ms 264 ms 275 ms 66.249.94.17
10 300 ms 306 ms 302 ms 66.249.95.247
11 302 ms 301 ms 303 ms 66.249.95.245
12 303 ms 307 ms 307 ms 66.249.94.135
13 305 ms 313 ms 315 ms 72.14.232.74
14 306 ms 305 ms 303 ms 64.233.167.99

Trace complete.

Strange!!

Has anyone else seen this problem? on other service providers.?

Update: 21/07/2006
Seems like they have unblocked it now. It seems to be working.!!

No comments:

Post a Comment