Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


mkeeley

25 posts

Geek


#275702 5-Sep-2020 15:39
Send private message quote this post

I have a couple of servers in Digital Ocean's San Francisco data center - this morning they seem to be blocked for me but other locations around the world could access them just fine.

 

I tried some tracerts, and narrowed it down to SF area. I tried several different hosts, all seem to break at any2ix peering.

 

(Forgive me if I have the terminology wrong!)

 

I am on 2 Degrees with a static IP.

 

e.g.

 

Digital Ocean SFO1: (or SFO2, SFO3)

 

Tracing route to speedtest-sfo1.digitalocean.com [107.170.223.15]
over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.0.253]
  2     5 ms     3 ms     3 ms  41.7.69.111.static.snap.net.nz [111.69.7.41]
  3     *        *        *     Request timed out.
  4   130 ms   126 ms   128 ms  two-degrees-new-zealand.as23655.any2ix.coresite.com [206.72.211.83]
  5   140 ms   138 ms   139 ms  206.72.211.191.any2ix.coresite.com [206.72.211.191]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.

 

TestMy.Net San Francisco:

 

Tracing route to sf.testmy.net [107.170.222.115]
over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.0.253]
  2     3 ms     3 ms     3 ms  41.7.69.111.static.snap.net.nz [111.69.7.41]
  3     *        *        *     Request timed out.
  4   126 ms   128 ms   126 ms  two-degrees-new-zealand.as23655.any2ix.coresite.com [206.72.211.83]
  5   141 ms     *      140 ms  206.72.211.191.any2ix.coresite.com [206.72.211.191]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.

 

However, to a LA or other Digital Ocean datacenters works fine:

 

TestMy.Net Los Angeles:

 

Tracing route to lax.testmy.net [45.63.56.125]
over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.0.253]
  2     7 ms     5 ms     4 ms  41.7.69.111.static.snap.net.nz [111.69.7.41]
  3     *        *        *     Request timed out.
  4   126 ms   128 ms   126 ms  two-degrees-new-zealand.as23655.any2ix.coresite.com [206.72.211.83]
  5   130 ms     *      129 ms  clan-servers-hosting.as20473.any2ix.coresite.com [206.72.211.53]
  6   128 ms     *      150 ms  10.68.5.5
  7   128 ms     *      128 ms  10.68.16.38
  8     *        *        *     Request timed out.
  9   128 ms   126 ms   128 ms  lax.testmy.net [45.63.56.125]

Trace complete.

 

Digital Ocean New York:

 

Tracing route to speedtest-nyc1.digitalocean.com [165.227.194.167]
over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.0.253]
  2    22 ms     7 ms     3 ms  41.7.69.111.static.snap.net.nz [111.69.7.41]
  3     *        *        *     Request timed out.
  4   130 ms   126 ms   130 ms  twodegrees-svc063403-ic344202.c.telia.net [62.115.175.227]
  5   129 ms   126 ms   138 ms  las-b24-link.telia.net [62.115.175.226]
  6   185 ms   184 ms     *     ash-bb2-link.telia.net [62.115.121.221]
  7     *        *        *     Request timed out.
  8   218 ms   220 ms     *     nyk-b3-link.telia.net [62.115.139.151]
  9     *      219 ms   219 ms  digitalocean-ic-306497-nyk-b3.c.telia.net [62.115.45.6]
 10   223 ms   224 ms     *     138.197.244.16
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   222 ms   219 ms     *     165.227.194.167
 15   222 ms     *      220 ms  165.227.194.167

Trace complete.

 

I called 2 Degrees support, the support rep there could access my sites OK, which I find super weird. It's like my IP is being blocked, at a peering level! So strange.
Anyone else with the same issues to speedtest-sfo1.digitalocean.com or sf.testmy.net ?

 

Mike


Create new topic
timmmay
16532 posts

Uber Geek

Trusted
Subscriber

  #2557470 5-Sep-2020 15:54
Send private message quote this post

If you post the server IP people on different service could try a ping for you.


mkeeley

25 posts

Geek


  #2557471 5-Sep-2020 15:56
