I am not sure what is going on, since last month the connection is getting slower and some times it goes down completely! When running the tracert the problem is always
at Alter.net one ping before Tera byte.
Is any one else has this problem?

Alter.net does appear to be a bottleneck, but then again, maybe my route table needs to be optimised. I am in Northern California and terrabyte according to Visual Trace is in Canada, so its a long way to go, many networks to hop.

Alter, seems to be screwing around for me... i have a 50% packet loss average for the last few days :( so its really not a tera-byte issue..

Unfortunately, if the problem lies with UUNet (alter.net), there is little we can do. We do not peer with them directly; however, they seem to be the peer of choice for many US providers, meaning you're stuck going over them one way or another.

I find them faster than ever now and thats from the UK.

the speed from here(malaysia) is good ... but sometimes it takes few seconds to locate the domain name and connect to my site, but once it connected everything is good :)

the problem was not the connection, my server CPU load is way up, Average load
1 min 11
5 min 7
15 min 5.7

Well this afternoon it is tera-bytes problem. This has been ongoing for the past 2 hours and is clearly at tera-bytes end.

10 226 ms 238 ms 212 ms sl-gw9-nyc-7-2.sprintlink.net [144.232.173.125]

11 232 ms 220 ms 218 ms sl-bb20-nyc-3-0.sprintlink.net [144.232.7.93]
12 242 ms 258 ms 246 ms sl-bb22-chi-12-0.sprintlink.net [144.232.18.53]

13 280 ms 290 ms 284 ms sl-bb10-sea-8-0.sprintlink.net [144.232.18.49]
14 324 ms 296 ms 268 ms sl-bb4-sea-0-0-0.sprintlink.net [144.232.6.10]
15 320 ms 296 ms 286 ms sl-insinco-6-1-0.sprintlink.net [144.228.109.254
]
16 320 ms 300 ms 270 ms 204.50.128.190
17 272 ms 388 ms 288 ms 204.50.128.138
18 290 ms 280 ms * core1-s5-1.edm.tera-byte.com [207.107.204.162]
19 290 ms 290 ms 290 ms cat6006-vlan11.edm.tera-byte.com [216.234.160.30
]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.

When i take a look at my bandwidth monitor i see 2 (short) moments when there is suddenly no traffic at all.

Originally posted by dutchie
When i take a look at my bandwidth monitor i see 2 (short) moments when there is suddenly no traffic at all.

My site monitor showed an outage:

Server www.x*********** failed to respond properly!
HTTP did not respond.

Message sent: 12:22 PM MDT April 14, 2001
(18:22 PM GMT April 14, 2001)


It checks once an hour.

This is really awefull, I just tried to log into the web admin section of my website to update a little information and the login went just fine, then when I clicked on a link it took a while and then I got DNS Error (like if the server was dead), then after about a minute it worked again and I changed the info and when I pressed submit it went dead on me again. Arrrgh!! :angry:

I'm seariously starting to consider giving up this server and go back to sharing until I can get my own server co-located in a couple of months. This is not worth it and definitely not good for business!

Without exaggerating I can say that 50% of the time I either can't get a connection to my server or it is so slow that I feel I'm using my old 2,400bit modem!

Saeed

mm its not that bad over here, and i'm calling in from europe.

and Mike, i meant tera-byte's monitor in the control panel.

Its just that there are +/- 2 moments a day that there seems to be no data-traffic. These are mostly short moments, and i wonder what they mean.
:confused:

[i] [snip]

and Mike, i meant tera-byte's monitor in the control panel.

Its just that there are +/- 2 moments a day that there seems to be no data-traffic. These are mostly short moments, and i wonder what they mean.
:confused: [/B]



Yup, I understand to be what you meant.

I posted my site monitor's pager notification because the timing coincided with c0bra's tracert nearly to the minute (taking into account the time zone differences.) In other words, my pager notification was independent verification of what c0bra reported.