Pelf suggested I post up my problem in Blogathon’s forum. I notice someone else having the same problem as well. Bill, Blogathon’s admin said there are looking into my problem. It seems like they couldn’t access my blog. I wonder why.
All this problem is distracting me. I need to concentrate on my 30 minutes cycle dateline damn it. Hmmm…I feel anger in me. Must be feeling hungry. Time for some food. My mom made porridge for dinner. I’m only eating it now (went out for dinner with gf earlier on) 
My parents tapao some capati as well. That will be for supper later on. Arggghhh…even eating is a problem. I’m eating in front of my computer now. I wonder if I have to bring the computer into the toilet if I need to take a dump later. Or maybe I could get a potty and finish my business in the room 
Stumble it!
Share it!
Subscribe to my feed
u use notebook with wi-fi, u can blog anywhere .. even in toilet
p/s: I do notice that TM net network is not stable tonight (based on feedback from my online kawan), and your webhost is hosting in TM data center, maybe the reason blogathon can’t access your blog.
But one thing I realized is that your blog loads fairly slowly generally.. But I’m sure if the Blogathon peeps are looking into your case..
I’ll continue to drop by, so don’t get distracted yet, OK? You’re doing well.. In fact, you still had time to visit me, thanks!
Don’t worry, keep blogging. Our pledge and donation are confirmed whether Blogathon take it as official or not.
perf,
I believe accessible speed of chankelwin.com is due to the data center is having packet loss or slow international connection.
http://www.tenthofmarch.com/2007/07/28/tmnet-datacenter-packet-loss-outbreak-again/
@hanneng
Thanks for the info. I’ve done a ping test and it looks like the TMNet outbreak is happening again. *sigh*
Bringing the notebook into the toilet will be a little risky. I don’t want it to get wet. Imagine if it dropped into the toilet bowl (before I flush) LOL.
@pelf
Thanks. I wander around sometimes when I have the time. The slowdown must be due to the packets loss problem TMNet is having.
@lilian
OK. Thanks!