Send private message quote this post

They can try the hosts I posted above. I have already tried my own hosts via VPN etc and it works OK.

 

speedtest-sfo1.digitalocean.com

 

sf.testmy.net 

 

 


 
 
 
 


michaelmurfy
/dev/null
9636 posts

Uber Geek

Moderator
Trusted
Lifetime subscriber

  #2557472 5-Sep-2020 15:58
Send private message quote this post
mkeeley

25 posts

Geek


  #2557474 5-Sep-2020 16:00
Send private message quote this post

Thanks @michaelmurfy, could you post a tracert?


Spong
805 posts

Ultimate Geek

Trusted

  #2557600 5-Sep-2020 18:00
Send private message quote this post

I'm on 2Degrees Ultra Broadband, also on a static IP, located in Auckland, and I get the same results as you when I attempt a Traceroute to your servers. Example below:

 

Tracing route to 107.170.223.15 over a maximum of 30 hops

 

  1    <1 ms    <1 ms    <1 ms  192.168.0.254
  2    10 ms     5 ms     5 ms  43.7.69.111.static.snap.net.nz [111.69.7.43]
  3     *        *        *     Request timed out.
  4   126 ms   125 ms   128 ms  two-degrees-new-zealand.as23655.any2ix.coresite.
com [206.72.211.83]
  5   140 ms   137 ms   138 ms  206.72.211.191.any2ix.coresite.com [206.72.211.1
91]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

 

Trace complete.





Tivo upgrades to operate with the new OzTivo EPG, support and service. Over 400 performed here so far. See: www.hillcrest.net.nz


mkeeley

25 posts

Geek


  #2557624 5-Sep-2020 18:57
Send private message quote this post

OK thanks very much, seems like it's not just my IP, but something with the peering agreements.


jarledb
Webhead
2556 posts

Uber Geek

Moderator
Trusted
Lifetime subscriber

  #2557628 5-Sep-2020 19:07
Send private message quote this post

Here are Traceroutes from 2degrees in Kapiti/Wellington:

 

traceroute to 107.170.223.15 (107.170.223.15), 64 hops max, 52 byte packets
 1  fritz.box (192.*.*.*)  4.379 ms  3.503 ms  2.830 ms
 2  86.7.69.111.static.snap.net.nz (111.69.7.86)  3.924 ms  5.206 ms  5.804 ms
 3  * * *
 4  two-degrees-new-zealand.as23655.any2ix.coresite.com (206.72.211.83)  144.223 ms  145.521 ms  139.553 ms
 5  206.72.211.191.any2ix.coresite.com (206.72.211.191)  153.465 ms  161.851 ms  153.879 ms
 6  * * *
 7  * * *
 8  107.170.223.15 (107.170.223.15)  151.624 ms  150.937 ms  150.131 ms

 

 

 

traceroute to 107.170.222.115 (107.170.222.115), 64 hops max, 52 byte packets
 1  fritz.box (192.*.*.*)  1.247 ms  1.068 ms  0.947 ms
 2  86.7.69.111.static.snap.net.nz (111.69.7.86)  2.272 ms  2.564 ms  3.296 ms
 3  * * *
 4  two-degrees-new-zealand.as23655.any2ix.coresite.com (206.72.211.83)  137.847 ms  138.189 ms  138.668 ms
 5  206.72.211.191.any2ix.coresite.com (206.72.211.191)  148.962 ms  149.185 ms  149.117 ms
 6  * * *
 7  * * *
 8  sf.testmy.net (107.170.222.115)  151.145 ms  150.212 ms  149.572 ms

 

 

 

 


 
 
 
 


michaelmurfy
/dev/null
9636 posts

Uber Geek

Moderator
Trusted
Lifetime subscriber

  #2557630 5-Sep-2020 19:09
Send private message quote this post

mkeeley:

 

OK thanks very much, seems like it's not just my IP, but something with the peering agreements.

 

I don't think this has anything to do with peering. Both of you are posting from the same IPv4 subnet so it could be as simple as them having this blocked for some reason.

 

From my connection:

 

