For those of you having trouble accessing iLind.net, the network problem appears to be with Roadrunner!
A few minutes ago, I ran a “traceroute”, which follows as my computer tries to access a web page, in this case “www.ilind.net”.
Here’s the result.
Traceroute has started…
traceroute to ilind.net (216.120.254.131), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 3.105 ms 1.319 ms 0.971 ms
2 10.102.120.1 (10.102.120.1) 9.298 ms 7.450 ms 10.499 ms
3 ge10-0-2-oahuhimili-gsr2.hawaii.rr.com (24.25.225.145) 12.295 ms 15.877 ms 10.662 ms
4 ge-2-1-0-bigihimaun-rtr1.hawaii.rr.com (24.25.230.190) 17.987 ms 13.371 ms 17.210 ms
5 xe-6-1-1-lsanca4-rtr1.socal.rr.com (24.25.230.206) 60.305 ms 63.390 ms
xe-2-0-2-lsanca4-rtr1.socal.rr.com (24.25.230.210) 85.320 ms
6 66.109.6.212 (66.109.6.212) 66.302 ms 71.700 ms 62.135 ms
7 ae-3-0.cr0.sjc30.tbone.rr.com (66.109.6.6) 67.792 ms 115.799 ms 78.029 ms
8 ae-1-0.pr0.sjc10.tbone.rr.com (66.109.6.137) 77.129 ms 69.126 ms 68.095 ms
9 64.132.69.69 (64.132.69.69) 75.995 ms 69.856 ms 69.569 ms
10 66-162-65-30.static.twtelecom.net (66.162.65.30) 146.556 ms 147.003 ms 150.012 ms
11 66-162-65-30.static.twtelecom.net (66.162.65.30) 150.396 ms 149.369 ms 164.519 ms
12 * *
As you can see, it stalls out at a Time Warner Telecom computer, identified by the IP address 66.162.65.30.
It seems to me that this is not a pretty picture.
Right now, I can view iLind.net by accessing via my Sprint broadband card, but can’t get there from Oceanic’s Roadrunner service.
In fact, trying to post his while connected via Roadrunner…connection failed.
Repeated after switching to Sprint–All okay.
What’s that about!!
Discover more from i L i n d
Subscribe to get the latest posts sent to your email.
For what it’s worth, I have Roadrunner both at work and at home, and I haven’t had any problems accessing your site at all. Maybe a regional thing? Or only affecting certain IPs?
I think you would have heard more if this was a widespread challenge. I have RR and no access problem.
I had a similar problem with my home phone calling out to my downtown number. Only prefixes in my small geographic area with numbers starting with 397 could not dial out to any 522 numbers. Aa to computers how the hosting is set up can throw off the access from your home ip address too thus giving the false symptoms you describe. I too use my sierra wireless to verify my web site and ip and I use my cell phone to verify Hawaiian Telcom numbers. Especially my business line. This is frustrating when paying big bucks to advertise a number or web site when only a limited area cannot see or call and how is the host to know? I am happy you draw attention to this. At first I thought I was crazy.
In others words, you can get there from here.