| [Eastern Ontario] Inaccessible sites There seem to be a number of sites in Brazil I cannot access through Cogeco but can access through any other provider. These used to be accessible through Cogeco, but now time out on all computers and mobile devices on my home network. I am wondering why this would be the case, since I am having no problems with North American sites. Here is an example.
www.reclameaqui.com.br
There is no problem accessing the site on Rogers cable at a friend's house. There is no problem accessing the site on my Virgin mobile account on my iPad (but cannot access it through Cogeco when the iPad is connected to my home wifi). I can access it on my cellphone with another provider. In short, no computer or device can access this or some other Brazilian pages through Cogeco.
I'm not sure when this started, since I've been out of Canada (in Brazil). However, in March there was no problem. And during the three weeks I have been back in Canada I have not been able to access the site above and some other Brazilian sites. Yet most Brazilian sites are fine.
Can anyone else reading this message access the site above? If not, any ideas what might be causing the problem? |
|
|
|
Reviews:
 ·Cogeco Cable
| I can't access the site you mentioned either, so I decided to run a tracert just to see what's going on while trying to connect.
3 17 ms 11 ms 11 ms d226-5-161.home.cgocable.net [24.226.5.161]
4 186 ms 199 ms 203 ms te4-1.ccr01.yhm01.atlas.cogentco.com [38.122.17.17]
5 145 ms 208 ms 207 ms te3-7.ccr01.buf02.atlas.cogentco.com [154.54.82.101]
6 17 ms 14 ms 13 ms te8-8.ccr02.cle04.atlas.cogentco.com [154.54.31.237]
7 18 ms 38 ms 16 ms te7-8.ccr01.pit02.atlas.cogentco.com [154.54.83.174]
8 26 ms 27 ms 25 ms te0-0-0-5.mpd21.dca01.atlas.cogentco.com [154.54.40.81]
9 26 ms 27 ms 28 ms te0-2-0-5.mpd21.iad02.atlas.cogentco.com [154.54.41.122]
10 26 ms 28 ms 27 ms Cogent-Xe9-3-0grawaseq1.red.telefonica-wholesale.net [213.140.53.105]
11 62 ms 74 ms 99 ms Xe9-0-8-0-grtmiabr3.red.telefonica-wholesale.net [84.16.14.202]
12 173 ms 181 ms 170 ms Xe3-1-3-0-grtsaosi2.red.telefonica-wholesale.net [213.140.49.226]
13 187 ms 167 ms 163 ms TEBRASIL-0-0-6-0-grtsaosi3.red.telefonica-wholesale.net [213.140.39.82]
14 179 ms 173 ms 169 ms 176.52.252.210
15 * * * Request timed out.
16 181 ms * * 200-147-29-11.static.uol.com.br [200.147.29.11]
17 169 ms * * 200-147-29-11.static.uol.com.br [200.147.29.11]
18 * 177 ms * host91-33.dh-c.net.br [200.225.91.33]
19 177 ms 178 ms 177 ms host91-33.dh-c.net.br [200.225.91.33]
20 * * * Request timed out.
Just keeps timing out after that. A couple of repeats in the route, and some connectivity problems with the .br end of the line.... don't know if this will help anyone, but there it is. |
|
 dillyhammerA. Good. Start.Premium,MVM