traceroute speedtest-sfo1.digitalocean.com
traceroute to speedtest-sfo1.digitalocean.com (107.170.223.15), 30 hops max, 60 byte packets
 1  router (192.168.2.1)  0.273 ms  0.241 ms  0.180 ms
 2  86.7.69.111.static.snap.net.nz (111.69.7.86)  1.907 ms  1.906 ms  1.862 ms
 3  * * *
 4  two-degrees-new-zealand.as23655.any2ix.coresite.com (206.72.211.83)  137.072 ms  137.004 ms  137.011 ms
 5  206.72.211.191.any2ix.coresite.com (206.72.211.191)  147.796 ms  147.846 ms  147.802 ms
 6  * * *
 7  * * *
 8  107.170.223.15 (107.170.223.15)  149.191 ms  149.105 ms  149.036 ms

 

I note this is also available over IPv6:

 

traceroute6 speedtest-sfo1.digitalocean.com
traceroute to speedtest-sfo1.digitalocean.com (2604:a880:1:20::9:9001), 30 hops max, 80 byte packets
 1  2406:e001:1:df01::1 (2406:e001:1:df01::1)  0.484 ms  0.428 ms  0.416 ms
 2  2406:e000:2801:1:: (2406:e000:2801:1::)  1.044 ms  1.397 ms  1.007 ms
 3  * * *
 4  2001:504:13::211:83 (2001:504:13::211:83)  136.765 ms  137.005 ms  136.910 ms
 5  * * *
 6  * * *
 7  * * *
 8  2604:a880:1:20::9:9001 (2604:a880:1:20::9:9001)  148.903 ms  148.941 ms  148.928 ms

 

Perhaps enable IPv6?





mkeeley

25 posts

Geek


  #2557656 5-Sep-2020 20:16
Send private message quote this post

Good point - I had assumed there would be a few more hops after the last I saw, but based on your trace it looks pretty close to the final servers.

 

Also I assumed the two servers were in different data centres, but actually the testmy.net server is a digital ocean server too. oops. So maybe Digital Ocean is blocking our 2degrees subnet.

 

I enabled IPv6, but get similar results:

 

Tracing route to speedtest-sfo1.digitalocean.com [2604:a880:1:20::9:9001]
over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  fritz.box [2406:e002:58d6:b101:3a10:d5ff:fe23:496f]
  2     5 ms     7 ms     7 ms  2406:e000:2801:29::
  3     *        *        *     Request timed out.
  4   159 ms   157 ms   159 ms  2001:504:13::211:83
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.

 

 


Create new topic





News »

Huawei launches IdeaHub Pro in New Zealand
Posted 27-Oct-2020 16:41


Southland-based IT specialist providing virtual services worldwide
Posted 27-Oct-2020 15:55


NASA discovers water on sunlit surface of Moon
Posted 27-Oct-2020 08:30


Huawei introduces new features to Petal Search, Maps and Docs
Posted 26-Oct-2020 18:05


Nokia selected by NASA to build first ever cellular network on the Moon
Posted 21-Oct-2020 08:34


Nanoleaf enhances lighting line with launch of Triangles and Mini Triangles
Posted 17-Oct-2020 20:18


Synology unveils DS16211+
Posted 17-Oct-2020 20:12


Ingram Micro introduces FootfallCam to New Zealand channel
Posted 17-Oct-2020 20:06


Dropbox adopts Virtual First working policy
Posted 17-Oct-2020 19:47


OPPO announces Reno4 Series 5G line-up in NZ
Posted 16-Oct-2020 08:52


Microsoft Highway to a Hundred expands to Asia Pacific
Posted 14-Oct-2020 09:34


Spark turns on 5G in Auckland
Posted 14-Oct-2020 09:29


AMD Launches AMD Ryzen 5000 Series Desktop Processors
Posted 9-Oct-2020 10:13


Teletrac Navman launches integrated multi-camera solution for transport and logistics industry
Posted 8-Oct-2020 10:57


Farmside hits 10,000 RBI customers
Posted 7-Oct-2020 15:32









Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Support Geekzone »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.