how-to block ads
|
»next review in page
Review by Mongoose46 
Posted: 1 year ago
member for 1 year, 1 visits, last login: 1 year ago
 Simpsonville,Greenville,SC
 Contract price not specified.
 "None"
 "Horrible internet service anywhere"
 "Avoid like the plague"
| Pre Sales information:
Install Co-ordination:
Connection reliability:
Tech Support:
Services:
Value for money:
|
I've compiled a huge report of complaints against Pavlov media and will be working to bring this before Mark Scifres himself, the owner of Pavlov media. If anyone would like to support this, please email me at noxthox@hotmail.com or add me on MSN.
Followup comments: | Forums » comments on review of Pavlov Media |
 | »next review in page (previous review)
Review by Leyth
Posted: 1.7 years ago
member for 1.7 years, 5 visits, last login: 1.6 years ago
Central,Pickens,SC
Contract price not specified.
"Fast internet when you're the only one in the apartment using it"
"EVERYTHING"
"Save yourself the money and get dialup, or save yourself the trouble and use a different ISP"
| Pre Sales information:
Install Co-ordination:
Connection reliability:
Tech Support:
Services:
Value for money:
|
Everyone's reviews are negative and my experience with pavlov wasn't very good either. I figured I would try to contact them and attempt to make some progress with them before I write a review.
First when I moved everyone had a 5.0mbit cap. The internet was practically non-existant during peak hours but nice and fast when not alot of people in the apartment complex was on. Football games, vacations, and weekends helped the internet out. I think they realized the problem and then limited everyone to 750kb/s. In my opinion, that was a great idea and with the bandwidth split up it should let everyone have a stable internet connection. Then the packetloss began. I take a few classes online when I can and I also like to watch and listen to video's and music off of youtube. I game sometimes as well. While doing homework or taking exams the internet would randomly disconnect like every 10 minutes. I've gotten screwed over on 1 exam because of this because the internet would not come back and i ran out of time on an exam i only had 1 attempt for. Pretty rediculous, I constantly have to redo homework because of this connection.
I am a computer technician so i have a good bit of experience with computers and networking. I contacted them letting them know of my knowledge and the issues i'm experiencing. Either way they wanted some test logs for proof. So i ran packetloss tests on the servers they wanted me to run, and it clearly showed packet loss and connection just hanging up. They told me this was an issue at my entire site and they were working on it. That was 3 weeks ago, i sent 1 email back trying to find out if they have been able to address the problem and no reply. I've talked to these guys on the phone before and its a painful process, because these guys are reading right off a sheet of instructions with possibly no technical computer experience. I'm going into the office tommorrow to speak with the management and see if I can talk them into looking into a better solution in providing internet to the apartment complex, or if i have any other choices for ISP in the area.
Followup comments:  snowfright
join:2008-01-22
Douglas, GA |  Food for thought.
| |
| | Leyth
join:2008-02-18
Simpsonville, SC
 ·Pavlov Media
