So apparently my sales rep is telling me cogent will not give me a second circuit for a redundent line so in other words, no vrrp or hsrp nothing Unless! i purchase another 200mb contract with them.
Anyone else ever have this problem?
not even are they willing to do a port fee for the second gbic i'd take up.
I am having a strange DNS issue on a Cogent circuit using Cogent DNS servers at 66.28.0.45 and 66.28.0.61. What is happening is that some domain requests will timeout the first try. Then subsequent tries will be quick with no timeouts.
I am having a very hard time getting through to Cogent that there might be an issue somewhere and I was wondering if anyone on a Cogent line using the same Cogent DNS servers could also do a test for me to and see if you can reproduce any timeouts.
How I am testing:
- Open nslookup (in linux use: nslookup -timeout=2, windows defaults to 2 seconds)
- Picking a random domain name (favorite cereal.com, movie title.com, brand name.com, random word.com)
- Repeating test for same domain if timeout occurs to see the next query resolve instantly
Here is an example of what Is happening for me:
Code:
[eger@womp ~]# nslookup -timeout=2
> superman.com
;; connection timed out; no servers could be reached
> superman.com
Server: 66.28.0.45
Address: 66.28.0.45#53
Non-authoritative answer:
Name: superman.com
Address: 64.12.47.7
> napaautoparts.com
;; connection timed out; no servers could be reached
> napaautoparts.com
Server: 66.28.0.45
Address: 66.28.0.45#53
Non-authoritative answer:
Name: napaautoparts.com
Address: 208.254.241.70
>
I picked 2 random domains (that were likely not cached at the name server) and they both timeout the first try. Anyone else able to replicate this?
This is something I've been thinking about a lot lately, and I'd like to hear what others have to say.
I'd like to keep one copy of each website on a different server - far away from each other, maybe different hosting providers, and be able to use managed DNS to switch between the two in case of an outage.
The sites could easily be backed up daily to the other host, but for databases that get updated frequently (like forums), what is the solution to this?
So the rule of thumb is if you have a 30A circuit to not exceed 80% or 24A.
If I buy a 30A circuit, I am assuming it is protected by a circuit breaker that is 30A, correct?
In *theory* we could run 29-30A all day and be fine.
So, I understand, the rule of 80% to be to the effect that "during startup, equipment uses more power ... or during runtime if it heats up, the fans go faster using more power" so it is safe to be at 24A in case you get spikes to 27-29A.
Is my reasoning correct?
Further, if you run primary/redundant circuits, is there really harm in running 13A on one circuit and 14A on the other.. and in the unlikely event of a failure, you are running 27A on one circuit (at 90% instead of 80%).
Any thoughts on this? Getting an extra 3A out of a 208V circuits is like putting in 3-4 more servers. If someone is doing this please let me know. I think it would work fine but i would like to know from the experts that do the colo stuff for a living what problems i could encounter, if any.
If you had to deciede between one of the two lowest wholesale providers, which would you choose and why?
View 14 Replies View RelatedWe are nearing the end of our contract with cogent and are deciding whether to continue with them. Bandcon has recently (within a last year or so) established its presence in NYC metro area.
Who would you choose among the two? Please give your input and evaluation of the two networks.
Have 2 questions
1. How about the quality of Cogent in Seattle?
2. Where can I buy Cogent there? Looking for 100mbps commit
Is colocating with Cogent practical decision.
They offer 10 or 100 Mbps connection
Requires a year contract for full rack.
Question is how does their service, network and bandwidth do compared to other DC/providers?
For those who use (or have used) their colocation service, what kind of feedback can you give?
We are considering colocating with them.
if I rented a half, or full cabinet for colocation. And would wanted Cogent was my isp for the cabinet how much do they charge?
Days they take to setup?
Costs to setup? (Setup fee?)
I know their pricing 100Mbps for $1,000 which is pretty crazy deal. And if I would go on their contract would it save me a setup fee?
i want to know any datacenter that offer 10 Mb or 100Mb port unmetered cogent bandwidth.
Do you know any?
It is for an image hosting file service.
I am sure people have been in contact with Cogent regarding connectivity...
They gave me a price for a 100 Megabit and a 1 Gigabit connection. So I wanted to see what people were quoted by Cogent.
He claims they have re-structured their entire business over the past 12 months.
He quoted $10/Megabit... How does this compare to anyone else?
Also is even getting a connection thru Cogent worth it?
I have been using Cogent for many years and have always been pretty pleased with the service and bandwidth (I know many consider bottom rate/budget bandwidth). I would usually be able to call in and speak with someone who could check routing, login to switches to verify port settings, and make reverse DNS changes right then and there.
Within the last 6 months though I have been getting pretty poor support from them. Seems they are hiring more and more people just to be able to answer phones. The techs seem to have a hard time comprehending even simple reverse DNS requests and always ask me to hold for extended periods of time.
Today I called in and was even asked to hold right as they picked up the phone!! I mean, if your just going to pick up to ask me to hold, why pick up in the first place until you are ready?
I am considering getting a server from take2hosting.com. Their offer is great and sales has been very helpful and fast. Left definitely a good impression.
The downside is that they are on Cogent-only bandwidth. In the past I have really gotten something against Cogent, mainly due to one of my FDC servers being routed over Cogent and only pulling 10K/sec to Europe.
How is the Cogent network nowadays? Has it improved since a year ago? Worth considering?
From my tests the speeds are actually really great. They are located in San Jose, and I am testing speeds to Europe. For example to Surfnet Amsterdam (Cogent hands off the traffic to Surfnet in Amsterdam, so its on the Cogent network all the way) I am able to pull 2.53MB/sec. This is an incredible speed for a Westcoast<->Europe transfer. It almost makes me believe Cogent has started getting its act together.
For people who would like to test speeds, please use this test file. Especially European tests would be interesting, and it would be great if you could post where cogent hands off traffic from LosAngeles to either your network or a transit network. (In the US or Europe)
Right now I am hosting on a Level3/GlobalCrossing network @ the eastcoast. This works really well but it shows in the price. If I could combine a couple of budget boxes into one of those Quadcores it would save quite a lot. Question is: Is Cogent trustworty nowadays?
Thanks for your input
Ps. I know that hosting on a single-homed network is not the smartest thing to do. However they will add more carriers soon so this will not really be an issue. I'm expecting them to not drop Cogent tho, so my question remains
Is there anyone here using Cogent network at Colo4Dallas? I have a request for file transfer hosting, dont need premium network.
View 14 Replies View RelatedAnyone using a Cogent colocation at Marina Del Rey, CA that would care to share their experience (good or bad).
Any gotchas that we should consider ?
Considering getting a single cabinet at that location and am interested in quality and reliability of network and facilities. We rarely use remote hands so that is not much of an issue.
We use Cogent at our colo, and since this Monday (8/13/07) we've been gettin dozens of complaints from AOL users stating that connections to our sites are very, very slow and often time out.
We tested from an AOL session and were able to confirm this. We found this odd, because it came out of the blue and nothing had changed on our end. We also get excellent all-around performance from other (non AOL) connections, be it dialup or broadband.
We went ahead and did a bunch of traceroutes on the AOL session. We found things get bogged down as soon as it hits Cogent's routers in DC (timeouts / no response). These AOL sessions have no problems whatsoever with other sites and other (non cogent hosted sites) loaded fast and without issue. We then tested loading Cogent's own web site from the AOL session and saw the same sluggishness as well. The same happened when we tested a couple other Cogent client sites from AOL. They all pulled very slow (10 to 35+ secs per page) on an AOL/DSL session. This did not happen on the same broadband connection w/out AOL running on top of it. The same pages loaded very fast.
Just wondering if other Cogent clients are experiencing this? :? We have not heard from them about this, but wanted to know if this is something isolated or not.
there is anyone out there who has their infrastructure colocated in cogent owned datacenter. And how stable and secure is it. The only reason i m interested in Cogent owned colo is that they provide solid SLA.
View 14 Replies View RelatedCould you guys look and see if what I am seeing is right? They offer Global Crossing and Cogent officially. So if I use GLBX looking glass, I get this.
Trying trace from node 'Miami, FL, US' to '96.31.73.xxx'
1 64.214.16.65 (64.214.16.65) 0.761 ms 0.608 ms
2 so0-0-0-2488M.ar2.TPA1.gblx.net (67.17.66.165) 5.690 ms 5.695 ms
3 WBS-CONNECT-LLC.ae0.409.ar2.TPA1.gblx.net (64.214.147.222) 5.731 ms 5.880 ms
4 69.46.31.106 (69.46.31.106) 7.442 ms 6.667 ms
5 node1.sarorahosting.com (96.31.73.2) 15.734 ms 15.993 ms
6 96.31.73.xxx (96.31.73.xxx) 15.861 ms 15.795 ms
Now if I tracert from the VPS to the GLBX router, I get this.
traceroute to 64.214.16.65 (64.214.16.65), 30 hops max, 40 byte packets
1 node1.sarorahosting.com (96.31.73.2) 0.072 ms 0.035 ms 0.008 ms
2 69.46.31.105 (69.46.31.105) 0.731 ms 0.863 ms 1.003 ms
3 gi0-6.na21.b001841-0.tpa01.atlas.cogentco.com (38.99.204.33) 1.147 ms 1.142 ms 1.428 ms
4 gi4-1.core01.tpa01.atlas.cogentco.com (38.20.33.89) 0.818 ms 0.814 ms 0.807 ms
5 po2-0.core01.mco01.atlas.cogentco.com (154.54.27.90) 148.004 ms * *
6 po5-0.core01.jax01.atlas.cogentco.com (66.28.4.146) 5.847 ms 5.839 ms 5.872 ms
7 po5-0.core01.atl01.atlas.cogentco.com (154.54.3.197) 11.953 ms 23.819 ms 23.870 ms
8 te3-3.ccr01.atl01.atlas.cogentco.com (154.54.5.38) 11.721 ms 11.752 ms 11.787 ms
9 te8-2.mpd01.atl04.atlas.cogentco.com (154.54.3.174) 11.962 ms 11.921 ms 11.987 ms
10 ge4-1-0-390-1000M.ar4.ATL1.gblx.net (64.208.110.97) 12.252 ms 12.359 ms 12.444 ms
11 64.214.16.65 (64.214.16.65) 16.026 ms 16.061 ms 16.594 ms
Now what would be causing this to happen?
how much per mbps is the norm, assuming we're ordering 50+?
what about non-cogent?
if you can share a 100MB download link that I can use to test cogent's speed to my network. Hopefully plugged into a 100MBPS port at the switch to see if it will max out or not.
View 6 Replies View Related