Tech, Games, Blogging and Other Random Thoughts

The Day My Blog Responded “Bandwidth Limit Exceeded”

Posted on October 28, 2009  in Blog Experiences

Yesterday my blog responded with a Bandwidth Limit Exceeded message. I have tweeted about it here.

Menardconnect: waaaaah!!! Bandwidth Limit Exceeded!!! Fixing this now
1:19 PM Oct 27th from TweetDeck

I am very thankful that my web hosting company was very helpful and they have helped me fix this issue right away.

What is Bandwidth Limit Exceeded in simple terms? If you are a just doing some basic internet surfing, this means that the website you are visiting have reached the limit of amount of data transfer allowed in a period of time (usually a monthly quota) by its web hosting company. If the site you are visiting is your own website, then the explanation is the same but the ball is in your hands 🙂 . You should contact your web hosting company and upgrade your web-hosting plan to accommodate more data transfer or discuss other ways on how you can fix the problem.

Looking at the positive side of things: this is a good news in general; this bandwidth limit exceeded message usually means that your website have more visitors and more traffic.

Moving forward, some key lessons that I learned related to this incident:

  • this can be avoided with better planning and proper monitoring in place
  • I need attend to the paper work in a more timely manner or suffer the consequences 🙂

0 thoughts on “The Day My Blog Responded “Bandwidth Limit Exceeded””

  1. been there. done that. after the bandwidth limit exceeded error, expect for a “500 error” messages later, that is, if your blog gets too much traffic and uses too much resources at the same time. tapos, papalayasin ka na sa shared hosting coz nagcocomplain na mga kashare mo and you’ll start thinking of getting a VPS. 😀 those are nice problems to have, ibig sabihin, lumalaki na kita mo.

  2. I’m an newbie webapp developer and just got the same bandwidth limit message.
    Does this mean that the back-end coding is not the one to blame and mainly a host problem?

    1. @Jikoyster,
      Disclaimer: I am _not_ a web development/coding expert.
      But my advise here is that it will be wise to check if your back-end coding will result to excessive data transfer from the web server to the client. If yes then it may also lead to this error.
      Its also advisable to contact your web hosting provider to inquire about this problem.