Like Whoa Goes Cogent...
 

Just the facts...

12 65.112.96.98 (65.112.96.98) 42.300 ms 42.008 ms 42.286 ms
13 000-073.np1.net (64.61.0.73) 41.172 ms 41.369 ms 41.414 ms
14 001-173.np1.net (64.61.1.173) 49.816 ms 41.863 ms 41.847 ms
15 Global_Net_Advertising.demarc.cogentco.com (66.28.20.70) 45.143 ms 45.200 ms 45.326 ms
16 ns2.likewhoa.com (66.181.170.170) 44.634 ms 44.502 ms 44.661 ms

nothing wrong with cogent. if BGP'ed correctly it just adds another pipe to feed off of, and with a lot of people using cogent since it's cheap it means cleaner/more direct connections for all those folks connecting to you.

i've been using a rackshack server off their cogent line for months and have only had one downtime when fiber was cut. other than that it's proven just as reliable and fast as anything else.

We clearly do not consider Cogent to be a provider that fits the quality of our service, at the same time, after debating the issue for some time, we have decided that customer's uptime at the moment is a primary issue.

We always had Cogent, but as a lower-end hosting, while we are actively working to restore Verio, we would like to alleviate the slow loading times problems, temporarily.

Global Net Advertising, seen on the traceroute, is a LikeWhoa managed company that owns SexCounter, AllLiquid and other adult properties.

That's fine, but what if your customers were promised Tier-1 bandwidth and pay Tier-1 prices? Wouldn't you be pissed off if you just wound up at another Cogent house?

A very wise statement. We consider the scenario on our hands as not being fixed yet. This means that until Cogent is permanently removed from BGP (we expect to happen within 1-4 hours, after Verio finally rejoins) we will consider this as downtime, and credit our customers per our service level agreements accordingly.

I agree, but if I've received quality service for well over a year, I think I can deal with a couple of hours of Cogent connectivity rather than becoming another revolving door customer.

I don't think anyone ever said it was permanent.

a good reply that also makes sense
:thumbsup

Give in to the dark side. Become one with Cogent. The force is strong with us.

aslong as it's up,, this is good enough for me now

fwiw, still no routes from verio announced, only routes from NP1's routers (through Qwest). i don't even see cogent except as a line between NP1 and Qwest. does NP1 sell Cogent?

I see the cogent only on the outbound. Not a big deal, things appear to be working again.

I have been running facility at Rackshack also, the cogent is surprisingly solid and fast. I do have a complaint about their routing and network topography, but it's working.

Rackshack on the other hand is a piece of shit. Those morons have caused us to have three major outages in the first six weeks as well as firewalled us out of our own machine at the router. They even knowingly gave us a misconfigured machine (actually they configured the network card to only output 2 megabits) - capable of fractions of what we were paying for and committed to. They have some guy there 24 hours to answer the phone but they are powerless to solve problems and always shift the blame to us. How could a fiber cut in their backyard be my fault? How could a misconfigured network card on a machine we were moving into be our fault? How could a switch firewall be our fault if we don't have any passwords for it? Anyway, Rackshack sucks ass.

Buy my content. It's good.

cogent is great. its one of the best b/w carriers i have been with. better then alot of crapy pipe out there right now.

plus its so so so cheap

now that is a good point. if people are charging uunet rates but supplying cogent bandwidth, then it's not cool. but cogent itself has been fine with me, i've even thought of putting some servers in their datacenter and taking advantage of their 100mbit/$3k deal.

They are still on Cogent when I checked today, despite the lie in this thread made by Tukhman yesterday... "This means that until Cogent is permanently removed from BGP (we expect to happen within 1-4 hours"

... My questions to the people that are hosted there are, Will you leave if they continue to use Cogent as their only route? and... How long will you wait before you realize Cogent is and will be their only route from now on?

16 62 ms 77 ms 93 ms 66.28.20.70 Global_Net_Advertising.demarc.cogentco.com.

When I read the thread from BandwidthTruth about them buring level3 and Verio for money, I was skeptical at first. Not that I do not believe they would do it, but that Verio and Level3 would lets these punks get that far in debt.

Anyway... I would like to hear from some of the current customers of LIEwhoa's to answer those two questions for us...

Thanks,

bash

Jesus folks.

Give em' a break. I can't imagine that the folks at Like Whoa would fuck over such a huge customer base.

Are they having problems? yes

Are they trying to fix it? Yes

Will they take care of you when the bill comes at the end of the month? Yes - they already said they would.

Every ISP has problems every now and then. From what I hear, LW is a class outfit and wouldn't fuck over webmasters like some here say they are.

