Reviews:
 ·Cogeco Voip
 ·Cogeco Cable
| Problems accessing a Tumblr-based site For about the past 2 weeks, my wife has been complaining that she can't visit one of her favourite blogs - www.stfuparentsblog.com to be specific. I tried a lot of things on my end, resetting the crap out of both hardware and software, trying to check there was no shenanigans with DNS. But absolutely nothing's fixed the issue. Every browser on every machine just times out, "Cannot display the page" (or whatever the specific error message is for the given browser). Firefox 3 & 8, Internet Explorer 8 & 9, even webkit-based browsers on an Android phone and HP TouchPad all exhibit the same problem.
The site is up; I can access it from my work internet (which I'm sure will look great on our access log there LOL), among other things.
She follows the site on Facebook as well and posted a comment there about her access problems. A few other people started to chime in - at first, all users were from Cogeco, but then others replied from across Canada (but only Canada).
So it may not be Cogeco-specific, but I was hoping that one of the gurus here might have a suggestion or at least some insight as to what might be going on.
I look forward to any information or help anyone can provide! |
|
cog_biz_useri ruin threads apparently
join:2011-04-19
Hamilton, ON | FWIW, i can't get to it either.
quote:
The following error was encountered:
* Connection to 72.32.231.8 Failed
The system returned:
(110) Connection timed out
--
Myth: It's only fair to pay for quality first-run movies.
Fact: Most movies shown on cable get two stars or less
and are repeated ad nauseum. |
|
| reply to chdude3
It's okay here at UWaterloo, but doesn't work from home in Oakville. Seems like a Cogeco routing issue. |
|
| reply to chdude3
Yup, same thing in northeast Oakville. |
|
|
|
Reviews:
·Cogeco Voip
·Cogeco Cable
| reply to chdude3
Hey - thanks for your responses, guys. I really appreciate the confirmation that it's not a problem specific to our setup. Thanks for taking the time to make your posts.
Since location does seem to play a part, we're near Upper Middle and Trafalgar in Oakville.
Anything that's got ".tumblr.com" in the URL works just fine (ie stormhero.tumblr.com). But any Tumblr based blog that has its own unique URL seems to time out. Examples:
»www.stfuparentsblog.com
»imremembering.com
»cashcats.biz
»www.thecosbysweaterproject.com
Hopefully one of the Cogeco techies can weigh in and advise if there's anything that can be done on our end, or if it's something that can (and will) be fixed on the Cogeco end, that would be great. |
|
| reply to chdude3
Just want to throw my testing in, all those blogs you listed do time out on Cogeco, but on my phone (Bell) they work fine. |
|
 DigitalXeronThere is a lack of sanity
join:2003-12-17
Hamilton, ON
2 edits | reply to chdude3
My organization's network has 2 ISPs, Cogeco (physical link, IPv4) and Hurricane Electric (alternate route, IPv4 and IPv6), I have tested with the following results:
Cogeco (to www.stfuparentsblog.com):
traceroute to www.stfuparentsblog.com (72.32.231.8), 30 hops max, 60 byte packets
3 10.64.172.1 (10.64.172.1) 11.324 ms 12.271 ms 12.311 ms
4 d226-5-225.home.cgocable.net (24.226.5.225) 13.271 ms 13.212 ms 13.218 ms
5 d226-6-130.home.cgocable.net (24.226.6.130) 14.105 ms 14.250 ms 14.252 ms
6 64.34.137.61 (64.34.137.61) 14.145 ms 14.029 ms 14.019 ms
7 10ge.xe-2-0-0.tor-151f-cor-1.peer1.net (216.187.114.145) 13.634 ms slave4.did-it.net (216.187.113.78) 11.803 ms 14.404 ms
8 10ge.xe-5-0-0.tor-1yg-cor-1.peer1.net (216.187.114.49) 13.529 ms 9.327 ms 13.090 ms
9 10ge.xe-0-0-0.chi-eqx-dis-1.peer1.net (216.187.114.141) 23.218 ms 22.161 ms 22.222 ms
10 10ge-ten1-1-0.dal-eqx-xe2-1.peer1.net (216.187.124.73) 46.745 ms 51.654 ms 51.715 ms
11 * * *
12 vlan903.core3.dfw1.rackspace.com (72.3.128.53) 50.492 ms 48.015 ms 49.948 ms
13 intra-core1-core3.dfw1.rackspace.com (72.3.128.82) 51.023 ms 51.150 ms 51.013 ms
14 intra-core5-core1.dfw1.rackspace.com (67.192.56.82) 50.868 ms 51.826 ms 51.922 ms
15 67.192.56.39 (67.192.56.39) 51.017 ms 50.644 ms 48.625 ms
16 72.32.231.8 (72.32.231.8) 57.026 ms 57.875 ms 57.804 ms
However a wget over Cogeco's network hangs:
--2011-12-11 16:43:54-- »www.stfuparentsblog.com/
Resolving www.stfuparentsblog.com... 72.32.231.8
Connecting to www.stfuparentsblog.com|72.32.231.8|:80...
Performing a tcptraceroute to port 80 brings up interesting results:
3 10.64.172.1 10.881 ms 8.098 ms 7.369 ms
4 d226-5-225.home.cgocable.net (24.226.5.225) 9.332 ms 12.156 ms 11.198 ms
5 d226-6-130.home.cgocable.net (24.226.6.130) 9.156 ms 10.332 ms 7.676 ms
6 64.34.137.61 8.325 ms 10.511 ms 8.927 ms
7 10ge.xe-2-0-0.tor-151f-cor-1.peer1.net (216.187.114.145) 12.297 ms 10.604 ms 7.802 ms
8 10ge.xe-0-0-0.tor-1yg-cor-1.peer1.net (216.187.114.133) 10.203 ms 8.556 ms 8.372 ms
9 10ge.xe-0-0-0.chi-eqx-dis-1.peer1.net (216.187.114.141) 19.687 ms 18.823 ms 19.370 ms
10 10ge-ten1-1-0.dal-eqx-xe2-1.peer1.net (216.187.124.73) 46.114 ms 47.920 ms 45.919 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
Sending a route update to our main router to change the route to our HE interface (ip route add 72.32.231.8 dev tun0)...
Hurricane Electric:
traceroute to www.stfuparentsblog.com (72.32.231.8), 30 hops max, 60 byte packets
3 we.love.servers.at.ioflood.com (184.105.134.1) 174.851 ms 174.919 ms 174.943 ms
4 gige-g1-11.core1.phx2.he.net (64.71.135.153) 174.550 ms 174.575 ms 174.592 ms
5 10gigabitethernet1-4.core1.phx1.he.net (184.105.213.17) 174.623 ms 174.638 ms 174.708 ms
6 10gigabitethernet1-3.core1.dal1.he.net (72.52.92.254) 175.277 ms 175.211 ms 175.430 ms
7 eq-dfw.rackspace.net (206.223.118.7) 191.111 ms 128.746 ms 210.526 ms
8 vlan903.core3.dfw1.rackspace.com (72.3.128.53) 283.358 ms 283.345 ms 283.443 ms
9 intra-core1-core3.dfw1.rackspace.com (72.3.128.82) 283.371 ms 283.449 ms 283.532 ms
10 intra-core5-core1.dfw1.rackspace.com (67.192.56.82) 283.470 ms 283.473 ms 283.377 ms
11 67.192.56.39 (67.192.56.39) 283.366 ms 267.892 ms 225.372 ms
12 72.32.231.8 (72.32.231.8) 216.272 ms 215.006 ms 215.024 ms
A wget succeeds and downloads the content:
--2011-12-11 16:49:19-- »www.stfuparentsblog.com/
Resolving www.stfuparentsblog.com... 72.32.231.8
Connecting to www.stfuparentsblog.com|72.32.231.8|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
P3P: CP="ALL ADM DEV PSAi COM OUR OTRo STP IND ONL"
X-Tumblr-User: stfuparents
Link: ; rel=icon
Vary: Accept-Encoding
X-Tumblr-Usec: D=129640
Content-Type: text/html; charset=UTF-8
Content-Length: 42195
Date: Sun, 11 Dec 2011 21:49:19 GMT
Connection: close
Length: 42195 (41K) [text/html]
Saving to: `/dev/null'
100%[================================================================================== ====================================================================>] 42,195 82.5K/s in 0.5s
2011-12-11 16:49:19 (82.5 KB/s) - `/dev/null' saved [42195/42195]
Performing a tcptraceroute using port 80 brings results that clash with the first:
3 we.love.servers.at.ioflood.com (184.105.134.1) 78.575 ms 78.957 ms 73.963 ms
4 gige-g1-11.core1.phx2.he.net (64.71.135.153) 74.669 ms 72.646 ms 73.759 ms
5 10gigabitethernet1-4.core1.phx1.he.net (184.105.213.17) 84.152 ms 74.302 ms 77.751 ms
6 10gigabitethernet1-3.core1.dal1.he.net (72.52.92.254) 104.378 ms 97.969 ms 101.563 ms
7 eq-dfw.rackspace.net (206.223.118.7) 97.976 ms 96.987 ms 100.350 ms
8 vlan903.core3.dfw1.rackspace.com (72.3.128.53) 100.724 ms 99.982 ms 98.165 ms
9 intra-core1-core3.dfw1.rackspace.com (72.3.128.82) 97.394 ms 97.997 ms 98.667 ms
10 intra-core5-core1.dfw1.rackspace.com (67.192.56.82) 97.310 ms 99.477 ms 99.295 ms
11 67.192.56.39 106.032 ms 100.668 ms 100.158 ms
12 72.32.231.8 [open] 100.093 ms 100.127 ms 210.928 ms
The above tests were all performed on the same machine and network, just taking different routes... So it seems like the traffic is dying at peer1's network.
Edit for DNS resolution of all of those blogs:
# dig +short cashcats.biz
72.32.231.8
# dig +short imremembering.com
72.32.231.8
# dig +short www.thecosbysweaterproject.com
thecosbysweaterproject.com.
72.32.231.8
# dig +short www.stfuparentsblog.com
72.32.231.8
--
--Kradorex Xeron
[an error occurred while processing this signature] |
|
| reply to chdude3
said by chdude3:So it may not be Cogeco-specific, but I was hoping that one of the gurus here might have a suggestion or at least some insight as to what might be going on.
I look forward to any information or help anyone can provide!
Hello,
We are aware of the issue and have been working the past few days trying to get it resolved. It appears to affect only custom domains and not tumblr.com domains.
I'll post more as it becomes available and when the issue is resolved.
Thanks! |
|
Reviews:
·Cogeco Voip
·Cogeco Cable
| said by Cogeco_Aaron:Hello,
We are aware of the issue and have been working the past few days trying to get it resolved. It appears to affect only custom domains and not tumblr.com domains.
I'll post more as it becomes available and when the issue is resolved.
Thanks!
Thanks for the update, Cogeco_Aaron. I wanted to leave enough time for Cogeco do do their investigation; it's been over a week since your response but there has been no change in behaviour. The affected sites are still unavailable.
Have you got any more information, or an ETA on when things might be fixed? Thanks again. |
|
exsevenPremium,VIP
join:2003-05-23
Beamsville, ON
kudos:1 | I dont think its a routing issue. Something else
[~/] % nmap -Pn www.stfuparentsblog.com
Starting Nmap 5.59BETA1 ( »nmap.org ) at 2011-12-21 08:49 EST
Nmap scan report for www.stfuparentsblog.com (72.32.231.8)
Host is up (0.040s latency).
Not shown: 995 filtered ports
PORT STATE SERVICE
20/tcp closed ftp-data
21/tcp closed ftp
22/tcp open ssh
25/tcp closed smtp
110/tcp closed pop3
Nmap done: 1 IP address (1 host up) scanned in 45.69 seconds
[~/] % ssh www.stfuparentsblog.com -v
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to www.stfuparentsblog.com [72.32.231.8] port 22.
debug1: Connection established.
debug1: identity file ~/.ssh/id_rsa type 1
debug1: identity file ~/.ssh/id_rsa-cert type -1
debug1: identity file ~/.ssh/id_dsa type -1
debug1: identity file ~/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH_4*
debug1: Enabling compatibility mode for protocol 2.0
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'www.stfuparentsblog.com' is known and matches the DSA host key.
debug1: Found key in ~/.ssh/known_hosts:12
debug1: ssh_dss_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: ~/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: ~/.ssh/id_dsa
debug1: No more authentication methods to try.
Permission denied (publickey). |
|
DigitalXeronThere is a lack of sanity
join:2003-12-17
Hamilton, ON
1 edit | said by exseven:I dont think its a routing issue. Something else
Agreed. I think it's probably the server at 72.32.231.8 or upstream network to that destination is filtering traffic originating from Cogeco's network.
I have done some sniffing around that general IP block (hosted by Rackspace, a public webhosting company) and it seems like other servers on the same AS are responding fine.
I would advise for Cogeco to possibly coordinate with tumblr to diagnose the issue from both ends?
--
--Kradorex Xeron
[an error occurred while processing this signature] |
|
| said by DigitalXeron:I would advise for Cogeco to possibly coordinate with tumblr to diagnose the issue from both ends? That's what is currently taking place. We have talked to Tumblr about it and they're investigating the issue on their end. The issue is we're coming up to the holidays and there's a pretty good chance that people integral to the repair might not be immediately available.
Hopefully we receive a response back quickly that they've found the issue and can get it fixed. |
|
| Any further information, Cogeco_Aaron? We're still experiencing the issue. My wife got frustrated and emailed Tumblr support. Unsurprisingly, they place the blame squarely on Cogeco's shoulders and suggest that we contact you.... |
|
 DW
@cgocable.net | reply to chdude3
I just contacted Cogeco Internet Technical Support.
I had them browse to the website I can't access (a tumblr based site with a custom URL), they had the same issue on their connection as well.
The agent told me to run a traceroute test and send the results off to tech support to launch an investigation by the technicians. I quoted this thread as well to show them all of us are experiencing the same issue.
I will post back the response when they get back to me! Maybe we all have uncovered an issue Cogeco is unaware of.
Fingers crossed! |
|
| reply to chdude3
I've been experiencing this for quite a while. Surprised to see it's not just an issue with my computer or router.
I emailed Tumblr with an explanation and link to this thread and got this response:
Doug, Jan-11 09:46 (EST):
Hi Marc--
Our engineers are aware of this issue and will fix it as soon as they can. Thanks for your patience.
Doug |
|
| I've been tracking this issue for 40 documented days now, with a long and sordid email chain with Tumblr and Cogeco both. As of 10PM EST, I am able to access custom domain Tumblr sites once more (apart from parislemon - I was able to access his again about halfway in, I assume it's being served off some kind of cache) and I'm hearing reports of the same from others whom I've notified. So check yours to see if it works again. Hopefully this is a permanent fix. |
|
Reviews:
·Cogeco Voip
·Cogeco Cable
| said by gojeffcho :I've been tracking this issue for 40 documented days now, with a long and sordid email chain with Tumblr and Cogeco both. As of 10PM EST, I am able to access custom domain Tumblr sites once more (apart from parislemon - I was able to access his again about halfway in, I assume it's being served off some kind of cache) and I'm hearing reports of the same from others whom I've notified. So check yours to see if it works again. Hopefully this is a permanent fix.
Just saw your post, just checked - my wife's happy, one of her favourite sites is now accessible again via Cogeco. Thanks for the info! |
|
