<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: New Datacenter Live: Singapore</title>
	<atom:link href="http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/</link>
	<description>Making the Internet safer and faster</description>
	<lastBuildDate>Tue, 15 May 2012 00:05:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Jason Tan</title>
		<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-542195</link>
		<dc:creator>Jason Tan</dc:creator>
		<pubDate>Sun, 24 Apr 2011 04:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-542195</guid>
		<description>My ISP is starhub. Why is the traffic routed to usa before coming to the sg opendns server?

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:

  1    </description>
		<content:encoded><![CDATA[<p>My ISP is starhub. Why is the traffic routed to usa before coming to the sg opendns server?</p>
<p>Tracing route to resolver1.opendns.com [208.67.222.222]<br />
over a maximum of 30 hops:</p>
<p>  1    </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rioven</title>
		<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-537359</link>
		<dc:creator>rioven</dc:creator>
		<pubDate>Wed, 20 Apr 2011 18:39:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-537359</guid>
		<description>My result from Malaysia (TM Streamyx)

Tracing route to resolver1.opendns.com [208.67.222.222] with TTL of 32:

 1  0ms    0ms    0ms    192.168.2.1
 2   *     7ms    7ms    219.93.218.177
 3  92ms   107ms  7ms    219.93.219.29
 4  50ms   48ms   49ms   10.55.208.52
 5  212ms  215ms  293ms  203.131.245.157
 6  207ms  270ms  249ms  xe-1-2-0.r20.newthk02.hk.bb.gin.ntt.net [129.250.3.206]

 7  253ms  257ms  255ms  p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.250.6.97]

 8  94ms   78ms   95ms   116.51.17.210
 9  137ms  74ms   72ms   resolver1.opendns.com [208.67.222.222]

Traceroute complete.</description>
		<content:encoded><![CDATA[<p>My result from Malaysia (TM Streamyx)</p>
<p>Tracing route to resolver1.opendns.com [208.67.222.222] with TTL of 32:</p>
<p> 1  0ms    0ms    0ms    192.168.2.1<br />
 2   *     7ms    7ms    219.93.218.177<br />
 3  92ms   107ms  7ms    219.93.219.29<br />
 4  50ms   48ms   49ms   10.55.208.52<br />
 5  212ms  215ms  293ms  203.131.245.157<br />
 6  207ms  270ms  249ms  xe-1-2-0.r20.newthk02.hk.bb.gin.ntt.net [129.250.3.206]</p>
<p> 7  253ms  257ms  255ms  p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.250.6.97]</p>
<p> 8  94ms   78ms   95ms   116.51.17.210<br />
 9  137ms  74ms   72ms   resolver1.opendns.com [208.67.222.222]</p>
<p>Traceroute complete.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-525367</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 13 Apr 2011 02:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-525367</guid>
		<description>Tracert is still going to San Jose:

traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets
 1  192.168.0.254 (192.168.0.254)  0.557 ms  0.743 ms  0.816 ms
 2  * * *
 3  242.246.65.202.unknown.m1.com.sg (202.65.246.242)  38.280 ms  38.219 ms  38.206 ms
 4  241.246.65.202.unknown.m1.com.sg (202.65.246.241)  7.535 ms  7.527 ms  7.366 ms
 5  Gi2-1.gw2.sin1.asianetcom.net (203.192.154.17)  8.421 ms  8.363 ms  9.112 ms
 6  gi10-0.gw5.sin1.asianetcom.net (202.147.48.86)  9.177 ms  7.282 ms  8.353 ms
 7  te0-0-2-0.wr2.sin0.asianetcom.net (61.14.157.113)  9.415 ms  9.448 ms  9.392 ms
 8  te0-0-2-0.wr2.osa0.asianetcom.net (61.14.157.62)  183.927 ms  183.882 ms  183.798 ms
 9  te0-0-4-0.wr1.osa0.asianetcom.net (61.14.157.21)  183.394 ms  184.506 ms  184.442 ms
10  61-14-157-98.asianetcom.net (61.14.157.98)  188.250 ms  188.203 ms  184.489 ms
11  xe-7-3-0.edge2.SanJose3.Level3.net (4.53.210.29)  188.231 ms  189.061 ms  189.752 ms
12  ae-31-90.car1.SanJose2.Level3.net (4.69.152.203)  186.415 ms ae-41-80.car1.SanJose2.Level3.net (4.69.152.139)  187.416 ms ae-11-70.car1.SanJose2.Level3.net (4.69.152.75)  192.915 ms
13  SPLICE-COMM.car1.SanJose2.Level3.net (4.59.0.174)  193.056 ms  192.868 ms  193.261 ms

PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.
64 bytes from 208.67.222.222: icmp_seq=1 ttl=50 time=186 ms
64 bytes from 208.67.222.222: icmp_seq=2 ttl=50 time=186 ms
64 bytes from 208.67.222.222: icmp_seq=3 ttl=50 time=186 ms
64 bytes from 208.67.222.222: icmp_seq=4 ttl=50 time=186 ms
64 bytes from 208.67.222.222: icmp_seq=5 ttl=50 time=186 ms</description>
		<content:encoded><![CDATA[<p>Tracert is still going to San Jose:</p>
<p>traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets<br />
 1  192.168.0.254 (192.168.0.254)  0.557 ms  0.743 ms  0.816 ms<br />
 2  * * *<br />
 3  242.246.65.202.unknown.m1.com.sg (202.65.246.242)  38.280 ms  38.219 ms  38.206 ms<br />
 4  241.246.65.202.unknown.m1.com.sg (202.65.246.241)  7.535 ms  7.527 ms  7.366 ms<br />
 5  Gi2-1.gw2.sin1.asianetcom.net (203.192.154.17)  8.421 ms  8.363 ms  9.112 ms<br />
 6  gi10-0.gw5.sin1.asianetcom.net (202.147.48.86)  9.177 ms  7.282 ms  8.353 ms<br />
 7  te0-0-2-0.wr2.sin0.asianetcom.net (61.14.157.113)  9.415 ms  9.448 ms  9.392 ms<br />
 8  te0-0-2-0.wr2.osa0.asianetcom.net (61.14.157.62)  183.927 ms  183.882 ms  183.798 ms<br />
 9  te0-0-4-0.wr1.osa0.asianetcom.net (61.14.157.21)  183.394 ms  184.506 ms  184.442 ms<br />
10  61-14-157-98.asianetcom.net (61.14.157.98)  188.250 ms  188.203 ms  184.489 ms<br />
11  xe-7-3-0.edge2.SanJose3.Level3.net (4.53.210.29)  188.231 ms  189.061 ms  189.752 ms<br />
12  ae-31-90.car1.SanJose2.Level3.net (4.69.152.203)  186.415 ms ae-41-80.car1.SanJose2.Level3.net (4.69.152.139)  187.416 ms ae-11-70.car1.SanJose2.Level3.net (4.69.152.75)  192.915 ms<br />
13  SPLICE-COMM.car1.SanJose2.Level3.net (4.59.0.174)  193.056 ms  192.868 ms  193.261 ms</p>
<p>PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.<br />
64 bytes from 208.67.222.222: icmp_seq=1 ttl=50 time=186 ms<br />
64 bytes from 208.67.222.222: icmp_seq=2 ttl=50 time=186 ms<br />
64 bytes from 208.67.222.222: icmp_seq=3 ttl=50 time=186 ms<br />
64 bytes from 208.67.222.222: icmp_seq=4 ttl=50 time=186 ms<br />
64 bytes from 208.67.222.222: icmp_seq=5 ttl=50 time=186 ms</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Koole</title>
		<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-484193</link>
		<dc:creator>Koole</dc:creator>
		<pubDate>Sat, 12 Mar 2011 23:44:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-484193</guid>
		<description>and this the result from FirstMedia Indonesia;

traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  1.562 ms  1.019 ms  0.744 ms
 2  10.9.0.1 (10.9.0.1)  13.259 ms  9.378 ms  10.492 ms
 3  192.168.190.229 (192.168.190.229)  10.382 ms  9.582 ms  11.521 ms
 4  192.168.190.145 (192.168.190.145)  39.608 ms  33.866 ms  8.089 ms
 5  fm-ip-202.73.96.6.fast.net.id (202.73.96.6)  8.201 ms  8.455 ms  7.746 ms
 6  fm-ip-202.73.96.5.fast.net.id (202.73.96.5)  8.153 ms  10.122 ms  7.811 ms
 7  fm-ip-202.73.96.9.fast.net.id (202.73.96.9)  19.482 ms  14.124 ms  8.936 ms
 8  ip-125-33.mcs.napinfo.net (119.110.125.33)  23.618 ms  18.491 ms  9.931 ms
 9  ip-112-226.mcs.napinfo.net (119.110.112.226)  19.754 ms  19.890 ms  22.181 ms
10  vlan558.icore1.svw-singapore.as6453.net (116.0.71.113)  35.916 ms  37.741 ms  34.259 ms
11  if-0-1712.tcore2.svw-singapore.as6453.net (180.87.15.21)  23.476 ms  22.413 ms  22.214 ms
12  if-11-2.tcore1.lvw-losangeles.as6453.net (180.87.15.150)  193.968 ms  192.456 ms  192.516 ms
13  if-10-0-0-12.mcore3.laa-losangeles.as6453.net (66.110.59.54)  191.393 ms  206.862 ms  194.674 ms
14  0.so-1-0-0.br2.lax7.alter.net (204.255.169.89)  192.746 ms  203.536 ms  191.822 ms
15  0.so-2-2-0.xt1.lax7.alter.net (152.63.112.146)  194.341 ms  193.186 ms  196.045 ms
16  0.so-7-1-0.xl3.lax15.alter.net (152.63.1.226)  201.757 ms  200.652 ms  202.657 ms
17  tengige0-4-2-0.gw4.lax15.alter.net (152.63.115.186)  199.944 ms
    tengige0-4-1-0.gw4.lax15.alter.net (152.63.115.178)  200.803 ms  200.255 ms
18  65.204.147.2 (65.204.147.2)  206.096 ms  200.076 ms  200.474 ms
19  * * *
20  * * *
21  * * *
22  * * *</description>
		<content:encoded><![CDATA[<p>and this the result from FirstMedia Indonesia;</p>
<p>traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 52 byte packets<br />
 1  192.168.1.1 (192.168.1.1)  1.562 ms  1.019 ms  0.744 ms<br />
 2  10.9.0.1 (10.9.0.1)  13.259 ms  9.378 ms  10.492 ms<br />
 3  192.168.190.229 (192.168.190.229)  10.382 ms  9.582 ms  11.521 ms<br />
 4  192.168.190.145 (192.168.190.145)  39.608 ms  33.866 ms  8.089 ms<br />
 5  fm-ip-202.73.96.6.fast.net.id (202.73.96.6)  8.201 ms  8.455 ms  7.746 ms<br />
 6  fm-ip-202.73.96.5.fast.net.id (202.73.96.5)  8.153 ms  10.122 ms  7.811 ms<br />
 7  fm-ip-202.73.96.9.fast.net.id (202.73.96.9)  19.482 ms  14.124 ms  8.936 ms<br />
 8  ip-125-33.mcs.napinfo.net (119.110.125.33)  23.618 ms  18.491 ms  9.931 ms<br />
 9  ip-112-226.mcs.napinfo.net (119.110.112.226)  19.754 ms  19.890 ms  22.181 ms<br />
10  vlan558.icore1.svw-singapore.as6453.net (116.0.71.113)  35.916 ms  37.741 ms  34.259 ms<br />
11  if-0-1712.tcore2.svw-singapore.as6453.net (180.87.15.21)  23.476 ms  22.413 ms  22.214 ms<br />
12  if-11-2.tcore1.lvw-losangeles.as6453.net (180.87.15.150)  193.968 ms  192.456 ms  192.516 ms<br />
13  if-10-0-0-12.mcore3.laa-losangeles.as6453.net (66.110.59.54)  191.393 ms  206.862 ms  194.674 ms<br />
14  0.so-1-0-0.br2.lax7.alter.net (204.255.169.89)  192.746 ms  203.536 ms  191.822 ms<br />
15  0.so-2-2-0.xt1.lax7.alter.net (152.63.112.146)  194.341 ms  193.186 ms  196.045 ms<br />
16  0.so-7-1-0.xl3.lax15.alter.net (152.63.1.226)  201.757 ms  200.652 ms  202.657 ms<br />
17  tengige0-4-2-0.gw4.lax15.alter.net (152.63.115.186)  199.944 ms<br />
    tengige0-4-1-0.gw4.lax15.alter.net (152.63.115.178)  200.803 ms  200.255 ms<br />
18  65.204.147.2 (65.204.147.2)  206.096 ms  200.076 ms  200.474 ms<br />
19  * * *<br />
20  * * *<br />
21  * * *<br />
22  * * *</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-448480</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Sat, 29 Jan 2011 11:17:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-448480</guid>
		<description>- Going to SanJose, from Sydney Australia
$ traceroute -U 208.67.222.222
traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets
 1  xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx)  0.314 ms  0.332 ms  0.356 ms
 2  10.236.48.1 (10.236.48.1)  17.774 ms  19.553 ms  19.734 ms
 3  vl400.kacz-s-1.ken.bigpond.net.au (58.160.12.1)  19.867 ms  20.004 ms  20.440 ms
 4  te6-2.agg2.ken.bigpond.net.au (58.160.15.246)  20.127 ms  20.298 ms  20.855 ms
 5  172.18.239.38 (172.18.239.38)  20.241 ms  20.523 ms  20.660 ms
 6  172.18.239.33 (172.18.239.33)  20.851 ms  8.802 ms  7.978 ms
 7  Bundle-Ether11.chw48.Sydney.telstra.net (203.45.17.21)  11.513 ms  18.428 ms  18.561 ms
 8  Bundle-Ether6.chw-core2.Sydney.telstra.net (203.50.6.153)  19.142 ms  19.278 ms  19.298 ms
 9  Bundle-Ether1.oxf-gw2.Sydney.telstra.net (203.50.6.90)  24.057 ms  23.906 ms  24.285 ms
10  TenGigabitEthernet6-0.sydo-core01.Sydney.reach.com (203.50.13.38)  17.770 ms  17.991 ms  18.105 ms
11  i-10-0-0.syd-core03.bi.reach.com (202.84.221.85)  18.542 ms  18.676 ms  18.783 ms
12  i-12-2-0.sjc-core01.bx.reach.com (202.84.140.157)  175.759 ms  176.076 ms  172.576 ms
13  i-2-1.eqnx02.bi.reach.com (202.84.251.122)  178.338 ms  177.970 ms  178.181 ms
14  l3-peer.eqnx02.pr.reach.com (134.159.62.198)  207.217 ms  207.158 ms  207.160 ms
15  ae-21-69.car1.SanJose2.Level3.net (4.68.18.11)  186.873 ms ae-31-99.car1.SanJose2.Level3.net (4.68.18.203)  183.430 ms ae-11-79.car1.SanJose2.Level3.net (4.68.18.75)  183.740 ms
16  SPLICE-COMM.car1.SanJose2.Level3.net (4.59.0.174)  372.320 ms  369.668 ms  368.502 ms
17  resolver1.opendns.com (208.67.222.222)  179.333 ms  202.413 ms  198.676 ms</description>
		<content:encoded><![CDATA[<p>- Going to SanJose, from Sydney Australia<br />
$ traceroute -U 208.67.222.222<br />
traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets<br />
 1  xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx)  0.314 ms  0.332 ms  0.356 ms<br />
 2  10.236.48.1 (10.236.48.1)  17.774 ms  19.553 ms  19.734 ms<br />
 3  vl400.kacz-s-1.ken.bigpond.net.au (58.160.12.1)  19.867 ms  20.004 ms  20.440 ms<br />
 4  te6-2.agg2.ken.bigpond.net.au (58.160.15.246)  20.127 ms  20.298 ms  20.855 ms<br />
 5  172.18.239.38 (172.18.239.38)  20.241 ms  20.523 ms  20.660 ms<br />
 6  172.18.239.33 (172.18.239.33)  20.851 ms  8.802 ms  7.978 ms<br />
 7  Bundle-Ether11.chw48.Sydney.telstra.net (203.45.17.21)  11.513 ms  18.428 ms  18.561 ms<br />
 8  Bundle-Ether6.chw-core2.Sydney.telstra.net (203.50.6.153)  19.142 ms  19.278 ms  19.298 ms<br />
 9  Bundle-Ether1.oxf-gw2.Sydney.telstra.net (203.50.6.90)  24.057 ms  23.906 ms  24.285 ms<br />
10  TenGigabitEthernet6-0.sydo-core01.Sydney.reach.com (203.50.13.38)  17.770 ms  17.991 ms  18.105 ms<br />
11  i-10-0-0.syd-core03.bi.reach.com (202.84.221.85)  18.542 ms  18.676 ms  18.783 ms<br />
12  i-12-2-0.sjc-core01.bx.reach.com (202.84.140.157)  175.759 ms  176.076 ms  172.576 ms<br />
13  i-2-1.eqnx02.bi.reach.com (202.84.251.122)  178.338 ms  177.970 ms  178.181 ms<br />
14  l3-peer.eqnx02.pr.reach.com (134.159.62.198)  207.217 ms  207.158 ms  207.160 ms<br />
15  ae-21-69.car1.SanJose2.Level3.net (4.68.18.11)  186.873 ms ae-31-99.car1.SanJose2.Level3.net (4.68.18.203)  183.430 ms ae-11-79.car1.SanJose2.Level3.net (4.68.18.75)  183.740 ms<br />
16  SPLICE-COMM.car1.SanJose2.Level3.net (4.59.0.174)  372.320 ms  369.668 ms  368.502 ms<br />
17  resolver1.opendns.com (208.67.222.222)  179.333 ms  202.413 ms  198.676 ms</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rizal</title>
		<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-443381</link>
		<dc:creator>rizal</dc:creator>
		<pubDate>Thu, 20 Jan 2011 09:00:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-443381</guid>
		<description>.. I&#039;am from indonesia .. my trace still got San Jose Server as resolver ..</description>
		<content:encoded><![CDATA[<p>.. I&#8217;am from indonesia .. my trace still got San Jose Server as resolver ..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruel Montero</title>
		<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-438310</link>
		<dc:creator>Ruel Montero</dc:creator>
		<pubDate>Thu, 13 Jan 2011 05:44:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-438310</guid>
		<description>Dear OPENDNS,

208.67.222.222 is from United States(US) in region North America

TraceRoute to 208.67.222.222 [resolver1.opendns.com]
Hop	(ms)	(ms)	(ms)		IP Address	Host name
1	14	17	7		72.249.0.65	 -
2	15	19	10		206.123.64.21	 -
3	7	8	6		8.9.232.73	xe-5-3-0.edge3.dallas1.level3.net
4	8	9	6		4.69.145.69	ae-23-70.car3.dallas1.level3.net
5	13	14	25		4.71.120.66	splice-comm.car3.dallas1.level3.net
6	15	12	7		208.67.222.222	resolver1.opendns.com
Trace complete


My IP

121.97.116.34 is from Philippines(PH) in region Southern and Eastern Asia

TraceRoute to 121.97.116.34 [121.97.116.34.bti.net.ph]
Hop	(ms)	(ms)	(ms)		IP Address	Host name
1	176	5	229		72.249.128.5	 -
2	11	12	7		8.9.232.73	xe-5-3-0.edge3.dallas1.level3.net
3	8	13	6		4.69.145.197	ae-43-90.car3.dallas1.level3.net
4	13	32	12		4.68.63.194	 -
5	45	43	46		213.248.80.13	las-bb1-link.telia.net
6	56	54	59		80.91.247.171	sjo-bb1-link.telia.net
7	282	271	286		213.248.98.242	bayan-ic-124584-sjo-bb1.c.telia.net
8	272	266	252		202.78.119.10	 -
9	278	271	275		121.96.0.1	121.96.0.1.bti.net.ph
10	308	296	305		121.97.116.34	121.97.116.34.bti.net.ph
Trace complete


Thanks</description>
		<content:encoded><![CDATA[<p>Dear OPENDNS,</p>
<p>208.67.222.222 is from United States(US) in region North America</p>
<p>TraceRoute to 208.67.222.222 [resolver1.opendns.com]<br />
Hop	(ms)	(ms)	(ms)		IP Address	Host name<br />
1	14	17	7		72.249.0.65	 -<br />
2	15	19	10		206.123.64.21	 -<br />
3	7	8	6		8.9.232.73	xe-5-3-0.edge3.dallas1.level3.net<br />
4	8	9	6		4.69.145.69	ae-23-70.car3.dallas1.level3.net<br />
5	13	14	25		4.71.120.66	splice-comm.car3.dallas1.level3.net<br />
6	15	12	7		208.67.222.222	resolver1.opendns.com<br />
Trace complete</p>
<p>My IP</p>
<p>121.97.116.34 is from Philippines(PH) in region Southern and Eastern Asia</p>
<p>TraceRoute to 121.97.116.34 [121.97.116.34.bti.net.ph]<br />
Hop	(ms)	(ms)	(ms)		IP Address	Host name<br />
1	176	5	229		72.249.128.5	 -<br />
2	11	12	7		8.9.232.73	xe-5-3-0.edge3.dallas1.level3.net<br />
3	8	13	6		4.69.145.197	ae-43-90.car3.dallas1.level3.net<br />
4	13	32	12		4.68.63.194	 -<br />
5	45	43	46		213.248.80.13	las-bb1-link.telia.net<br />
6	56	54	59		80.91.247.171	sjo-bb1-link.telia.net<br />
7	282	271	286		213.248.98.242	bayan-ic-124584-sjo-bb1.c.telia.net<br />
8	272	266	252		202.78.119.10	 -<br />
9	278	271	275		121.96.0.1	121.96.0.1.bti.net.ph<br />
10	308	296	305		121.97.116.34	121.97.116.34.bti.net.ph<br />
Trace complete</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura Oppenheimer</title>
		<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-438007</link>
		<dc:creator>Laura Oppenheimer</dc:creator>
		<pubDate>Wed, 12 Jan 2011 17:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-438007</guid>
		<description>Hi Ebuks,

Thanks for dropping us a note about your issue!

Simply switching to OpenDNS for your DNS does NOT protect you from the x-rated stuff out there. In order to get Web content filtering set up, you&#039;ll need to sign into the dashboard, set up your network, and choose which categories of content you&#039;d like to block.

The reason is that in order to do Web content filtering, we need to know your IP address so we can apply your settings.

If you have further questions about this, drop us a note in our support center -- we can take a look: https://www.opendns.com/dashboard/support/

Thanks,
Laura</description>
		<content:encoded><![CDATA[<p>Hi Ebuks,</p>
<p>Thanks for dropping us a note about your issue!</p>
<p>Simply switching to OpenDNS for your DNS does NOT protect you from the x-rated stuff out there. In order to get Web content filtering set up, you&#8217;ll need to sign into the dashboard, set up your network, and choose which categories of content you&#8217;d like to block.</p>
<p>The reason is that in order to do Web content filtering, we need to know your IP address so we can apply your settings.</p>
<p>If you have further questions about this, drop us a note in our support center &#8212; we can take a look: <a href="https://www.opendns.com/dashboard/support/" rel="nofollow">https://www.opendns.com/dashboard/support/</a></p>
<p>Thanks,<br />
Laura</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tigerpiceks</title>
		<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-437698</link>
		<dc:creator>tigerpiceks</dc:creator>
		<pubDate>Wed, 12 Jan 2011 03:49:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-437698</guid>
		<description>This one from Smart Telecom (EVDO) Indonesia. :)

C:\Users\duke&gt;tracert 208.67.222.222

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:

  1     *     1284 ms   106 ms  10.20.30.45
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4   112 ms   103 ms    98 ms  10.28.11.34
  5     *        *        *     Request timed out.
  6   105 ms   106 ms   302 ms  10.17.97.40
  7     *      128 ms    96 ms  202.70.48.49
  8   108 ms   106 ms   106 ms  202.70.48.17
  9     *        *      116 ms  202.43.179.41
 10     *        *        *     Request timed out.
 11   331 ms   395 ms   311 ms  202.43.176.222
 12   125 ms   127 ms   134 ms  203.208.131.101
 13   735 ms   456 ms   145 ms  ge-1-1-2-0.sngtp-dr2.ix.singtel.com [203.208.152
.58]
 14   177 ms   177 ms   185 ms  203.208.152.213
 15   222 ms   156 ms   131 ms  203.208.151.250
 16   169 ms   171 ms   181 ms  so-3-0-0-0.hkgcw-cr4.ix.singtel.com [203.208.172
.182]
 17   273 ms   177 ms   165 ms  203.208.152.194
 18   220 ms   239 ms   223 ms  p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.25
0.6.97]
 19   174 ms   193 ms   190 ms  116.51.17.210
 20   196 ms   200 ms   188 ms  resolver1.opendns.com [208.67.222.222]

Trace complete.</description>
		<content:encoded><![CDATA[<p>This one from Smart Telecom (EVDO) Indonesia. <img src='http://blog.opendns.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>C:\Users\duke&gt;tracert 208.67.222.222</p>
<p>Tracing route to resolver1.opendns.com [208.67.222.222]<br />
over a maximum of 30 hops:</p>
<p>  1     *     1284 ms   106 ms  10.20.30.45<br />
  2     *        *        *     Request timed out.<br />
  3     *        *        *     Request timed out.<br />
  4   112 ms   103 ms    98 ms  10.28.11.34<br />
  5     *        *        *     Request timed out.<br />
  6   105 ms   106 ms   302 ms  10.17.97.40<br />
  7     *      128 ms    96 ms  202.70.48.49<br />
  8   108 ms   106 ms   106 ms  202.70.48.17<br />
  9     *        *      116 ms  202.43.179.41<br />
 10     *        *        *     Request timed out.<br />
 11   331 ms   395 ms   311 ms  202.43.176.222<br />
 12   125 ms   127 ms   134 ms  203.208.131.101<br />
 13   735 ms   456 ms   145 ms  ge-1-1-2-0.sngtp-dr2.ix.singtel.com [203.208.152<br />
.58]<br />
 14   177 ms   177 ms   185 ms  203.208.152.213<br />
 15   222 ms   156 ms   131 ms  203.208.151.250<br />
 16   169 ms   171 ms   181 ms  so-3-0-0-0.hkgcw-cr4.ix.singtel.com [203.208.172<br />
.182]<br />
 17   273 ms   177 ms   165 ms  203.208.152.194<br />
 18   220 ms   239 ms   223 ms  p16-2-0-3.r02.sngpsi02.sg.bb.gin.ntt.net [129.25<br />
0.6.97]<br />
 19   174 ms   193 ms   190 ms  116.51.17.210<br />
 20   196 ms   200 ms   188 ms  resolver1.opendns.com [208.67.222.222]</p>
<p>Trace complete.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ebuks</title>
		<link>http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-437435</link>
		<dc:creator>Ebuks</dc:creator>
		<pubDate>Tue, 11 Jan 2011 17:05:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.opendns.com/2010/11/17/new-datacenter-live-singapore/#comment-437435</guid>
		<description>Dear OpenDNS,

I recently heard about OpenDNS through a colleague and I was excited about trying it out. I intended using it for website filtering. Protect the children from getting into certain websites they shouldn&#039;t be going to.

I planned on configuring the DNS IP address on a home router later. However, to test out the service, I co figured the following IP Address as my primary and secondary DNS servers 208.67.222.222 and 208.67.220.220. I visited certain (x rated) websites which I though would be blocked by this service but to my surprise, it opened! I guess my question is what you guy meant by &#039;web filtering&#039;?

How do I get this to work? Is there an alternate DNS IP address I can use?

-Ebuks</description>
		<content:encoded><![CDATA[<p>Dear OpenDNS,</p>
<p>I recently heard about OpenDNS through a colleague and I was excited about trying it out. I intended using it for website filtering. Protect the children from getting into certain websites they shouldn&#8217;t be going to.</p>
<p>I planned on configuring the DNS IP address on a home router later. However, to test out the service, I co figured the following IP Address as my primary and secondary DNS servers 208.67.222.222 and 208.67.220.220. I visited certain (x rated) websites which I though would be blocked by this service but to my surprise, it opened! I guess my question is what you guy meant by &#8216;web filtering&#8217;?</p>
<p>How do I get this to work? Is there an alternate DNS IP address I can use?</p>
<p>-Ebuks</p>
]]></content:encoded>
	</item>
</channel>
</rss>