BGP4 is an animal that needs care and feeding, and occasionally shit gets fucked up. Better to be slow than down.

Agree. No fucking way any provider would let another get that far in the hole. Never. You cut bait after the first non-payment. Especially these guys (Verio and L3). It's a BGP4 problem.

Actually you are the moron.
Only some of the traffic is transported through cogentco.
Here from Denmark I am not being routed through Cogentco.
Before you bitch about something please do a bit of resarch first so you won't look like a fool when you try and badmouth someone :thumbsup

Never in the history of this board has an adult host had downtime for 12 hours and they have it happen twice in one year!

I have also heard on the contrary. Although I have never had the pleasure of meeting them in person... I will say that I was told from friends that have called them up for a quote that they all have Russian accents and are full of lies.

Thanks for calling me a moron, but can you please show me a trace route to them that does not go through Cogent?

Bash... I'm a little busy right now making sure my customers are happy, and not with just restoration...

You on the other hand, I will get back to. I know who you are, stop taking this too far. It's sad that you have nothing to do all day besides bashing your competitor, and we don't even consider you one. Please, just let it go, because me and you have been done about a year ago.

Are they DOWN or just slow?

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Sprung | % Verlust | IP-Adresse | Bezeichnung der Zwischenstation | Lage | Zeitzone | ms | Grafik | Netzwerk |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 212.254.207.15 | noc.bboxbbs.ch | - | | | | Buemplizer Box |
| 1 | | 212.254.207.1 | router-bb-bern2.bboxbbs.ch | Bern, Switzerland | +01:00 | 0 | x | Buemplizer Box |
| 2 | | 212.254.206.1 | router-bb-bern1.bboxbbs.ch | Bern, Switzerland | +01:00 | 0 | x | Buemplizer Box |
| 3 | | 212.254.255.130 | be-core-02.tiscali.ch | ?(Switzerland) | +01:00 | 5 | x--- | DataComm (Schweiz) AG |
| 4 | | 212.254.255.214 | glatt-core-02-se12-0-0.tiscali.ch | ?(Switzerland) | +01:00 | 11 | x-- | DataComm (Schweiz) AG |
| 5 | | 213.200.70.1 | pos-2-0.zur10.ip.tiscali.net | ?(Germany) | +01:00 | 14 | x--- | Nacamar Data Communications GmbH |
| 6 | | 213.200.82.105 | so-1-0-0.bsl10.ip.tiscali.net | ?(Germany) | +01:00 | 11 | x- | Nacamar Data Communications GmbH |
| 7 | | 213.200.82.101 | so-5-0-0.fra30.ip.tiscali.net | ?(Germany) | +01:00 | 17 | -x | Nacamar Data Communications GmbH |
| 8 | | 213.200.81.201 | so-7-1-0.nyc30.ip.tiscali.net | ?(Germany) | +01:00 | 90 | x | Tiscali International Network B.V. |
| 9 | | 213.200.82.129 | so-5-2-0.nyc10.ip.tiscali.net | ?(Germany) | +01:00 | 90 | x | Tiscali International Network B.V. |
| 10 | | 213.200.82.165 | so-0-2-0.was10.ip.tiscali.net | ?(Germany) | +01:00 | 100 | x | Tiscali International Network B.V. |
| 11 | | 213.200.66.66 | qwest-ic-was.ip.tiscali.net | ?(Germany) | +01:00 | 107 | -x | Tiscali International Network B.V. |
| 12 | | 205.171.9.13 | dca-core-01.inet.qwest.net | Washington, DC, USA | -05:00 | 100 | x- | Colorado SuperNet, Inc. CSN-BLOCK-7 |
| 13 | | 205.171.9.10 | dca-core-03.inet.qwest.net | Washington, DC, USA | -05:00 | 100 | x- | Colorado SuperNet, Inc. CSN-BLOCK-7 |
| 14 | | 205.171.8.217 | jfk-core-03.inet.qwest.net | New York, NY, USA | -05:00 | 109 | -x- | Colorado SuperNet, Inc. CSN-BLOCK-7 |
| 15 | | 205.171.30.114 | jfk-edge-04.inet.qwest.net | New York, NY, USA | -05:00 | 110 | x- | Colorado Supernet, Inc. |
| 16 | | 65.112.96.98 | - | ... | | 110 | x- | Qwest Communications JFK-WAN-65-112-96 |
| 17 | | 64.61.0.73 | 000-073.np1.net | ?Randolph, MA 02368 | | 117 | -x | InfoHouse, Inc. INFOHOUSE-BLK |
| 18 | | 64.61.1.173 | 001-173.np1.net | ?Randolph, MA 02368 | | 118 | -x | InfoHouse, Inc. INFOHOUSE-BLK |
| 19 | | 64.61.24.150 | 024-150.colo.ny.np1.net | ?Randolph, MA 02368 | | 119 | -x- | InfoHouse, Inc. INFOHOUSE-BLK |
| 20 | | 66.181.170.170 | likewhoa.com | ?Brooklyn, NY 11230 | | 125 | -x- | Like Whoa Inc LIKEWHOA |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