join:2010-01-09
Hamilton, ON
kudos:9 | reply to Toollio
I can at least confirm that I can get to it on my Teksavvy DSL connection, and my neighbour next door cannot get to it on his Cogeco connection.
Mike |
|
| said by dillyhammer:I can at least confirm that I can get to it on my Teksavvy DSL connection, and my neighbour next door cannot get to it on his Cogeco connection.
Mike
Thanks to everyone so far. The post above pretty much confirms, as I have, that it is a Cogeco problem. I can confirm that there is no problem at the Brazil end. I just had a friend access the site in Brazil...and I am still getting it on my virgin mobile, but not Cogeco. |
|
Host:
Wireless Networking
All Things Unix
Cox HSI
Efficient
Southwest Chat
| reply to Toollio
The site works fine via web browser from here in the US, but the trace shows some problems along the way.
bash-4.1# tcptraceroute www.reclameaqui.com.br
Selected device wlan0, address 192.168.1.106, port 48857 for outgoing packets
Tracing the path to www.reclameaqui.com.br (200.98.215.88) on TCP port 80 (http), 30 hops max
1 192.168.1.2 0.985 ms 0.853 ms 0.787 ms
2 10.73.64.1 9.509 ms 9.512 ms 10.772 ms
3 ip68-4-12-21.oc.oc.cox.net (68.4.12.21) 9.334 ms 12.964 ms 7.974 ms
4 ip68-4-13-156.oc.oc.cox.net (68.4.13.156) 10.549 ms 13.752 ms 13.380 ms
5 ip68-4-11-2.oc.oc.cox.net (68.4.11.2) 8.979 ms 25.134 ms 10.395 ms
6 ip68-4-11-92.oc.oc.cox.net (68.4.11.92) 11.682 ms 19.073 ms 8.707 ms
7 paltbprj02-ae0.0.rd.pt.cox.net (68.1.0.235) 24.322 ms 23.860 ms 23.906 ms
8 GE7-0-8-0-grtpaopx3.red.telefonica-wholesale.net (213.140.55.113) 24.554 ms 25.427 ms 24.445 ms
9 Xe10-1-8-0-grtmiabr4.red.telefonica-wholesale.net (94.142.119.50) 89.608 ms 184.292 ms 88.787 ms
10 Xe2-0-6-0-grtsaosi2.red.telefonica-wholesale.net (94.142.118.145) 207.471 ms 204.641 ms 236.774 ms
11 Xe0-1-6-0-grtsaosi3.red.telefonica-wholesale.net (94.142.118.81) 244.887 ms 204.091 ms 204.142 ms
12 176.52.252.210 216.352 ms 204.340 ms 203.909 ms
13 201-0-5-210.dsl.telesp.net.br (201.0.5.210) 204.037 ms 235.524 ms 204.812 ms
14 * * *
15 200-147-29-11.static.uol.com.br (200.147.29.11) 204.064 ms 208.560 ms 205.181 ms
16 * * *
17 host91-33.dh-c.net.br (200.225.91.33) 205.412 ms 206.180 ms 204.102 ms
18 * * *
19 reclameaqui.com.br (200.98.215.88) [open] 203.962 ms 205.996 ms *
|
|
dillyhammerA. Good. Start.Premium,MVM
join:2010-01-09
Hamilton, ON
kudos:9 Reviews:
 ·Start Communicat..
