In article <1119915033.966493.275...@g49g2000cwa.googlegroups.com>,
"PG" <paul.greb...@gmail.com> wrote: > Is IStop down... again?
> I'm on a remote network now, and I haven't been able to connect to my > machine at home for a few hours now. I can't reach www.istop.com > either.
I am on iStop DSL, and haven't had any problems today.
It looks like there is a routing problem in the 24.226 network (Cogeco), though, because I can't get to you (the headers reveal that you posted the message from 24.150.192.149):
traceroute to 24.150.192.149 (24.150.192.149), 64 hops max, 40 byte packets 1 192.168.0.1 1.274 ms 0.370 ms 0.282 ms 2 192.168.10.1 1.123 ms 1.069 ms 1.103 ms 3 66.11.165.1 16.697 ms 15.218 ms 15.031 ms 4 66.11.167.166 15.473 ms 24.225 ms 16.443 ms 5 66.11.167.167 46.837 ms 16.538 ms 15.667 ms 6 198.32.245.27 16.666 ms 15.437 ms 15.838 ms 7 24.226.0.102 16.377 ms 17.356 ms 17.155 ms 8 24.226.0.218 15.544 ms 16.355 ms 16.729 ms 9 24.226.9.98 19.247 ms 19.069 ms 17.912 ms 10 24.226.9.102 20.251 ms 20.245 ms 20.366 ms 11 * * * 12 * * * 13 *^C
-ben
----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==---- http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups ----= East and West-Coast Server Farms - Total Privacy via Encryption =----
Well, I'm down too. Modem's synching but I can't log in. This is a traceroute from Rogers:
fly:~ dusanv$ traceroute -n istop.com traceroute to istop.com (66.11.168.194), 64 hops max, 40 byte packets 1 192.150.23.1 29.582 ms 3.364 ms 3.293 ms 2 24.100.110.1 24.642 ms 39.240 ms 35.392 ms 3 10.1.70.129 26.239 ms 25.833 ms 22.059 ms 4 66.185.83.185 32.704 ms 25.498 ms 29.855 ms 5 66.185.82.129 59.619 ms 23.132 ms 28.771 ms 6 66.185.82.125 29.395 ms 73.827 ms 26.795 ms 7 66.185.81.13 52.062 ms 51.212 ms 48.320 ms 8 216.6.82.33 58.389 ms 51.874 ms 53.125 ms 9 216.6.82.6 80.596 ms 62.735 ms 79.983 ms 10 216.6.63.22 93.459 ms 81.388 ms 59.925 ms 11 154.54.10.73 57.343 ms 65.336 ms 65.938 ms 12 154.54.2.197 61.287 ms 56.615 ms 65.367 ms 13 66.28.4.82 59.775 ms 59.325 ms 68.420 ms 14 66.28.4.117 82.027 ms 62.152 ms 78.763 ms 15 66.28.4.218 103.523 ms 68.816 ms 104.758 ms 16 38.112.37.50 75.769 ms 278.393 ms 57.916 ms 17 38.112.21.198 58.695 ms 217.019 ms 391.206 ms 18 66.11.167.161 171.502 ms 94.826 ms 263.104 ms 19 * * * 20 * * * ^C
> I'm on a remote network now, and I haven't been able to connect to my > machine at home for a few hours now. I can't reach www.istop.com > either.
> No one's answering in the office when I call, either. I'd like to know > that someone is looking into this. I need some reassurance that > they've haven't just closed up shop, every time they're gone for more > than a few minutes.
> In article <1119915033.966493.275...@g49g2000cwa.googlegroups.com>, > "PG" <paul.greb...@gmail.com> wrote:
>> Is IStop down... again?
>> I'm on a remote network now, and I haven't been able to connect to my >> machine at home for a few hours now. I can't reach www.istop.com >> either.
> I am on iStop DSL, and haven't had any problems today.
PG wrote: > that someone is looking into this. I need some reassurance that > they've haven't just closed up shop, every time they're gone for more > than a few minutes.
From the outside world, we can still reach one router that belongs to istop. So they aren't completely gone.
And they wouldn't go in one day. If Bell shuts them down again, parts of ISTOP would still stay up (in toronto) and they would setup www.istop.com in Toronto to bypass all bell infrastructure, like they had done in the final hours of their big fault last december.
However, the more likely scenario would be Bell forcing ISTOP to ditch its remaining DSL customers (it was forced to ditch its non-PPPoe customers a few weeks ago), and this would be done by selling those customers to another ISP, with whatever revenus used to pay debts.
In article <1119918033.367322.199...@f14g2000cwb.googlegroups.com>,
dus...@gmail.com wrote: > Well, I'm down too. Modem's synching but I can't log in. This is a > traceroute from Rogers:
Well, yep, I guess their Ottawa link must be down again. Fortunately for me, I am still synced and logged in from earlier, and terminating in Toronto (try hitting me at 66.11.173.61). But I can't resolve www.istop.com nor ping it by number (or anything else on 66.11.168.*).
I suppose if I were to reboot my modem, I would be SOL.
-ben
----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==---- http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups ----= East and West-Coast Server Farms - Total Privacy via Encryption =----
Hope I didn't hurt you too much when I hit you :-)
Interesting that from cogent, it goes to a different router (167.162 instead of 167.161 for the ottawa link).
I take it 6042147canada_inc.demarc.cogentco.com is the first ISTOP router I hit ? (I see a cogent IP address from my end, but I guess it has an istop IP on the other side).
Istop's now been down for 5 hours. I assume/hope it will be back up when we wake up.
But still, I have a eerie feeling that there is more to these relatively frequent interruptions of this one link than meets the eye.
No matter the causes behind the scenes, ISTOP is probably going to be losing customers. DSl customers don't generate much profit, but web hosting does. And web hosting done in ottawa is a big bread winner for ISTOP and is affected by the downing of this link.
If Bell is playing tricks on Ralph, you'd think Ralph would switch this critical link to another supplier. Plenty of possible speculation on why he isn't switching.
In article <1119934222.834486.300...@z14g2000cwz.googlegroups.com>,
dus...@gmail.com wrote: > It's back up now it seems although the web site seems to be down???
Yeah, still can't seem to reach anything on the Ottawa (66.11.168) network.
For some amusement, and reminder of the fun we had in December, look at <http://smtp.istop.com/> which apparently was the stand-in for 'www'.
-ben
----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==---- http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups ----= East and West-Coast Server Farms - Total Privacy via Encryption =----
One can speculate a lot about this. When Bell last screwed ISTOP, istop setup its name server and a small web site in toronto until service was restored.
Right now, they would have reprogrammed their toronto router to shift specific IPs over to tht, and gotten tht to accept to route those IPs.
Wouldn't it be ironic if THT dumped their customers onto look, only to then buy the remnants of ISTOP ?
Yep same here. I can connect using my old USRobitics modem but not with the DSL modem. I just payed for my next month today :-( Time to start thinking about changing again. Where do I go? Videotron or Bell... Edson
> I'm on a remote network now, and I haven't been able to connect to my > machine at home for a few hours now. I can't reach www.istop.com > either.
> No one's answering in the office when I call, either. I'd like to know > that someone is looking into this. I need some reassurance that > they've haven't just closed up shop, every time they're gone for more > than a few minutes.
----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==---- http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups ----= East and West-Coast Server Farms - Total Privacy via Encryption =----
It gets even stranger! A trace to the substitute web site goes via Shaw/Big Pipe and their TORIX peering with iStop:
3 8 ms 9 ms 31 ms 216.254.128.1 [216.254.128.1] 4 14 ms 8 ms 8 ms ge-1-1.bb2.tor.primus.ca [216.254.129.168] 5 10 ms 14 ms 11 ms ra1sh-ge4-2-11.mt.bigpipeinc.com [66.244.223.173] 6 9 ms 16 ms 16 ms rc2sh-ge9-3.mt.shawcable.net [66.163.66.38] 7 8 ms 9 ms 8 ms gw-istop.torontointernetxchange.net [198.32.245.25] 8 13 ms 9 ms 10 ms ip163-167.tor.istop.com [66.11.167.163] 9 23 ms 32 ms 9 ms smtp.istop.com [66.11.167.126]
But a trace to www.istop.com [66.11.168.194] goes via Cogent, not Big Pipe:
3 17 ms 14 ms 11 ms 216.254.128.1 [216.254.128.1] 4 12 ms 12 ms 8 ms ge-1-1.bb1.tor.primus.ca [216.254.129.164] 5 15 ms 15 ms 9 ms g2.ba22.b011027-0.yyz01.atlas.cogentco.com [38.112.1.5] 6 11 ms 9 ms 9 ms g1-1.core01.yyz02.atlas.cogentco.com [66.28.6.29] 7 8 ms 10 ms 12 ms p15-1.core01.yyz01.atlas.cogentco.com [154.54.2.229] 8 13 ms 9 ms 12 ms g0-1.na01.b011027-1.yyz01.atlas.cogentco.com [38.112.37.50] 9 10 ms 8 ms 9 ms 6042147Canada_Inc.demarc.cogentco.com [38.112.21.198] 10 10 ms 9 ms 9 ms ip161-167.tor.istop.com [66.11.167.161] 11 * * * Request timed out. 12 * * * Request timed out.
Note that the two destination IPs (66.11.167.126 and 66.11.168.194) are within a single /20 associated with Doncaster/iStop's AS and yet they are being routed differently from Primus. I can't see exactly what Big Pipe is advertising because I haven't found a looking lass that shows Big Pipe advertising a route to AS21936 (traces from Allstream in Canada and AT&T in the US do not show the Big Pipe route, either), but, since Primus knows about it, Big Pipe must be advertising it to some peers...
Edson gray wrote: > Time to start thinking about changing again. Where do I go? Videotron > or Bell...
Why stoop to either? There are perfectly good third party DSL providers (Teksavvy gets a lot of mention here thanks to JF; I can't complain about Primus; there are probably many, many more.)
-- Geoffrey Welsh <Geoffrey [dot] Welsh [at] bigfoot [dot] com> Never leave until tomorrow what can wait until next week.
Speakin of sitting tight, while checking this very board for news - on my neighbor's free wifi - heheh. Me2 !
Seriously, tho. I'm fed up with iStop. Empasis on the "Stop"! I've been with them for a while, but now that naked DSL is being quietly brough out, I'm gonna go with whichever reliable provider I can find and nix my land line anyway.
I've read some posts that perhaps the writting is on the wall for iStop - that they just can't compete as a reseller and their customers (like me) should be looking elsewhere.
Any thoughts on VIF (I'm in the Montreal area) or Mustang? I think only Sympatico offers naked DSL right now, but the CRTC has to move in soon, no?
Well, there's always 56k...god, what did I put in my coffee this morn? Ouch.
Heh well, I've always found iStop to beat the others with what it had to offer me. Cheap prices, cheap static ip, reverse lookup of my domain, unlimited upstream, generous downstream, no port blockage whatsoever both-ways.
So these are the reasons why i'm coping with the outage and various downtimes iStop has. I've been told teksavvy was very close to them with the offer and price.
As soon as I can ditch my landline, i'm doing that as well. But not to go back with bell at twice the price.
I think that's what bugs me more then anything else.
Add a message to the voicemail explaining what is going on at least. Generally when a company doesn't update its customers as to the current situation, it often means they are bust and could care less.
With istop however, it's almost the norm.
Anyhow, I gave them one chance last time this happened. This is it for me. I just switched out.
PG wrote: > I would like to at least hear something from them. I tried calling > yesterday and the phone just rang. Then the recorded voice said that > voice mail was unavailable. I expect them not to just leave people > wondering like this when they go down. If someone in the company has > an internet connection, how about posting something here?
I am extremly pissed of with them, they coold have left a voice recording if they are to chicken to answer the phone......
I am looking for a different provider and to be sure it will not be sypatico either. (Where two fight they are usualy both to blame)
Reminds me of "Pragma Internet" in Ste-Therese, QC many years ago. One friday night, nothing. Connection dropped, no phone no nothing. We drove down there and saw that the entire offices had been emptied. But the door was not broken.
Well I just called teksavvy, their prices are similar and they set me up on for a dsl login (http://www.teksavvy.com/web/prices_Login.htm) while I was on the line with them. I was happy with Istop untill this happened but they better come up with a very good explanation, or else I will cancel istop and swap alltogether. (I probably will anyway)
IMHO calling them on nonstop redial is a bit over the top, Just because they (istop) are not behaving in a professional manner, that does not mean we have to behave like that tempting as it may be ;)