bash-2.03$ date
Thu Sep 12 11:45:28 PDT 2002
bash-2.03$ traceroute 66.181.170.170
traceroute to 66.181.170.170 (66.181.170.170), 30 hops max, 40 byte packets
1 norcal.oc192.2.xfrnetworks.com (63.146.168.2) 0.529 ms 0.337 ms 0.268 ms
2 cntr-02.jsv.qwest.net (66.77.106.137) 0.256 ms 0.240 ms 0.179 ms
3 205.171.14.5 (205.171.14.5) 8.441 ms 0.416 ms 0.335 ms
4 svl-core-02.inet.qwest.net (205.171.14.125) 0.594 ms 0.592 ms 0.704 ms
5 205.171.8.201 (205.171.8.201) 72.657 ms 73.085 ms 72.730 ms
6 205.171.9.10 (205.171.9.10) 72.655 ms 72.653 ms 72.680 ms
7 205.171.8.217 (205.171.8.217) 69.842 ms 69.859 ms 69.854 ms
8 205.171.30.114 (205.171.30.114) 69.860 ms 69.860 ms 69.875 ms
9 65.112.96.98 (65.112.96.98) 76.556 ms 76.696 ms 76.707 ms
10 000-073.np1.net (64.61.0.73) 82.212 ms 81.799 ms 81.703 ms
11 001-173.np1.net (64.61.1.173) 82.201 ms 82.290 ms 81.860 ms
12 024-150.colo.ny.np1.net (64.61.24.150) 82.486 ms 82.684 ms 82.550 ms
13 ns2.likewhoa.com (66.181.170.170) 81.775 ms 82.043 ms 82.954 ms
bash-2.03$

F:\>tracert likewhoa.com

Tracing route to likewhoa.com [66.181.170.170]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms CL [192.168.0.1]
2 30 ms 20 ms 20 ms boanxx4.ip.tele.dk [195.249.0.116]
3 20 ms 20 ms 30 ms ge-0-2-1-2.1000M.boanxu1.ip.tele.dk [195.249.14.
219]
4 20 ms 20 ms 20 ms pos7-0.2488M.boanxg2.ip.tele.dk [195.249.4.254]

5 30 ms 20 ms 30 ms pos6-0.2488M.albnxg1.ip.tele.dk [195.249.2.37]
6 30 ms 40 ms 30 ms so-0-3-0.br1.CPH1.gblx.net [62.12.33.77]
7 60 ms 50 ms 50 ms pos5-0-622M.cr2.CPH1.gblx.net [62.12.32.61]
8 121 ms 110 ms 110 ms pos1-0-622M.cr2.NYC2.gblx.net [206.132.249.170]

9 120 ms 111 ms 120 ms pos1-0-2488M.br2.NYC2.gblx.net [208.48.234.214]

10 110 ms 120 ms 110 ms 208.51.134.2
11 110 ms 111 ms 120 ms jfk-core-02.inet.qwest.net [205.171.30.17]
12 110 ms 120 ms 121 ms jfk-edge-04.inet.qwest.net [205.171.30.110]
13 120 ms 120 ms 120 ms 65.112.96.98
14 130 ms 120 ms 131 ms 000-073.np1.net [64.61.0.73]
15 130 ms 120 ms 130 ms 001-173.np1.net [64.61.1.173]
16 130 ms 130 ms 130 ms 024-150.colo.ny.np1.net [64.61.24.150]
17 130 ms 130 ms 120 ms ns2.likewhoa.com [66.181.170.170]

Trace complete.

I am sitting on Verio in the Midwest:

13 64.61.0.73 40ms 40ms 50ms TTL: 0 (000-073.np1.net bogus rDNS: host not found [authoritative])
14 64.61.1.173 41ms 50ms 40ms TTL: 0 (001-173.np1.net bogus rDNS: host not found [authoritative])
15 66.28.20.70 50ms 40ms 50ms TTL: 0 (Global_Net_Advertising.demarc.cogentco.com bogus rDNS: host not found [authoritative])
16 66.181.170.170 40ms 50ms 40ms TTL:238 (ns2.likewhoa.com ok)