·Cogeco Cable
·TekSavvy DSL
·Caneris
| reply to Toollio
said by Toollio:and I am still getting it on my virgin mobile
No problem getting it on my iphone via Fido, works fine.
Mike
--
Cogeco - The New UBB Devil -»[Burloak] Usage Based Billing Nightmare
Make The Switch - »openmedia.ca/switch |
|
| reply to No_Strings
said by No_Strings 
17 host91-33.dh-c.net.br (200.225.91.33) 205.412 ms 206.180 ms 204.102 ms
18 * * *
19 reclameaqui.com.br (200.98.215.88) [open : 203.962 ms 205.996 ms *
[/code]
Through Cogeco I get the same second last hop as you, but after that it is destination unreachable. There is no final hop to 200.98.215.88, either on a trace using reclameaqui.com.br or tracing to 200.98.215.88. |
|
| reply to Toollio
I can access the aforementioned site no prob.
using cogeco. |
|
| reply to Toollio
I think there are some routing issues with Cogeco right now or with one of their downstream peers...
Hotmail/Outlook for me has been troublesome on Cogeco. It partially loads or hangs. Using my DSL work connection, it works just fine. I VPN in to work, and then access Hotmail or Outlook.com it works fine. It does come and go too. Sometimes it loads a-ok, and others it times out for no reason.
I have noticed since about Tuesday there has been some general trouble getting to sites. Sometimes Engadget, and Facebook are slow as well. |
|
| I still cannot get the site I mentioned, as well as a few others in Brazil. Perhaps someone at Cogeco who reads this thread could offer an explanation.
FYI, I tried the same site on two neighbours' Cogeco connections. They can't get it either--as was the case with some other posters in this thread. So it definitely has nothing to do with my network. And because it is available through other providers in Ontario it seems to have everything to do with Cogeco. |
|
| I can't get to it with my Cogeco connection.
I switch to my DSL connection, and can immediately access the site. |
|
| reply to Toollio
I'm in eastern Ontario (Cornwall) on Cogeco and I get to that site. |
|
1 edit | Very strange. So people in Cobourg (my neighbours and I) and Hamilton cannot access the site, but people in Cornwall and some other Cogeco cities can. I remain puzzled. I'm not making a big deal out of one site, but there are others. And surely every Cogeco customer should be able to get this and every legit site (and it is legit) not just some customers. |
|
MrPink
join:2003-08-15
Peterborough, ON | reply to Toollio
site won't load for me and i'm in peterborough... |
|
| reply to Toollio
It would help if someone posted a tracert from their Cogeco account that CAN access the site. Maybe they have different routing, for some reason. |
|
cog_biz_useri ruin threads apparently
join:2011-04-19
Hamilton, ON | reply to Toollio
# nslookup www.reclameaqui.com.br
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: www.reclameaqui.com.br
Address: 200.98.215.88
# tracepath www.reclameaqui.com.br
1: bloomfield 0.038ms pmtu 1500
1: smoothwall 0.655ms
1: smoothwall 0.531ms
2: 10.74.192.1 18.059ms
3: d226-5-209.home.cgocable.net 18.593ms
4: no reply
5: no reply
6: no reply
7: te9-7.ccr01.jfk01.atlas.cogentco.com 22.549ms
8: te0-0-0-5.mpd21.dca01.atlas.cogentco.com 29.621ms asymm 9
9: te0-2-0-5.mpd21.iad02.atlas.cogentco.com 28.800ms asymm 10
10: te0-2-0-1.mpd21.iad02.atlas.cogentco.com 28.033ms
11: Cogent-Xe9-3-0grawaseq1.red.telefonica-wholesale.net 32.598ms asymm 12
12: Xe2-0-0-0-grtsaosi3.red.telefonica-wholesale.net 192.401ms asymm 15
13: 176.52.252.210 177.204ms
14: TE-Brasil-1-0-6-0-grtsaosi3.red.telefonica-wholesale.net 164.852ms asymm 13
15: 201-0-5-210.dsl.telesp.net.br 169.156ms asymm 13
16: 200-147-29-3.static.uol.com.br 181.223ms asymm 15
17: 200-147-29-3.static.uol.com.br 166.100ms asymm 19
18: host91-33.dh-c.net.br 183.138ms asymm 16
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
# tracepath www.reclameaqui.com.br
1: bloomfield 0.039ms pmtu 1500
1: smoothwall 0.620ms
1: smoothwall 0.533ms
2: 10.74.192.1 8.954ms
3: d226-5-209.home.cgocable.net 11.784ms
4: no reply
5: no reply
6: no reply
7: te9-7.ccr01.jfk01.atlas.cogentco.com 111.353ms
8: te0-3-0-7.mpd21.jfk02.atlas.cogentco.com 21.826ms
9: te0-2-0-5.mpd21.iad02.atlas.cogentco.com 29.378ms asymm 10
10: XE2-3-0-grtwaseq5.red.telefonica-wholesale.net 29.361ms asymm 12
11: Cogent-Xe9-3-0grawaseq1.red.telefonica-wholesale.net 31.231ms asymm 12
12: Xe10-0-2-0-grtmiabr4.red.telefonica-wholesale.net 76.432ms asymm 10
13: TEBRASIL-0-0-6-0-grtsaosi3.red.telefonica-wholesale.net 184.198ms asymm 17
14: 201-0-5-210.dsl.telesp.net.br 165.605ms asymm 18
15: 201-0-5-210.dsl.telesp.net.br 165.309ms asymm 18
16: 200-147-29-3.static.uol.com.br 160.503ms asymm 19
17: 200-147-29-3.static.uol.com.br 177.534ms asymm 19
18: host91-33.dh-c.net.br 206.727ms asymm 15
19: host91-33.dh-c.net.br 179.254ms asymm 16
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
no go.
--
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. |
|
exsevenPremium,VIP
join:2003-05-23
L8E0G6
kudos:1 | reply to Toollio
I'm just going to point out that the last hop when you can't reach it is the second last hop when you can. There is probably sole firewall issues or something else in Brazil out of cogeco control.
Try contacting dh-c.net.br |
|
| said by exseven:I'm just going to point out that the last hop when you can't reach it is the second last hop when you can. There is probably sole firewall issues or something else in Brazil out of cogeco control.
Try contacting dh-c.net.br
There is no issue at the Brazil end. I just asked my wife, who is in Brazil, to access the site from there--no problems. I can still access the site fine in Canada with my Virgin mobile account on my ipad. I just had a friend on Rogers in Toronto try it again, and he can access it as usual. I can access it on my cellular.
The reality is that this problem seems to affect only Cogeco subscribers--and strangely only a portion of them. One would assume a problem at the Brazil end would affect everyone--or at least all Cogeco subscribers.
Here is my tracert from this morning, similar to the poster above. (I have Xd out some addresses for security.) It would be interesting if someone who can access the site could post theirs.
Tracing route to www.reclameaqui.com.br [200.98.215.88]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms xxx]
2 5 ms 6 ms 5 ms x.x.x.x
3 21 ms 19 ms 18 ms d226-5-109.home.cgocable.net [xx.x x.xx]
4 16 ms 17 ms 18 ms xe-2-2-0.tor10.ip4.tinet.net [77.67.69.237]
5 29 ms 29 ms 28 ms xe-1-1-0.nyc23.ip4.tinet.net [89.149.185.81]
6 41 ms 41 ms 81 ms as12956.ip4.tinet.net [77.67.78.2]
7 117 ms 74 ms 72 ms Xe11-1-8-0-grtmiabr4.red.telefonica-wholesale.ne
t [94.142.126.118]
8 172 ms 232 ms 172 ms Xe2-0-0-0-grtsaosi3.red.telefonica-wholesale.net
[94.142.123.106]
9 185 ms 182 ms 186 ms Xe1-0-4-0-grtsaosi3.red.telefonica-wholesale.net
[94.142.118.89]
10 173 ms 174 ms 174 ms 176.52.253.238
11 * * * Request timed out.
12 176 ms 186 ms 189 ms 200-147-29-3.static.uol.com.br [200.147.29.3]
13 * 177 ms * 200-147-29-3.static.uol.com.br [200.147.29.3]
14 186 ms * 177 ms host91-33.dh-c.net.br [200.225.91.33]
15 * * 179 ms host91-33.dh-c.net.br [200.225.91.33]
16 * * * Request timed out.
17 * * * Request timed out.
|
|
exsevenPremium,VIP
join:2003-05-23
L8E0G6
kudos:1 | As the trace gets to host91-33.dh-c.net.br in all cases i would say the issue is between them and reclameaqui.com.br or a firewall at reclameaqui that is blocking a/multiple subnets. Contact them and ask for a reverse trace back to your home IP, and to verify their firewalls and with their hoster (dh-c.net). The packet leaves the cogeco network and makes it almost all the way to the end system then stops...
17 host91-33.dh-c.net.br (200.225.91.33) 205.412 ms 206.180 ms 204.102 ms
18Â * * *
19 reclameaqui.com.br (200.98.215.88) [open] 203.962 ms 205.996 ms * |
|
2 edits | said by exseven:As the trace gets to host91-33.dh-c.net.br in all cases i would say the issue is between them and reclameaqui.com.br or a firewall at reclameaqui that is blocking a/multiple subnets. Contact them and ask for a reverse trace back to your home IP, and to verify their firewalls and with their hoster (dh-c.net). The packet leaves the cogeco network and makes it almost all the way to the end system then stops...
17 host91-33.dh-c.net.br (200.225.91.33) 205.412 ms 206.180 ms 204.102 ms
18 * * *
19 reclameaqui.com.br (200.98.215.88) [open] 203.962 ms 205.996 ms *
How, then, would you explain the fact that Cogeco subscribers in Cornwall (see above) and at least one location can access the site? Surely the end points in Brazil would not be different for different Cogeco clients?
There is no point in contacting dh-c.net. Brazilian companies are notoriously bad at responding to consumer issues. I will receive no reply.
Edit to add info:
I just tried an experiment. I am now accessing the site through a VPN server in Montreal. The site can be reached. However, the tracert seems to be the same as with cogeco--final hop unreachable and the same second-last hop. I also did a trace on my ipad through virgin mobile--I get the site, but trace shows final destination unceachable and the same second last hop. This suggests to me that the final destination cannot be pinged or tracerted, and that does not necessarily mean it is broken. Many routers and providers block pings and tracerts ( ICMP packets). |
|
