10 Sep
2015
10 Sep
'15
9:11 p.m.
Same behaviour from comcast.com in Oregon (a cablemodem connection) as
well as from peakinternet.com (local isp.) Also have tried using one of
my AWS (amazon) virtuals and get the similar results.
comcast.com traceroute stops at:
be2017.ccr21.lax04.atlas.cogentco.com (154.54.0.237)
my amazon instance stops at:
be2019.ccr21.lax04.atlas.cogentco.com (154.54.88.10)
peakinternet.com stops at:
100ge11-1.core1.lax2.he.net (72.52.92.122)
FWIW I noticed this started several weeks ago - been trying to get to
look at current crop of home builts and could not find a way to the web
ring. iinet.net.au is reachable but not members.iinet.net.au
The amazon instance is in the US West region (north-central Oregon I
presume.)
Tomorrow I'll fire up a proxy on the east coast and see what happens.
-Gary
On 09/10/2015 08:49 PM, Brian L. Stuart wrote:
On Thu, 9/10/15, Christian Gauger-Cosgrove
<captainkirk359am at gmail.com> wrote:
From a friend of mine on RoadRunner (I won't
say where, but in the USA
of course); their trace dies as it leaves the Cogent Communications
network (since it bounces through a few of their servers before dying).
I'm
seeing the same behavior from Verizon-provided service.
BLS