OK well I have never been a customer of Like Whoa, but I have seen many decent sites host with them, so they must be ok for the most part. But reading all of the recent threads lately about their aggressive email and icq spam tactics, and now the Longest downtime of any host in a very long time, and the switching from teir1 to cogent bandwidth, this leads me to believe that they are not very stable. Some people have brought up some very valid points on this thread, not just about Like WhoHa, but about any host. If your host was getting a bad rep for being spammers, and then was down over 15 hours, then switched from teir1 bandwidth to cogent....well wouldnt you be pissed, and consider getting out while you still had the chance and your sites were not completely wiped out???

i suspect we'll see another official announcement of what is going on soon enough..

its not easy moving to another host,,

if everyone jumped ship when their host has problems then everyone would be changing at least 5 times a year,

Hmm. Does Cogent know you say this about them? Prolly dont wanna use carriers that you say suck. One only has to look at the former hosting.fm (and yes they were Cogents LARGEST customer at one point)to realize that if Cogent decides they dont like you, they will boot you faster than you can say shit.


I'd find an alt real fast =)

Actually, I remember another company (a MAJOR adult specialty hosting company) that was down for a couple days. This was within the last year.

Technically Cogent IS in fact a Tier 1 Provider. And it's been surprisingly good.

Any you don't get to be the size of Whoa by ripping people off, and when you get that big people are going to talk about you very critically. Bear in mind, they are also a large adult internet company, and when their lines are down they are losing sales themselves. They have had the Cogent lines in their facility since I started hosting there and they have always kept it completely separate. I'm glad they have it there as backup and it seems to be working reasonably well now.

Life goes on. I've had worse outages - my worst was three days dead in Vegas on UUNet. To this day I avoid anything Worldcom.

from route-views.oregon-ix.net

Tracing the route to ns2.likewhoa.com (66.181.170.170)

1 nero-gw.oregon-ix.net (198.32.162.2) 0 msec 0 msec 0 msec
2 eugn-core1-gw.nero.net (207.98.64.162) [AS 3701] 4 msec 0 msec 0 msec
3 aar1-serial4-0-0.SantaClara.cw.net (208.172.151.1) [AS 3561] 12 msec 12 msec
12 msec
4 agr2-loopback.SantaClara.cw.net (208.172.146.102) [AS 3561] 12 msec 16 msec
12 msec
5 dcr2-so-7-1-0.SantaClara.cw.net (208.172.156.185) [AS 3561] 12 msec 12 msec
12 msec
6 agr4-so-2-0-0.SantaClara.cw.net (208.172.156.142) [AS 3561] 12 msec 16 msec
agr4-so-6-0-0.SantaClara.cw.net (208.172.156.158) [AS 3561] 16 msec
7 acr1-loopback.SanFrancisco.cw.net (206.24.210.61) [AS 3561] 16 msec 16 msec
16 msec
8 cable-and-wireless-peering.SanFrancisco.cw.net (206.24.211.226) [AS 3561] 20
msec 16 msec 16 msec
9 svl-core-03.inet.qwest.net (205.171.14.162) [AS 209] 20 msec 20 msec 16 msec
10 svl-core-02.inet.qwest.net (205.171.14.125) [AS 209] 24 msec 12 msec 16 msec
11 dca-core-01.inet.qwest.net (205.171.8.201) [AS 209] 88 msec 88 msec 84 msec
12 dca-core-03.inet.qwest.net (205.171.9.10) [AS 209] 92 msec 88 msec 88 msec
13 jfk-core-03.inet.qwest.net (205.171.8.217) [AS 209] 92 msec 84 msec 84 msec
14 jfk-edge-04.inet.qwest.net (205.171.30.114) [AS 209] 88 msec 88 msec 88 msec
15 65.112.96.98 [AS 209] 92 msec 92 msec 92 msec
16 000-073.np1.net (64.61.0.73) [AS 11846] 92 msec 92 msec 96 msec
17 001-173.np1.net (64.61.1.173) [AS 11846] 92 msec 92 msec 92 msec
:BangBang: 18 Global_Net_Advertising.demarc.cogentco.com (66.28.20.70) [AS 16631] 100 msec
96 msec 100 msec
19 ns2.likewhoa.com (66.181.170.170) [AS 21790] 100 msec 96 msec 100 msec
route-views.oregon-ix.net>

NOTE: Hop 18.

Rik

...if you know how to use Source routing, you will see that while Likewhoa is currently not _showing_ Cogent as the inbound route, Cogent is definitely handling a chunk of their outbound.

For paths from likewhoa to Level3 for example, probably others.

(Not a comment on whether this is a good thing or not, but it clearly looks like a business issue with LikeWhoa/Verio and not a technical or BGP problem)

Rik

you're a bunch of crybabies..