Lantency issues with major backbones

[kmaw]

Originally Posted by Jme574

It is related to my hosting. If they pay me to host their site and through no fault of their own, their sites are unavailable, it has to fall somewhere.

It was out of your control, HG's, and the Planets. It was beyond. It could have happened whether you were with HG or another hosting company.

I wouldn't have taken the blame or given the credit, personally. But glad to see you're taking some responsibility... it should give your customers more faith in you, because you're not simply passing the buck to someone in cyberspace they don't know.

[PsiPro]

Originally Posted by Jme574

You can believe the HG will be getting some kind of credit from the planet for their problems and down time, they are just not gonna pass it along. So those of us that actually want or need to keep our customers are gonna have to eat the costs of credit to our customers.

The problem was not the planets directly at all. The issue was that the internet backbone had a high latency (for a backbone). ThePlanet is NOT a backbone, they are simply connected directly to many of them.

ThePlanet Boasts 100% Uptime guarentee, the same thing that is promised by hosting companies. The problem is that clients do not understand what uptime is. ThePlanet promises that their infastructure will be avaliable 100% of the time, server to server connections etc. What YOU are promising to your customers is that every link in the chain of the internet from your server to their house will be working 99.9% of the time, somthing far outside of your control. Do a tracert (Start > Run > Type 'cmd' (no quotes) > type 'tracert YOURSERVER.COM' (no quotes, replace with your domain)) this will show you how many connections on the internet could be giving you trouble and causing downtime on your servers.

You should also know, that Hostgator will proably not receive any form of rembursment for this downtime because as was said they are not paying ThePlanet to upkeep the internet backbones. But if they did get rembursment... Let say for argument they pay $300 for the server they are on, and lets say a full 24hr downtime, so they receive... $10 back, divided between the 150 clients on the server, you would be entitled to.. $1/45, not much to speak of so I wouldn't be trying to say HG is trying to earn the extra $0.02 off of you.

And I do agree with you, it can be argued that it is good customer service to apease your customers, but I still wouldn't take the blame for the downtime.

In all honesty tho, HG proably didn't to a terribly lot to try to bring their servers back to life. It would even have been dificult to connect to them as they would likely have to SSH in from another of their servers but it still would have been slow, difficult, and painful. The issue was likly fixed by ThePlanet.

[kmaw]

That's wild.. who knew... it even jumps around the planet a few times..


C:\Documents and Settings>tracert kylemaw.com

Tracing route to kylemaw.com [74.52.11.162]
over a maximum of 30 hops:

1 64 ms 67 ms 85 ms 204.48.0.1
2 58 ms 57 ms 71 ms rtr-chatham-core.ciaccess.com [209.216.133.1]
3 84 ms 113 ms 80 ms 216.254.143.245
4 83 ms 88 ms 80 ms gi1-0-3.bb2.tor.primus.ca [216.254.128.168]
5 58 ms 98 ms 83 ms 216.95.173.29
6 86 ms 76 ms 65 ms 0.so-6-0-1.xl2.tor2.alter.net [152.63.131.134]
7 107 ms 77 ms 91 ms 0.so-7-0-0.xl2.dca5.alter.net [152.63.42.189]
8 80 ms 83 ms 99 ms 0.so-7-0-0.br1.dca5.alter.net [152.63.43.177]
9 102 ms 104 ms 84 ms telia-gw.n54ny.ip.att.net [192.205.32.49]
10 148 ms 124 ms 129 ms tbr1-p011701.wswdc.ip.att.net [12.123.8.106]
11 115 ms 150 ms 132 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
12 128 ms 141 ms 135 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
13 146 ms 132 ms 137 ms gar1-p370.dlrtx.ip.att.net [12.123.16.173]
14 128 ms 116 ms 134 ms 12.119.136.18
15 127 ms 131 ms 115 ms vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]

16 134 ms 140 ms 137 ms vl21.dsr01.dllstx2.theplanet.com [70.85.127.67]

17 145 ms 114 ms 121 ms po1.car01.dllstx6.theplanet.com [12.96.160.18]
18 124 ms 139 ms 130 ms a2.b.344a.static.theplanet.com [74.52.11.162]

Trace complete.

[LvTrain]

Looks like "Mustang" is also down

the trace route comes back fine but all my sites are down.

TraceRoute to 67.19.170.34 [thempire.net]
Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 66.98.244.1 gphou-66-98-244-1.ev1.net
2 0 0 0 66.98.241.16 gphou-66-98-241-16.ev1.net
3 0 0 0 66.98.240.9 gphou-66-98-240-9.ev1.net
4 1 1 1 216.200.251.165 ge-6-0-0.mpr1.iah1.us.above.net
5 5 5 5 64.125.31.38 so-6-1-0.cr1.dfw2.us.above.net
6 6 6 6 64.124.79.77 64.124.79.77.theplanet.com
7 6 6 6 70.85.127.62 vl32.dsr02.dllstx3.theplanet.com
8 6 6 7 70.85.127.91 vl42.dsr02.dllstx4.theplanet.com
9 6 6 6 67.19.255.10 gi1-0-1.car03.dllstx4.theplanet.com
10 6 6 6 67.19.170.34 mustang.websitewelcome.com



It appears that DNS is not working on mustang.

[PsiPro]

If you find your site to be down, and a timeout in tracert, you should check http://www.dnsstuff.com/ and do the online tracert there. This will let you know if the issue is localized in your area, or their area.