1 edit | Re: Food for thought. I've called many times, nothing ever comes out of it except 'we're working on it.'
here is something that they are 'working on'
Pinging www.l.google.com [64.233.167.104] with 32 bytes of data:
Reply from 64.233.167.104: bytes=32 time=259ms TTL=243
Reply from 64.233.167.104: bytes=32 time=322ms TTL=243
Reply from 64.233.167.104: bytes=32 time=111ms TTL=243
Reply from 64.233.167.104: bytes=32 time=622ms TTL=243
Reply from 64.233.167.104: bytes=32 time=900ms TTL=243
Reply from 64.233.167.104: bytes=32 time=630ms TTL=243
Reply from 64.233.167.104: bytes=32 time=891ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1121ms TTL=243
Reply from 64.233.167.104: bytes=32 time=749ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1047ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1067ms TTL=243
Reply from 64.233.167.104: bytes=32 time=655ms TTL=243
Reply from 64.233.167.104: bytes=32 time=951ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1148ms TTL=243
Reply from 64.233.167.104: bytes=32 time=750ms TTL=243
Reply from 64.233.167.104: bytes=32 time=936ms TTL=243
Reply from 64.233.167.104: bytes=32 time=683ms TTL=243
Reply from 64.233.167.104: bytes=32 time=275ms TTL=243
Reply from 64.233.167.104: bytes=32 time=302ms TTL=243
Reply from 64.233.167.104: bytes=32 time=526ms TTL=243
Reply from 64.233.167.104: bytes=32 time=433ms TTL=243
Reply from 64.233.167.104: bytes=32 time=642ms TTL=243
Reply from 64.233.167.104: bytes=32 time=844ms TTL=243
Reply from 64.233.167.104: bytes=32 time=696ms TTL=243
Reply from 64.233.167.104: bytes=32 time=724ms TTL=243
Reply from 64.233.167.104: bytes=32 time=768ms TTL=243
Reply from 64.233.167.104: bytes=32 time=912ms TTL=243
Reply from 64.233.167.104: bytes=32 time=978ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1001ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1120ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1200ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1095ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1140ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1146ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1137ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1080ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1111ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1077ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1087ms TTL=243
Reply from 64.233.167.104: bytes=32 time=1120ms TTL=243
Ping statistics for 64.233.167.104:
Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 1200ms, Average = 831ms
Pinging www.yahoo-ht3.akadns.net [69.147.114.210] with 32 bytes of data:
Reply from 69.147.114.210: bytes=32 time=849ms TTL=52
Request timed out.
Reply from 69.147.114.210: bytes=32 time=991ms TTL=52
Reply from 69.147.114.210: bytes=32 time=878ms TTL=52
Reply from 69.147.114.210: bytes=32 time=447ms TTL=52
Request timed out.
Reply from 69.147.114.210: bytes=32 time=683ms TTL=52
Request timed out.
Request timed out.
Reply from 69.147.114.210: bytes=32 time=1135ms TTL=52
Reply from 69.147.114.210: bytes=32 time=1346ms TTL=52
Reply from 69.147.114.210: bytes=32 time=1176ms TTL=52
Request timed out.
Reply from 69.147.114.210: bytes=32 time=1164ms TTL=52
Request timed out.
Request timed out.
Reply from 69.147.114.210: bytes=32 time=738ms TTL=52
Reply from 69.147.114.210: bytes=32 time=794ms TTL=52
Reply from 69.147.114.210: bytes=32 time=782ms TTL=52
Reply from 69.147.114.210: bytes=32 time=952ms TTL=52
Reply from 69.147.114.210: bytes=32 time=868ms TTL=52
Reply from 69.147.114.210: bytes=32 time=905ms TTL=52
Reply from 69.147.114.210: bytes=32 time=980ms TTL=52
Reply from 69.147.114.210: bytes=32 time=1059ms TTL=52
Reply from 69.147.114.210: bytes=32 time=1102ms TTL=52
Reply from 69.147.114.210: bytes=32 time=886ms TTL=52
Reply from 69.147.114.210: bytes=32 time=549ms TTL=52
Reply from 69.147.114.210: bytes=32 time=288ms TTL=52
Reply from 69.147.114.210: bytes=32 time=603ms TTL=52
Reply from 69.147.114.210: bytes=32 time=713ms TTL=52
Reply from 69.147.114.210: bytes=32 time=718ms TTL=52
Reply from 69.147.114.210: bytes=32 time=354ms TTL=52
Reply from 69.147.114.210: bytes=32 time=218ms TTL=52
Reply from 69.147.114.210: bytes=32 time=467ms TTL=52
Reply from 69.147.114.210: bytes=32 time=675ms TTL=52
Reply from 69.147.114.210: bytes=32 time=828ms TTL=52
Reply from 69.147.114.210: bytes=32 time=909ms TTL=52
Reply from 69.147.114.210: bytes=32 time=921ms TTL=52
Reply from 69.147.114.210: bytes=32 time=1056ms TTL=52
Reply from 69.147.114.210: bytes=32 time=1136ms TTL=52
Ping statistics for 69.147.114.210:
Packets: Sent = 40, Received = 33, Lost = 7 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 218ms, Maximum = 1346ms, Average = 823ms | |
| 
pavlov sucks dK
@pavlovmedia.com
| I hate pavlov media If at all possible, never get pavlov media as a service provider. Not only does all of their services suck, when you try and talk to someone on the phone you get some poonjab on the other side of the world who has never seen an hdtv or wireless internet devices. They read how to guides off of a computer and have no clue about the actual problem. You can never get an actual technician on the phone nor do they care to fix your problem. AVOID PAVLOV AT ALL COSTS!!! | |
| | | |
| Forums » comments on review of Pavlov Media |
| »next review in page (previous review)
Review by chaser324
UPDATED: 1.7 years ago
member for 1.7 years, 8 visits, last login: 2 days ago
Central,Pickens,SC
Contract price not specified.
"Just slightly better than no internet connection at all."
"A failure in virtually every way."
"Avoid at all costs!!"
| Pre Sales information:
Install Co-ordination:
Connection reliability:
Tech Support:
Services:
Value for money:
|
I just want to say that I agree with pretty much all of the other reviews made about Pavlov. I'm living at University Village (Clemson, SC), and they have a contract with Pavlov Media to provide internet service for the entire apartment complex. From the very first day I moved in here, I've had problems.
Lag spikes are a massive problem all day, every day. I would say every 5-10 minutes you are guaranteed to get at least one noticeable spike in the lag. This makes online gaming virtually impossible. Everything will seem fine for a while, and then...the lag comes...and it always comes. This problem carries over into just regular internet surfing as well though. You'll just be looking at stuff online and then all of a sudden everything will come to a screeching halt for a minute or more.
At least once a week you're also pretty much guaranteed to completely lose internet access for a couple of hours. I'm not really sure why, but it seems to always happen. On at least a couple of occasions in the past year, there were times when internet access would be unavailable for an entire day or more. There was also two entire weeks where the connection quality was such complete crap that it may as well have been dead.
As far as download speeds, that's been a variable thing. From the time I moved in up until a few months ago it was pretty much always the case that during high traffic times you would get download bandwidth somewhere in the neighborhood of 200-300 kbps. Unacceptably slow. However during lower traffic times I could get 4-5 Mbps. There was a "fair-share" system in place that was supposed to give less priority to your connection if you downloaded over 500 MB in a 24 hour period, but it didn't really seem to have any real effect. A couple of months ago though the entire situation seems to have changed. It would appear to me that some sort of cap has been placed on downloads that never allow them to get over 1 Mbps. My download speed now tends to always float at right around 600-700 kbps sometimes jumping up to 800-900 kbps during low traffic times. I guess maybe I should be happy about the improved consistency...but I'm not really...it should still be better than this.
As far as customer service...there isn't any real "service". There was one time when I tried interfacing with their customer support (during the two week period mentioned previously where the internet was virtually inaccessible), and this is pretty much how it went. I send an initial e-mail with a thorough explanation of the situation along with the piles of information that they request (pings, traceroutes, various internet bandwidth tests, etc.). A few days later I get a reply that says they aren't aware of any current quality issues in my area, and that in order for them to further assist me I need to answer an entire page or more of general questions. So I begrudgingly answer all of the additional questions that they sent me. I wait an entire week, and never hear any sort of reply. I e-mail them once again. The reply the next day with an e-mail saying that they were sorry for the delay, they are now aware that there is an issue and they are investigating it. A few days later, I get an e-mail from one of the apartment complex admins that the issue has been resolved...and I suppose it was...the internet quality had returned to its previous level of crappiness.
Also one additional complaint I would like to put forth (this one is rather small in comparison to the others) is that I hate ISPs that have these stupid registration web pages that you are forced to view the first time you try to connect a new device. At the very least, if you are going to do this, provide me with an easy way to register additional MAC addresses so that I can easily register devices that don't have a web browser (XBox, PS3, etc.).
Followup comments: | Forums » comments on review of Pavlov Media |
| »next review in page (previous review)
Review by darkking
Posted: 2.1 years ago
member for 7.7 years, 49 visits, last login: 38 days ago
Jacksonville,Duval,FL
Contract price not specified.
"I would have to make them up"
"UnFREAKING bearable,ive seen dialup faster"
"UTTER %$&* of a CO. I Hope they go down in flames"
| Pre Sales information:
Install Co-ordination:
Connection reliability:
Tech Support:
Services:
Value for money:
|
promised 3m/768, current..today and they day before and the day before that... 185/600
They pass the buck with excuses,they lie or they just do nothing
Ive given them traceroutes,speedtests and more...NO results
I'm in a new Development and im rallying all the neighbors to get them kicked and replaced with a cable service.
I hope YOU dont choose them....
Followup comments: | Forums » comments on review of Pavlov Media |
| »next review in page (previous review)
Review by Shripe
Posted: 2.5 years ago
member for 2.5 years, 7 visits, last login: 1.3 years ago
Madison,Dane,WI
Contract price not specified.
"None"
"Frequent downtime, horrible service"
"Bigger, local companies are better than this crap"
| Pre Sales information:
Install Co-ordination:
Connection reliability:
Tech Support:
Services:
Value for money:
|
There were several times this semester where the internet was down for more than 24 hours, including a span of nearly three days in April. The customer service representatives seem somewhat knowledgeable, but it takes them forever to act on a support ticket. It took a lengthy call from the marketing director of the five University House buildings to get any work done. Very unreliable service, and when you have a problem, it takes a lot of time to even tell them to get it fixed.
Followup comments: | Forums » comments on review of Pavlov Media |
| »next review in page (previous review)
Review by pavlovsucks
Posted: 2.6 years ago
member for 2.6 years, 17 visits, last login: 2.1 years ago
Madison,Dane,WI
Contract price not specified.
"Absolutely nothing."
"Worst internet service in history of man (i'm serious)"
"i would rather use a 28.8k dial-up connection than this."
| Pre Sales information:
Install Co-ordination:
Connection reliability:
Tech Support:
Services:
Value for money:
|
I was fairly surprised to find out that Pavlov Media was not listed on broadband reports, as far as i know they provide service to many customers(lol not really) in Wisconsin and Illinois areas. Pavlov Media steals your money by making plenty of contracts with many university and other medium to large organizations to embed their service in the client's rental fees. For how cheap I don't know, but it averages out to less than 20$ per person for their so-called 1.5mbps "quality high speed internet" service here at University House - Langdon, a private dorm in Wisconsin's UW-Madison campus and downtown area.
When I first signed up to live at the UH-Langdon I carelessly asked if internet service is provided for here and who was the service provider. The manager at the time said "all I know is we're using DSL service from Pavlov Media, here's a pamphlet." I was curious because I have never heard of that ISP name before anywhere, and only of Charter Communications and AT&T in the Madison City metro area. So I called their 24 hour "help"(you'll see what I mean later) line later that night and asked "what type of DSL service do you guys provide to UH-Langdon in Madison Wisconsin?" the guy was clueless and eventually told me that was 'confidential' information after I explained that all I wanted to know was the speed offered there.
Nevertheless, I moved in a few days later and noticed that the internet speed was alot slower than the university dorm speeds, but that's okay because that was expected beforehand. I didn't use the computer much until almost a week later when I continuously noticed that there was something wrong with the internet speed which I later found out to be packet loss. I took notice of that and ran ping and bandwidth tests and sent the results to the email addresses listed on the Pavlov Media's University House Langdon User Listing page.
A few days later I received nothing in email and no phone calls, so I called them back and asked about it, I later found out they somehow never received the email, the tech on the phone asked me to send them to 2 different email addresses this time and said that they will get back to me by the end of the week. 2 weeks later, I thought I had given them enough time to act on this already, then only to find out that all the emails I had previous sent were either "rejected by server" or "connection failure" to the email addresses listed on the Pavlov Media help page as well as the email addresses the tech told me on the phone himself.
I called right back and asked about that, this time the new tech said for me to send the test results to his email directly and that he will forward that to their Network Operations Center, and assured me that he will let me know as soon as my ticket has been reviewed by their Network Operations Center. I gave them enough time again, another 2 weeks later I still didn't get anything from Pavlov Media, so I called back and asked about it.
This time the same tech guy named Allen from last time talked to me and said that he received a verbal response from "Paul" in the Network Operations Center that which "Paul" didn't see a problem with the issued ticket(to give you guys some background information here, I did what the Pavlov Media help page said and ran ping tests to google, yahoo, and apple.com) as well as bandwidth test at »promos.mcafee.com/speedometer/, the ping tests resulted in a few 50 to 380 ping spikes and averaged about 50 to 60 percent packet loss), so I asked Allen how could Paul not see a problem with those results, he explained that what he got was simply a verbal response, nothing official and told me to wait and that he will call me back for sure this time(unlike the other times he promised to call back and later told me that he "forgot").
By the following Monday I did receive a voicemail from Allen saying that the suspected packet loss problem is a result of a bad laser link signal between the buildings and said that they will work to fix that as soon as possible. By Friday of that week he left another message asking me to check to see whether or not the packet loss issue has been resolved.
Here's what the internet was like at that time: when playing any online games with any type of ping/packet monitor, I would receive normal expected Pavlov Media speed for a few good minutes, then my packet loss would rush all the way up to 70 and steadily climb, this would go on for about 5 to 10 minutes and eventually calm down, happening about four to six or seven times per hour, not to mention the frequent disconnects I got when the internet would basically cripple and become impossible to even open up the Firefox startup page, when 30 minute long ping tests are ran resulting in packet losses as high as 70s). What happened the next day which was Saturday was completely surreal, there was 0 to 1 percent packet loss the entire day, and I thought to myself, wow I guess they finally fixed the internet.
Before I go on, I need to lay down some more background information. The entire past 3 months that I have been using Pavlov Media's "high quality" high speed DSL internet service, it wasn't just me that was experiencing the same exact problems, every single person who lived here that I had asked would tell me things such as "the internet has been acting up", "it's a piece of shit", "the internet is horrible here", and the best part, none of us could possibly escape this service because: all the residents here as well as alot of other large multidwelling units Pavlov Media provides high speed DSL to all over the nation are only using Pavlov because it's an included service in their leasing contract.
Our landlords(nationwide) would prohibit us to pay for other more desirable services because they say that would probably involve physically going into the wall jacks and "tear things up", not even giving a chance for me to explain how there might be other ways around it. Most of us also could not afford the wasted money to break our leasing contracts(which are semester leases at the least and costs thousands of dollars) and try to move elsewhere.
I never bothered to contact Pavlov Media's technical help staff again after that 1 and half month operation they had on our current DSL service which only resulted in it being even worse than I had previous imagined possible. As I am typing this to you, I tried to open up my Wisconsin university email and show you the ping tests I had, only to have it time out numerous times. I also tried to run the speed test here on broadband report, after leaving that on for about 30 minutes nothing had even happened.
As of today, there hasn't been one complete hour that I and my roommate had been using the internet without experiencing less than 20 to 30% packet loss. Every couple of seconds, not minutes, the service would get so bad that opening up www.google.com could only be a fantasy, and I will copy and save this long piece of essay and keep trying to send it to Broadband reports until it gets through.
Followup comments:
lookingUH
@ameritech.net
| Quick question After reading your review of the internet service I am glad I did as I was considering living at UH Langdon. Part of me can't help but wonder if your exaggerating at all, I mean as bad as it sounds you did make a noticeable contradiction you originally said "there was 0 to 1 percent packet loss the entire day, and I thought to myself, wow I guess they finally fixed the internet." only to follow up in the next paragraph with the claim "there hasn't been one complete hour that I and my roommate had been using the internet without experiencing less than 20 to 30% packet loss." So I juts kind of wonder which is it did it actually work for 24 hours or never at all, not trying to be an ass or anything but I couldn't help but notice that. | |
| | pavlovsucks
join:2007-04-14
Madison, WI
| Re: Quick question No prob man, however I really don't believe I had been exaggerating at all. It's time for me to post a follow-up anyways.
For the past few days the internet has not even been working, for reasons unknown, the entire complex other than the downstairs computer lab couldn't get any connection at all. Pavlov "promptly" responded about 3-4 days ago and said that the problem would be fixed the very next day if not the day of. No one from Pavlov showed up nor contacted UH-Langdon by the end of yesterday. This was the status of the internet for the past few days:
»img258.imageshack.us/img258/2585···dwh9.jpg
»img139.imageshack.us/img139/7323···2st2.jpg
As of today, this is what the net is like:
Pinging google.com [72.14.207.99] with 32 bytes of data:
Reply from 72.14.207.99: bytes=32 time=1014ms TTL=239
Reply from 72.14.207.99: bytes=32 time=912ms TTL=239
Reply from 72.14.207.99: bytes=32 time=1081ms TTL=239
Reply from 72.14.207.99: bytes=32 time=1135ms TTL=239
Reply from 72.14.207.99: bytes=32 time=1118ms TTL=239
Reply from 72.14.207.99: bytes=32 time=1456ms TTL=239
Reply from 72.14.207.99: bytes=32 time=1266ms TTL=239
Request timed out.
Request timed out.
Reply from 72.14.207.99: bytes=32 time=1034ms TTL=239
Reply from 72.14.207.99: bytes=32 time=926ms TTL=239
Reply from 72.14.207.99: bytes=32 time=957ms TTL=239
Reply from 72.14.207.99: bytes=32 time=956ms TTL=239
Reply from 72.14.207.99: bytes=32 time=956ms TTL=239
Reply from 72.14.207.99: bytes=32 time=978ms TTL=239
Request timed out.
Reply from 72.14.207.99: bytes=32 time=1188ms TTL=239
Reply from 72.14.207.99: bytes=32 time=1126ms TTL=239
Reply from 72.14.207.99: bytes=32 time=1011ms TTL=239
Reply from 72.14.207.99: bytes=32 time=958ms TTL=239
Reply from 72.14.207.99: bytes=32 time=970ms TTL=239
Reply from 72.14.207.99: bytes=32 time=1051ms TTL=239
Ping statistics for 72.14.207.99:
Packets: Sent = 22, Received = 19, Lost = 3 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 912ms, Maximum = 1456ms, Average = 1057ms
I find it hilarious that the Pavlov website boasts with the slogan "You Ring, We Respond", and this is their description of their High Speed Internet service:
At Pavlov Media, we understand that staying connected is of utmost importance(LOL!). If your community offers Pavlov Media internet service(You should be thankful if yours doesn't), you can be assured that we are managing your network to achieve a high degree of reliability(LOL!), speed(LOL!) and convenience(LOL!). From the moment you register for service, we are there to keep each network strong, and each user happy(LOL!!).
do a simple google search about what anyone who uses Pavlov Media thinks about it, and you'll understand where I'm coming from.
Oh and I forgot to mention their 500mb/24hrs bandwidth limit, how very "convenient" indeed.
An example of my account:
In the last 24 hours, you have transferred a total of 5.17MB of data.
Your account is currently receiving normal network prioritization. Your network usage for the last 24 hours is less than 500 megabytes. Should your usage during any rolling 24 hour period exceed 500 megabytes, your account will be assigned a lower prioritization level on the network. Should this occur, you may continue to use the network, however some applications may experience a decrease in network performance.
It isn't "may experience a decrease in network performance", it's utterly impossible for Pavlov Media to decrease in performance at all. | |
| pavlovsucks
join:2007-04-14
Madison, WI
| the next day Reply from 64.233.187.99: bytes=32 time=921ms TTL=242
Reply from 64.233.187.99: bytes=32 time=997ms TTL=241
Reply from 64.233.187.99: bytes=32 time=962ms TTL=242
Reply from 64.233.187.99: bytes=32 time=924ms TTL=241
Request timed out.
Reply from 64.233.187.99: bytes=32 time=793ms TTL=242
Reply from 64.233.187.99: bytes=32 time=925ms TTL=242
Reply from 64.233.187.99: bytes=32 time=841ms TTL=241
Reply from 64.233.187.99: bytes=32 time=887ms TTL=241
Request timed out.
Reply from 64.233.187.99: bytes=32 time=869ms TTL=241
Reply from 64.233.187.99: bytes=32 time=863ms TTL=242
Reply from 64.233.187.99: bytes=32 time=913ms TTL=242
Reply from 64.233.187.99: bytes=32 time=1024ms TTL=241
Reply from 64.233.187.99: bytes=32 time=875ms TTL=242
Reply from 64.233.187.99: bytes=32 time=881ms TTL=241
Reply from 64.233.187.99: bytes=32 time=929ms TTL=241
Ping statistics for 64.233.187.99:
Packets: Sent = 502, Received = 435, Lost = 67 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 529ms, Maximum = 1266ms, Average = 890ms | |
| | pavlovsucks
join:2007-04-14
Madison, WI | Re: the next day the internet has been completely out of service for reasons unknown again since the date of the previous post until this one. | |
| | | pavlovsucks
join:2007-04-14
Madison, WI
| Re: the next day and they put up a giant sign downstairs saying that the internet finally works, this is the quality of it (after being down about 4-5 days in the past week)
Pinging google.com [64.233.167.99] with 32 bytes of data:
Reply from 64.233.167.99: bytes=32 time=56ms TTL=244
Reply from 64.233.167.99: bytes=32 time=71ms TTL=244
Reply from 64.233.167.99: bytes=32 time=91ms TTL=244
Reply from 64.233.167.99: bytes=32 time=152ms TTL=244
Reply from 64.233.167.99: bytes=32 time=33ms TTL=244
Reply from 64.233.167.99: bytes=32 time=282ms TTL=244
Reply from 64.233.167.99: bytes=32 time=284ms TTL=244
Reply from 64.233.167.99: bytes=32 time=302ms TTL=244
Reply from 64.233.167.99: bytes=32 time=440ms TTL=244
Reply from 64.233.167.99: bytes=32 time=648ms TTL=244
Reply from 64.233.167.99: bytes=32 time=540ms TTL=244
Reply from 64.233.167.99: bytes=32 time=375ms TTL=244
Reply from 64.233.167.99: bytes=32 time=439ms TTL=244
Reply from 64.233.167.99: bytes=32 time=348ms TTL=244
Reply from 64.233.167.99: bytes=32 time=232ms TTL=244
Reply from 64.233.167.99: bytes=32 time=84ms TTL=244
Reply from 64.233.167.99: bytes=32 time=60ms TTL=244
Reply from 64.233.167.99: bytes=32 time=236ms TTL=244
Reply from 64.233.167.99: bytes=32 time=87ms TTL=244
Reply from 64.233.167.99: bytes=32 time=94ms TTL=244
Reply from 64.233.167.99: bytes=32 time=36ms TTL=244
Reply from 64.233.167.99: bytes=32 time=92ms TTL=244
Reply from 64.233.167.99: bytes=32 time=64ms TTL=244
Reply from 64.233.167.99: bytes=32 time=67ms TTL=244
Reply from 64.233.167.99: bytes=32 time=347ms TTL=244
Reply from 64.233.167.99: bytes=32 time=498ms TTL=244
Reply from 64.233.167.99: bytes=32 time=935ms TTL=244
Reply from 64.233.167.99: bytes=32 time=632ms TTL=244
Reply from 64.233.167.99: bytes=32 time=408ms TTL=244
Reply from 64.233.167.99: bytes=32 time=383ms TTL=244
Reply from 64.233.167.99: bytes=32 time=159ms TTL=244
Reply from 64.233.167.99: bytes=32 time=214ms TTL=244
Reply from 64.233.167.99: bytes=32 time=367ms TTL=244
Reply from 64.233.167.99: bytes=32 time=216ms TTL=244
Reply from 64.233.167.99: bytes=32 time=68ms TTL=244
Request timed out.
Reply from 64.233.167.99: bytes=32 time=79ms TTL=244
Reply from 64.233.167.99: bytes=32 time=70ms TTL=244
Reply from 64.233.167.99: bytes=32 time=156ms TTL=244
Reply from 64.233.167.99: bytes=32 time=240ms TTL=244
Reply from 64.233.167.99: bytes=32 time=422ms TTL=244
Reply from 64.233.167.99: bytes=32 time=365ms TTL=244
Reply from 64.233.167.99: bytes=32 time=340ms TTL=244
Request timed out.
Reply from 64.233.167.99: bytes=32 time=53ms TTL=244
Reply from 64.233.167.99: bytes=32 time=36ms TTL=244
Reply from 64.233.167.99: bytes=32 time=63ms TTL=244
Reply from 64.233.167.99: bytes=32 time=63ms TTL=244
Request timed out.
Reply from 64.233.167.99: bytes=32 time=38ms TTL=244
Reply from 64.233.167.99: bytes=32 time=35ms TTL=244
Reply from 64.233.167.99: bytes=32 time=58ms TTL=244
Reply from 64.233.167.99: bytes=32 time=73ms TTL=244
Reply from 64.233.167.99: bytes=32 time=129ms TTL=244
Reply from 64.233.167.99: bytes=32 time=103ms TTL=244
Reply from 64.233.167.99: bytes=32 time=38ms TTL=244
Reply from 64.233.167.99: bytes=32 time=93ms TTL=244
Reply from 64.233.167.99: bytes=32 time=216ms TTL=244
Ping statistics for 64.233.167.99:
Packets: Sent = 58, Received = 55, Lost = 3 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 935ms, Average = 218ms
un-fucking-bearable. | |
| | | | pavlovsucks
join:2007-04-14
Madison, WI
| a week later this is Pavlov media's premium internet service, supposedly 1.5mb down, and 1mb up. and here i present to you what their "high quality" service truly promises:
Pinging google.com [64.233.167.99] with 32 bytes of data:
Reply from 64.233.167.99: bytes=32 time=750ms TTL=244
Reply from 64.233.167.99: bytes=32 time=558ms TTL=244
Reply from 64.233.167.99: bytes=32 time=528ms TTL=244
Reply from 64.233.167.99: bytes=32 time=551ms TTL=244
Reply from 64.233.167.99: bytes=32 time=485ms TTL=244
Request timed out.
Reply from 64.233.167.99: bytes=32 time=624ms TTL=244
Reply from 64.233.167.99: bytes=32 time=507ms TTL=244
Reply from 64.233.167.99: bytes=32 time=617ms TTL=244
Reply from 64.233.167.99: bytes=32 time=656ms TTL=244
Reply from 64.233.167.99: bytes=32 time=693ms TTL=244
Reply from 64.233.167.99: bytes=32 time=700ms TTL=244
Reply from 64.233.167.99: bytes=32 time=545ms TTL=244
Reply from 64.233.167.99: bytes=32 time=539ms TTL=244
Reply from 64.233.167.99: bytes=32 time=578ms TTL=244
Reply from 64.233.167.99: bytes=32 time=598ms TTL=244
Reply from 64.233.167.99: bytes=32 time=689ms TTL=244
Reply from 64.233.167.99: bytes=32 time=617ms TTL=244
Reply from 64.233.167.99: bytes=32 time=644ms TTL=244
Reply from 64.233.167.99: bytes=32 time=594ms TTL=244
Reply from 64.233.167.99: bytes=32 time=647ms TTL=244
Reply from 64.233.167.99: bytes=32 time=596ms TTL=244
Ping statistics for 64.233.167.99:
Packets: Sent = 22, Received = 21, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 485ms, Maximum = 750ms, Average = 605ms
and then other sites, that Pavlov said to do ping tests on when we see a problem(which is all the fucking time.):
Pinging apple.com [17.254.3.183] with 32 bytes of data:
Reply from 17.254.3.183: bytes=32 time=560ms TTL=243
Reply from 17.254.3.183: bytes=32 time=664ms TTL=243
Reply from 17.254.3.183: bytes=32 time=784ms TTL=243
Reply from 17.254.3.183: bytes=32 time=750ms TTL=243
Reply from 17.254.3.183: bytes=32 time=596ms TTL=243
Reply from 17.254.3.183: bytes=32 time=593ms TTL=243
Reply from 17.254.3.183: bytes=32 time=649ms TTL=243
Reply from 17.254.3.183: bytes=32 time=514ms TTL=243
Ping statistics for 17.254.3.183:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 514ms, Maximum = 784ms, Average = 638ms
C:\Documents and Settings\Chen>ping -t dslreports.com
Pinging dslreports.com [209.123.109.175] with 32 bytes of data:
Request timed out.
Reply from 209.123.109.175: bytes=32 time=107ms TTL=52
Reply from 209.123.109.175: bytes=32 time=69ms TTL=52
Request timed out.
Reply from 209.123.109.175: bytes=32 time=124ms TTL=52
Reply from 209.123.109.175: bytes=32 time=68ms TTL=52
Reply from 209.123.109.175: bytes=32 time=104ms TTL=52
Reply from 209.123.109.175: bytes=32 time=134ms TTL=52
Request timed out.
Reply from 209.123.109.175: bytes=32 time=64ms TTL=52
Reply from 209.123.109.175: bytes=32 time=69ms TTL=52
Reply from 209.123.109.175: bytes=32 time=66ms TTL=52
Request timed out.
Reply from 209.123.109.175: bytes=32 time=62ms TTL=52
Reply from 209.123.109.175: bytes=32 time=81ms TTL=52
Reply from 209.123.109.175: bytes=32 time=58ms TTL=52
Reply from 209.123.109.175: bytes=32 time=94ms TTL=52
Reply from 209.123.109.175: bytes=32 time=62ms TTL=52
Reply from 209.123.109.175: bytes=32 time=176ms TTL=52
Reply from 209.123.109.175: bytes=32 time=66ms TTL=52
Reply from 209.123.109.175: bytes=32 time=67ms TTL=52
Reply from 209.123.109.175: bytes=32 time=114ms TTL=52
Reply from 209.123.109.175: bytes=32 time=200ms TTL=52
Ping statistics for 209.123.109.175:
Packets: Sent = 23, Received = 19, Lost = 4 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 200ms, Average = 93ms | |
|
UHLStudent
@fusionbroadband.net
|  The wonderful Pavlov Media
| |
| | pavlovsucks
join:2007-04-14
Madison, WI | Re: The wonderful Pavlov Media lol this is great, send me your aim/msn/email on here please  | |
| kezyxes
join:2007-06-12
| Call with Pavlov Media I'm an incoming freshman for the 2007-2008 school year at Madison, and considered UH Langdon.
It's a good thing I did some research on dslreports on Pavlov Media before I decided to sign a contract.
I decided to call Pavlov Media to hear what they had to say about the problems experienced in april-may. Using the customer service number for cable and ethernet (866-236-6688), I did not speak to a CSR even after 2 hours on hold. I didn't wait longer because I had another incoming call. (The call lasted from about 19:00 CST to 21:00 CST on a weekday.)
Next, I tried the "Subscrption Service Number" (800-538-2123), which is a number that operators of large multi-dwelling units call for problems. (Note: Pavlov Media _only_ sells services to big apartments.) This time, I was put on hold for only 8-9 minutes.
The woman on the other side was very nice, and seemed to know how packet loss/ping/etc works. She also seems familier with the problems experienced by UH buildings in Madison over april-june.
She told me the following:
- More T1 lines are added to all of the UH buildings.
- She spent around 2 minutes trying to find the ETA on these T1 lines, but said they were not posted. She said usually these installations take about 6 months.
- New servers (I'm guessing routers with better packet queueing?) were just recently installed
- These servers (routers) are not operational yet
- The old 250MB/day or 500MB/day cap are being removed. Instead, the new servers (routers?) let everybody "browse at about the same speed".
- When I asked her about bandwidth limits, she tried to find the information, but "couldn't access the [newly installed] servers".
- She said something along the lines of "Under the new servers, the daily cap is removed, but people with more bandwidth will experience more packet loss".
Of course, take these with a pound of salt.
The last part sets me off; I don't know of a single packet scheduler that makes people with more bandwidth have higher packet loss. This makes me think that the above might be just a ploy, although I couldn't tell such from the woman's voice.
There are also a couple consistency issues; nothing was mentioned about the | |
| cbjaxx
join:2006-05-04
Jacksonville, FL
| Finally a light at the end I am very happy to announce that my builders have recently kicked Pavlov to the curb and we will be getting a new ISP as of tomorrow. I can only hope they will provide better service than pavlov and is not pavlov under a different name. anyone every hear anything about beyond communications? | |
| | pavlov sucks
join:2007-09-26 | Re: Finally a light at the end It doesn't seem Beyond Communications is any worse or better. I'd liken the current switch to one of management, it still seems the horrid tech support exists as well as horrible speeds. | |
| | cbjaxx
join:2006-05-04
Jacksonville, FL | This is true I personally believe Beyond Communications is worse with their bursting upload speeds. Its rare that I see my connection go over 300k down lately. I have something in the works to fix that though. I will see how that goes for now | |
| | | pavlov sucks
join:2007-09-26
1 edit | Re: Finally a light at the end The speeds are capped at 3mb, but it seems for the past 2 or 3 days, I've been lucky to get over 250kb, which is odd. Upload speeds are great, but I wish there was something I could do about the download speeds. Let me know if you get something going. | |
|
Pavlov go away
@pavlovmedia.com
| Pavlov in UCF University House Well, since I have 2 desktops, 1 laptop, a Wii and a Xbox 360 I decided to call Pavlov media to try to get my router to work. While talking to the tech support guy for many hours he told me many times over that they don't support routers but he will try to find a way past this. I mentioned to him that it was a D-Link router and he talked as if he had never heard of D-Link before. After about 3 hours of tech support the only thing we did was disable the mac bridge on one of my computers. So that was great.
Oh and also I tried to download some Halo 3 videos on xbox live last night and after about a hour and a half it got to 4 percent on a 84 mb video. Gotta love that Pavlov. | |
|
Edandris
@pavlovmedia.com | worst ISP ever Don't even bother with them. I am steaming right now....its they are horrible. I might as well power a satellite i build myself with a gerbal in a wheel too get better internet. | |
|
Burn Down Pavlov
@pavlovmedia.com
| I have never seen worse service I have been living in a new apartment complex in Central Illinois for a month. The complex was just recently finished and is completely new. You would figure that you would not see any problems with service. I was VERY wrong. I have been without Internet for 5 days from Pavlov Media. They just tell me that they will have a tech out to me as soon as possible. This ISP is a total joke. Other apartments in my building and mine does not. It cannot be a huge issue and how hard is it to send a technician from their headquarters which is based here in town 2 miles to a complex to reset their equipment. I have recently called other ISPs to see about switching service.
Honestly I hope Pavlov Media would burn to the ground. | |
|
Redcorvus
@pavlovmedia.com
| pavlov going the distance Unfortunately, pavlov media seems to be a growing business, because they've spread to my area (East Lansing, Michigan State) and I've been infected. I must confess that I haven't been getting quite as bad service as you guys. When I ping google it has decent latency with only about 2% packet loss. I have found out that I cannot play some computer games (Diablo 2 for instance) because the connection is utterly terrible. I also couldn't even connect my friend's xbox 360 because it would instantly get disconnected when we tried to play Halo 2. I am wishing I went with a different option than where I am living at now... | |
|
pavlovsucksdick
@pavlovmedia.com | garbage I go to michigan state and the internet here make me want to burn down my apartment. seriously though I get garbage when I try to ping google. | |
|
PavlovIsHorrible
@pavlovmedia.com
| Bad, very bad. I consistently have horrible download / upload speeds, and my pings time out.
I called Pavlov 3 time and explained my situation. A technician called my cell phone today and left a message saying that they are upgrading the bandwith for my site (The Landings at Chandler Crossings). They are trying to complete this by the end of October, but he made it clear that I should expect some delays (1-2 weeks).
Overall, I am annoyed and severely frustrated with Pavlov Media. | |
|
MSUROCKS
@pavlovmedia.com | Pavlov- improved? Has anyone noticed any improvement lately? I heard from the office that they finally upgraded our speeds last Friday (11/2)
anyone notice? i haven't had a chance to try yet | |
|
PavlovIsBETTER
@pavlovmedia.com | Yes Pavlov upgraded the internet and I now reach 750kbps CONSISTENTLY. It is tolerable now, w00p! | |
| | | | | Leyth
join:2008-02-18
Simpsonville, SC
·Pavlov Media
| Re: Yes I unfortunately have pavlov. The connection is good... when everyone has gone home for summer. Oh well 3 more months til everyone leaves and maybe... just maybe i'll get my 1mbit cap maxed out. There must be another solution to this. I admit i like the internet speed for online gaming but today on my online course it was really difficult to submit my answers. | |
| | | | chaser324
join:2008-02-24
Central, SC
·Pavlov Media
1 edit | University Village I just want to say that I agree with pretty much all of the previous comments made about Pavlov. I'm living at University Village (Clemson, SC), and they have a contract with Pavlov Media to provide internet service for the entire apartment complex. From the very first day I moved in here, I've had problems.
Lag spikes are a massive problem all day, every day. I would say every 5-10 minutes you are guaranteed to get at least one noticeable spike in the lag. This makes online gaming virtually impossible. Everything will seem fine for a while, and then...the lag comes...and it always comes. This problem carries over into just regular internet surfing as well though. You'll just be looking at stuff online and then all of a sudden everything will come to a screeching halt for a minute or more.
At least once a week you're also pretty much guaranteed to completely lose internet access for a couple of hours. I'm not really sure why, but it seems to always happen. On at least a couple of occasions in the past year, there were times when internet access would be unavailable for an entire day or more. There was also two entire weeks where the connection quality was such complete crap that it may as well have been dead.
As far as download speeds, that's been a variable thing. From the time I moved in up until a few months ago it was pretty much always the case that during high traffic times you would get download bandwidth somewhere in the neighborhood of 200-300 kbps. Unacceptably slow. However during lower traffic times I could get 4-5 Mbps. There was a "fair-share" system in place that was supposed to give less priority to your connection if you downloaded over 500 MB in a 24 hour period, but it didn't really seem to have any real effect. A couple of months ago though the entire situation seems to have changed. It would appear to me that some sort of cap has been placed on downloads that never allow them to get over 1 Mbps. My download speed now tends to always float at right around 600-700 kbps sometimes jumping up to 800-900 kbps during low traffic times. I guess maybe I should be happy about the improved consistency...but I'm not really...it should still be better than this.
As far as customer service...there isn't any real "service". There was one time when I tried interfacing with their customer support (during the two week period mentioned previously where the internet was virtually inaccessible), and this is pretty much how it went. I send an initial e-mail with a thorough explanation of the situation along with the piles of information that they request (pings, traceroutes, various internet bandwidth tests, etc.). A few days later I get a reply that says they aren't aware of any current quality issues in my area, and that in order for them to further assist me I need to answer an entire page or more of general questions. So I begrudgingly answer all of the additional questions that they sent me. I wait an entire week, and never hear any sort of reply. I e-mail them once again. The reply the next day with an e-mail saying that they were sorry for the delay, they are now aware that there is an issue and they are investigating it. A few days later, I get an e-mail from one of the apartment complex admins that the issue has been resolved...and I suppose it was...the internet quality had returned to its previous level of crappiness.
Also one additional complaint I would like to put forth (this one is rather small in comparison to the others) is that I hate ISPs that have these stupid registration web pages that you are forced to view the first time you try to connect a new device. At the very least, if you are going to do this, provide me with an easy way to register additional MAC addresses so that I can easily register devices that don't have a web browser (XBox, PS3, etc.). | |
| | | |
| Forums » comments on review of Pavlov Media |
|
|
·
