how-to block ads
|
 Review by tcp1 
UPDATED: 1.5 years ago
member for 9.6 years, 431 visits, last login: 129 days ago
 Reston,Fairfax,VA
 Contract price not specified.
 "Communicative, very accommodating, straightforward.."
 "Not their fault, but coordinating with Qwest AND Verizon can be a problem."
 "Good deal for NxT1 service, successful install"
| |
11/20/2007
========
This line has been up and *solid* ever since we started it, and I left the company at this time in November, so such ends my experience with bandwidth.com.
Their service monitoring was great - even when we had a power blip at our location and the router cycled, we'd get a call. They monitored for SMTP open relays, and helped us work that out as well.
Overall, their folks are very knowledgeable, very accessible, and a big point for me - they FOLLOW UP! They actually call back when they say they will!
HIGHLY recommended.
9/17/06
======
This is for a business order.. We decided to put in two bonded T1s (NxT1 over multilink PPP - 3.0mbps) at our new business location.
Bandwidth.com gave the best price (about $850) for two T1s (bonded), offered through Qwest.
If you've ever had a T1 installed, you know how tough it is when you're getting all the pieces together. In this case, we had three players:
1. Bandwidth.com - SLA provider, broker / contractor.
2. Qwest - Network provider / ISP
3. Verizon - "Last Mile" line provider.
(4. Me - getting the router configured correctly!)
Surprsingly, everything went pretty well. Sales reps are very friendly. Install reps are very friendly, as are tech support reps! Also very knowledgeable.
About 35 days from order date until full install - and part of that was a delay that was our fault. (We ordered the wrong WIC cards - Cisco V2's vs V1s.)
The only problem is that we had requested that the demarc be extended from the basement to the 6th floor.. Apparently this didn't get transfered from Bandwidth to Qwest to Verizon. No surprise, and they came out early the next week to fix it -- but really since we are Bandwidth.com's customer, they should have been the ones to own up to this and not blame Qwest and Verizon. Granted, they did get it all taken care of eventually.
The service seems reliable and robust. I'd give the experience an 8/10.
Update 4/17/06
============
Update: I have no complaints at all about the actual bandwidth.com service after this time.. (It's actually a Qwest T1). However, the only issue I've had is that they're pretty quick to pull the trigger on abuse tickets for anything "weird" they see on the network.
I'm not sure if this is related to Qwest, but the tickets come through and we deal with the bandwidth.com abuse department.
We do a lot of experimental stuff where I work, and it seems whenever we have anything that opens a standard port related to e-mail (25, 110, etc) we get an abuse report accusing us of being a spam relay.
We don't run any e-mail servers, and we run in a secure environment - we're a DoD contractor and our boxes are locked down. We DO run services that sometimes communicate via SMTP, but they are NOT open relays or public mail servers.
The bandwidth.com guys are always very helpful and understanding, and I think it's just their policy to pass on anything they receive as an abuse report. So far, most of the reports have been from Spamhaus or CAUCE or other "grassroots" anti-spam organizations.. While I believe they have the best intentions at heart, talk to any admin - and you'll know that sometimes these organizations can get a little "vigilante" and aggressive in reporting open relays and dropping whole IP blocks because of suspicion. Can't say I blame them given problems with spam, but they also don't listen to reason and you can't fight them - and too many places use their lists blindly.
(Our bandwidth guys, off the record, also echoed this sentiment.)
Usually, all that's required is us to talk to their tech guys, explain that no, we aren't running an open relay on port 21 - yes, what we're running might be a little "weird", but it's not sending spam (as we can show from our firewall traffic logs) - and that ends the issue.
I don't think this is a bandwidth.com issue per se, but I think we could save a lot of aggravation if they'd take notes about our 'special case' once in a while.
Other than that, service has been rock solid and customer service top notch.
Followup comments: | Forums » comments on review of Bandwidth.com |
|
|
·
·
·
·