I am having problems accessing this site tonight and I am trying to establish if it's the host or my computer.
slow?...hummmm... maybe the word 'SLUGGISH' would fit best...
have you got a recent backup?
I backed the site up at 1pm today actually :)
It seems like our server is under heavy load at the moment, I apologise for this temporary issue.
I have to go up to bed soon, but if anyone is still here please post here and let me know how long it goes on for.
Thanks.
(I am secretly pissed off that I just renewed the hosting for another year!!)
A bit earlier it took like forever to load the pages, but it seems ok now.
Maybe they sorted the problem now.
Yes it seems like the problem has gone away :)
I had problems around 19:00 ish gmt, seems ok now though dude.
Yup, yesterday I experienced also some slow connections.
Right now everything seems to work just fine again!
I am glad it's fixed now, sorry for the slow site folks.
Site was down for a bit late (but before midnight) last night. Are we stuck with this host? Not that big a problem, just annoying if you're halfway through a topic, or posting at the time.
Yes we have this host for another 11 months.. The biggest problem that I have is that there are several sites hosted here and it will be insanely difficult to swap them over.
I think that I will be moving DBF next year though.
Can see how that'd be a problem. More sites hosted = more sites down at the one time, though. That said, it's not that noticeable, and it's a pretty big load on the server (I guess?) at some times.
Let's put it this way, all the domains together have transferred over 8.5gb this month, DBF has done 4.5gb of that, we've served 137,000 pages this month, generating 1.5 million hits this month including bots.
As it stands we are becoming a medium level site, it's quite a nice problem to have really.
In practical terms it means that I will probably have to split the hosting of the domains I host over a few plans within the next 12 months.
I imagine that Hostpappa will get pissed off that we are using some bandwidth now :D
The site isnt really slow here... but last days i had sometimes the problem when entered the url of this site in firefox, that the site was not reachable... a few seconds/mins later it worked again...
Quote from: Shockwave on July 29, 2009
I imagine that Hostpappa will get pissed off that we are using some bandwidth now :D
Why? Don't you pay by the half GB for that stuff? More profit to them
Quote from: slinks on July 30, 2009
Quote from: Shockwave on July 29, 2009
I imagine that Hostpappa will get pissed off that we are using some bandwidth now :D
Why? Don't you pay by the half GB for that stuff? More profit to them
What usually happens with shared hosting is that when your site becomes busy it is a big drain on resources.
They mkay say unlimited bandwidth and storage, but if you go for a VPS or dedicated server there are clearly defined limits.
Hostpappa could probably host 15 small clients using the resources we're taking up, eventually hosts have a habit of saying thanks but no thanks, find someone else..
The last hours i had problems to connect to this site... i got every time an empty webpage and i have tried to reconnect to get a new IP adress and so on... all without luck.. having this problem last time very often but only with the url of this board... mhhhh... here are some tech datas i did... maybe it help you...!?
The contest (full sourcecode) of the site i got when tried to reach the dbf url... (transfer completed)
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><title></title></head><body></body></html>
Here are some infos about ping and tracert...
C:\>ping www.dbfinteractive.com
Ping wird ausgeführt für dbfinteractive.com [67.220.225.50] mit 32 Bytes Daten:
Antwort von 67.220.225.50: Bytes=32 Zeit=158ms TTL=46
Antwort von 67.220.225.50: Bytes=32 Zeit=158ms TTL=46
Antwort von 67.220.225.50: Bytes=32 Zeit=157ms TTL=46
Antwort von 67.220.225.50: Bytes=32 Zeit=157ms TTL=46
Ping-Statistik für 67.220.225.50:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 157ms, Maximum = 158ms, Mittelwert = 157ms
C:\>tracert www.dbfinteractive.com
Routenverfolgung zu dbfinteractive.com [67.220.225.50] über maximal 30 Abschnitt
e:
1 26 ms 25 ms 38 ms lo1.br60.dus.de.hansenet.net [213.191.64.39]
2 25 ms 25 ms 26 ms ae0-101.cr01.dus.de.hansenet.net [62.109.110.61]
3 29 ms 28 ms 27 ms so-3-0-0-0.cr01.fra.de.hansenet.net [213.191.87.
245]
4 27 ms 30 ms 31 ms ae0-101.pr01.fra.de.hansenet.net [62.109.109.176
]
5 31 ms 29 ms 28 ms fra32-hansenet-4.fra.seabone.net [89.221.34.45]
6 118 ms 119 ms 117 ms new4-new11-racc1.new.seabone.net [195.22.216.235
]
7 122 ms 121 ms 121 ms te-4-2.car3.Newark1.Level3.net [4.71.148.9]
8 126 ms 126 ms 126 ms ae-32-52.ebr2.Newark1.Level3.net [4.68.99.62]
9 127 ms 127 ms 127 ms ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101
]
10 138 ms 138 ms 139 ms ae-2-2.ebr2.Chicago2.Level3.net [4.69.132.69]
11 144 ms 143 ms 148 ms ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
12 144 ms 144 ms 143 ms ae-2-52.edge3.Chicago3.Level3.net [4.68.101.52]
13 179 ms 189 ms 167 ms BIG-PIPE-IN.edge3.Chicago3.Level3.net [4.53.96.1
06]
14 145 ms 144 ms 145 ms rc1ec-tge0-0-2-0.il.shawcable.net [66.163.65.45]
15 151 ms 152 ms 151 ms rc2sh-pos3-0.mt.shawcable.net [66.163.76.146]
16 157 ms 159 ms 157 ms 66.163.66.90
17 160 ms 159 ms 160 ms rx0sh-scratch-telecom.mt.bigpipeinc.com [66.244.
223.182]
18 157 ms 157 ms 158 ms hp17.hostpapa.com [67.220.225.50]
Ablaufverfolgung beendet.
C:\>ping www.dbfinteractive.com
Ping wird ausgeführt für dbfinteractive.com [67.220.225.50] mit 32 Bytes Daten:
Antwort von 67.220.225.50: Bytes=32 Zeit=158ms TTL=46
Antwort von 67.220.225.50: Bytes=32 Zeit=159ms TTL=46
Antwort von 67.220.225.50: Bytes=32 Zeit=158ms TTL=46
Antwort von 67.220.225.50: Bytes=32 Zeit=158ms TTL=46
Ping-Statistik für 67.220.225.50:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 158ms, Maximum = 159ms, Mittelwert = 158ms
C:\>tracert www.dbfinteractive.com
Routenverfolgung zu dbfinteractive.com [67.220.225.50] über maximal 30 Abschnitt
e:
1 26 ms 26 ms 148 ms lo1.br60.dus.de.hansenet.net [213.191.64.39]
2 25 ms 26 ms 25 ms ae0-101.cr01.dus.de.hansenet.net [62.109.110.61]
3 28 ms 30 ms 30 ms so-3-0-0-0.cr01.fra.de.hansenet.net [213.191.87.
245]
4 28 ms 28 ms 28 ms ae0-101.pr01.fra.de.hansenet.net [62.109.109.176
]
5 29 ms 28 ms 28 ms fra32-hansenet-4.fra.seabone.net [89.221.34.45]
6 119 ms 119 ms 119 ms new4-new11-racc1.new.seabone.net [195.22.216.235
]
7 122 ms 122 ms 121 ms te-4-2.car3.Newark1.Level3.net [4.71.148.9]
8 121 ms 125 ms 126 ms ae-32-52.ebr2.Newark1.Level3.net [4.68.99.62]
9 127 ms 127 ms 128 ms ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101
]
10 138 ms 139 ms 139 ms ae-2-2.ebr2.Chicago2.Level3.net [4.69.132.69]
11 150 ms 144 ms 144 ms ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
12 206 ms 176 ms 145 ms ae-2-52.edge3.Chicago3.Level3.net [4.68.101.52]
13 163 ms 161 ms 169 ms BIG-PIPE-IN.edge3.Chicago3.Level3.net [4.53.96.1
06]
14 143 ms 144 ms 144 ms rc1ec-tge0-0-2-0.il.shawcable.net [66.163.65.45]
15 151 ms 153 ms 153 ms rc2sh-pos3-0.mt.shawcable.net [66.163.76.146]
16 158 ms 160 ms 158 ms 66.163.66.90
17 158 ms 159 ms 159 ms rx0sh-scratch-telecom.mt.bigpipeinc.com [66.244.
223.182]
18 157 ms 158 ms 158 ms hp17.hostpapa.com [67.220.225.50]
Ablaufverfolgung beendet.
C:\>
According to your tracert it seems like the site failed at the host.
I had a database error message by email which means that the number of sql connections must have been maxed out.
Cheers for the heads up though mate. Please keep posting this stuff as I send it all on to the hosts whenever I need to complain.
The problem was with
new4-new11-racc1.new.seabone.net [195.22.216.235]
not with hostpapa
Jim
@Jim:
Why do you think or how/where do you know/see that the problem was at new4-new11-racc1.new.seabone.net [195.22.216.235] ?
@Shockwave:
About 5 minutes ago, this website was again not reachable for me (this time the message: site not found)...
two minutes later all works fine again
Thu, 06-August-2009 - 12:15 am (german time)
C:\>ping www.dbfinteractive.com
Ping wird ausgeführt für dbfinteractive.com [67.220.225.50] mit 32 Bytes Daten:
Antwort von 67.220.225.50: Bytes=32 Zeit=153ms TTL=49
Antwort von 67.220.225.50: Bytes=32 Zeit=154ms TTL=49
Antwort von 67.220.225.50: Bytes=32 Zeit=154ms TTL=49
Antwort von 67.220.225.50: Bytes=32 Zeit=154ms TTL=49
Ping-Statistik für 67.220.225.50:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 153ms, Maximum = 154ms, Mittelwert = 153ms
C:\>tracert www.dbfinteractive.com
Routenverfolgung zu dbfinteractive.com [67.220.225.50] über maximal 30 Abschnitt
e:
1 26 ms 27 ms 27 ms lo1.br56.dus.de.hansenet.net [213.191.64.35]
2 28 ms 26 ms 25 ms ae1-102.cr01.dus.de.hansenet.net [62.109.110.125
]
3 28 ms 28 ms 29 ms so-3-1-0-0.cr01.fra.de.hansenet.net [213.191.87.
158]
4 28 ms 28 ms 28 ms ae0-101.pr01.fra.de.hansenet.net [62.109.109.176
]
5 28 ms 29 ms 27 ms fra32-hansenet-2.fra.seabone.net [89.221.34.25]
6 118 ms 117 ms 117 ms new4-new50-racc1.new.seabone.net [195.22.216.239
]
7 117 ms 118 ms 117 ms te-4-2.car3.Newark1.Level3.net [4.71.148.9]
8 129 ms 124 ms 126 ms ae-32-52.ebr2.Newark1.Level3.net [4.68.99.62]
9 124 ms 123 ms 122 ms ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101
]
10 137 ms 135 ms 137 ms ae-2-2.ebr2.Chicago2.Level3.net [4.69.132.69]
11 145 ms 144 ms 144 ms ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
12 135 ms 134 ms 134 ms ae-2-52.edge3.Chicago3.Level3.net [4.68.101.52]
13 136 ms 136 ms 137 ms BIG-PIPE-IN.edge3.Chicago3.Level3.net [4.53.96.1
06]
14 135 ms 138 ms 137 ms rc1ec-tge0-1-2-0.il.shawcable.net [66.163.65.53]
15 153 ms 155 ms 154 ms rc2sh-ge4-0-0.mt.shawcable.net [66.163.77.121]
16 148 ms 150 ms 149 ms 66.163.66.90
17 154 ms 153 ms 154 ms rx0sh-scratch-telecom.mt.bigpipeinc.com [66.244.
223.182]
18 155 ms 155 ms 155 ms hp17.hostpapa.com [67.220.225.50]
Ablaufverfolgung beendet.
C:\>
new4-new50-racc1.new.seabone.net [195.22.216.239] again.
I had problems last night as well.
5 31 ms 29 ms 28 ms fra32-hansenet-4.fra.seabone.net [89.221.34.45]
6 118 ms 119 ms 117 ms new4-new11-racc1.new.seabone.net [195.22.216.235]
->Va!n - because your ping trace shows there's 90ms hop between these two servers. In comparison, hostpapa responded to their upstream provider in 1ms.
From your description it looks like it's dropping packets between those two nodes, causing sporadic failures. Whois tells me seabone.net is owned by networksolutions.com.
Jim
@jim: ah okay. thx
yeah... now i am lucky i can reach this website... yesterday (friday) i was the complete day at home and have tried again and again (over the full day until now) to reach this site... everytime without luck... :( Thats pretty bad... (for existing users and esp for newbies wanna visit this site the first time)
I dont know why this happens here.. i have often tried to reconnec, to get another ip... all other websites here worked fine and fast like pouet and co... just only this site was not reachable (just a blank empty browser window)
Cant we do something to solve this problem in future before loosing members / newbies?
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><title></title></head><body></body></html>
C:\>ping www.dbfinteractive.com
Ping wird ausgeführt für dbfinteractive.com [67.220.225.50] mit 32 Bytes Daten:
Antwort von 67.220.225.50: Bytes=32 Zeit=164ms TTL=49
Antwort von 67.220.225.50: Bytes=32 Zeit=164ms TTL=49
Antwort von 67.220.225.50: Bytes=32 Zeit=158ms TTL=49
Antwort von 67.220.225.50: Bytes=32 Zeit=170ms TTL=49
Ping-Statistik für 67.220.225.50:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 158ms, Maximum = 170ms, Mittelwert = 164ms
C:\>tracert www.dbfinteractive.com
Routenverfolgung zu dbfinteractive.com [67.220.225.50] über maximal 30 Abschnitt
e:
1 26 ms 26 ms 39 ms lo1.br61.dus.de.hansenet.net [213.191.64.40]
2 25 ms 25 ms 71 ms ae1-102.cr02.dus.de.hansenet.net [62.109.110.126
]
3 29 ms 52 ms 53 ms so-0-1-0-0.cr02.fra.de.hansenet.net [213.191.66.
34]
4 28 ms 28 ms 28 ms ae0-101.pr01.fra.de.hansenet.net [62.109.109.176
]
5 28 ms 28 ms 67 ms fra32-hansenet-4.fra.seabone.net [89.221.34.45]
6 151 ms 118 ms 117 ms new4-new11-racc1.new.seabone.net [195.22.216.235
]
7 117 ms 117 ms 117 ms te-4-2.car3.Newark1.Level3.net [4.71.148.9]
8 127 ms 123 ms 123 ms ae-32-52.ebr2.Newark1.Level3.net [4.68.99.62]
9 122 ms 126 ms 123 ms ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101
]
10 139 ms 142 ms 139 ms ae-2-2.ebr2.Chicago2.Level3.net [4.69.132.69]
11 151 ms 144 ms 143 ms ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
12 205 ms 138 ms 138 ms ae-2-54.edge3.Chicago3.Level3.net [4.68.101.116]
13 142 ms 144 ms 188 ms BIG-PIPE-IN.edge3.Chicago3.Level3.net [4.53.96.1
10]
14 144 ms 144 ms 144 ms rc1ec-tge0-0-5-0.il.shawcable.net [66.163.65.49]
15 157 ms 156 ms 155 ms rc2sh-pos3-0.mt.shawcable.net [66.163.76.146]
16 156 ms 157 ms 156 ms 66.163.66.90
17 157 ms 157 ms 158 ms rx0sh-scratch-telecom.mt.bigpipeinc.com [66.244.
223.182]
18 159 ms * 159 ms hp17.hostpapa.com [67.220.225.50]
Ablaufverfolgung beendet.
C:\>ping www.dbfinteractive.com
Ping wird ausgeführt für dbfinteractive.com [67.220.225.50] mit 32 Bytes Daten:
Antwort von 67.220.225.50: Bytes=32 Zeit=159ms TTL=49
Antwort von 67.220.225.50: Bytes=32 Zeit=159ms TTL=49
Zeitüberschreitung der Anforderung.
Antwort von 67.220.225.50: Bytes=32 Zeit=158ms TTL=49
Ping-Statistik für 67.220.225.50:
Pakete: Gesendet = 4, Empfangen = 3, Verloren = 1
(25% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 158ms, Maximum = 159ms, Mittelwert = 158ms
C:\>ping www.dbfinteractive.com
Ping wird ausgeführt für dbfinteractive.com [67.220.225.50] mit 32 Bytes Daten:
Antwort von 67.220.225.50: Bytes=32 Zeit=169ms TTL=49
Antwort von 67.220.225.50: Bytes=32 Zeit=158ms TTL=49
Antwort von 67.220.225.50: Bytes=32 Zeit=158ms TTL=49
Antwort von 67.220.225.50: Bytes=32 Zeit=176ms TTL=49
Ping-Statistik für 67.220.225.50:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 158ms, Maximum = 176ms, Mittelwert = 165ms
C:\>tracert www.dbfinteractive.com
Routenverfolgung zu dbfinteractive.com [67.220.225.50] über maximal 30 Abschnitt
e:
1 27 ms 26 ms 26 ms lo1.br61.dus.de.hansenet.net [213.191.64.40]
2 25 ms 26 ms 25 ms ae1-102.cr02.dus.de.hansenet.net [62.109.110.126
]
3 30 ms 30 ms 46 ms so-0-1-0-0.cr02.fra.de.hansenet.net [213.191.66.
34]
4 28 ms 28 ms 51 ms ae0-101.pr01.fra.de.hansenet.net [62.109.109.176
]
5 28 ms 28 ms 29 ms fra32-hansenet-4.fra.seabone.net [89.221.34.45]
6 117 ms 119 ms 117 ms new4-new11-racc1.new.seabone.net [195.22.216.235
]
7 117 ms 117 ms 123 ms te-4-2.car3.Newark1.Level3.net [4.71.148.9]
8 122 ms 124 ms 125 ms ae-32-52.ebr2.Newark1.Level3.net [4.68.99.62]
9 122 ms 122 ms 122 ms ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101
]
10 139 ms 139 ms 139 ms ae-2-2.ebr2.Chicago2.Level3.net [4.69.132.69]
11 157 ms 150 ms 155 ms ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
12 138 ms 209 ms 141 ms ae-2-54.edge3.Chicago3.Level3.net [4.68.101.116]
13 141 ms 201 ms 167 ms BIG-PIPE-IN.edge3.Chicago3.Level3.net [4.53.96.1
10]
14 144 ms 143 ms 144 ms rc1ec-tge0-0-5-0.il.shawcable.net [66.163.65.49]
15 155 ms 155 ms 155 ms rc2sh-pos3-0.mt.shawcable.net [66.163.76.146]
16 157 ms 157 ms 169 ms 66.163.66.90
17 157 ms 159 ms 157 ms rx0sh-scratch-telecom.mt.bigpipeinc.com [66.244.
223.182]
18 216 ms 216 ms 263 ms hp17.hostpapa.com [67.220.225.50]
Ablaufverfolgung beendet.
C:\>tracert www.dbfinteractive.com
Routenverfolgung zu dbfinteractive.com [67.220.225.50] über maximal 30 Abschnitt
e:
1 26 ms 25 ms 26 ms lo1.br61.dus.de.hansenet.net [213.191.64.40]
2 25 ms 33 ms 25 ms ae1-102.cr02.dus.de.hansenet.net [62.109.110.126
]
3 28 ms 29 ms 29 ms so-0-1-0-0.cr02.fra.de.hansenet.net [213.191.66.
34]
4 30 ms 29 ms 28 ms ae0-101.pr01.fra.de.hansenet.net [62.109.109.176
]
5 29 ms 29 ms 29 ms fra32-hansenet-2.fra.seabone.net [89.221.34.25]
6 117 ms 117 ms 118 ms new4-new11-racc1.new.seabone.net [195.22.216.235
]
7 118 ms 117 ms 117 ms te-4-2.car3.Newark1.Level3.net [4.71.148.9]
8 124 ms 122 ms 133 ms ae-32-52.ebr2.Newark1.Level3.net [4.68.99.62]
9 122 ms 122 ms 122 ms ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101
]
10 139 ms 139 ms 139 ms ae-2-2.ebr2.Chicago2.Level3.net [4.69.132.69]
11 138 ms 173 ms 149 ms ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
12 138 ms 139 ms 139 ms ae-2-54.edge3.Chicago3.Level3.net [4.68.101.116]
13 164 ms 143 ms 142 ms BIG-PIPE-IN.edge3.Chicago3.Level3.net [4.53.96.1
10]
14 143 ms 146 ms 143 ms rc1ec-tge0-0-5-0.il.shawcable.net [66.163.65.49]
15 156 ms 164 ms 155 ms rc2sh-pos3-0.mt.shawcable.net [66.163.76.146]
16 158 ms 178 ms 157 ms 66.163.66.90
17 158 ms 158 ms 159 ms rx0sh-scratch-telecom.mt.bigpipeinc.com [66.244.
223.182]
18 158 ms 158 ms 159 ms hp17.hostpapa.com [67.220.225.50]
Ablaufverfolgung beendet.
C:\>ping www.dbfinteractive.com
Ping wird ausgeführt für dbfinteractive.com [67.220.225.50] mit 32 Bytes Daten:
Antwort von 67.220.225.50: Bytes=32 Zeit=155ms TTL=51
Antwort von 67.220.225.50: Bytes=32 Zeit=156ms TTL=51
Antwort von 67.220.225.50: Bytes=32 Zeit=154ms TTL=51
Antwort von 67.220.225.50: Bytes=32 Zeit=155ms TTL=51
Ping-Statistik für 67.220.225.50:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 154ms, Maximum = 156ms, Mittelwert = 155ms
C:\>ping www.dbfinteractive.com
Ping wird ausgeführt für dbfinteractive.com [67.220.225.50] mit 32 Bytes Daten:
Antwort von 67.220.225.50: Bytes=32 Zeit=155ms TTL=51
Antwort von 67.220.225.50: Bytes=32 Zeit=155ms TTL=51
Antwort von 67.220.225.50: Bytes=32 Zeit=155ms TTL=51
Antwort von 67.220.225.50: Bytes=32 Zeit=155ms TTL=51
Ping-Statistik für 67.220.225.50:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 155ms, Maximum = 155ms, Mittelwert = 155ms
C:\>tracert www.dbfinteractive.com
Routenverfolgung zu dbfinteractive.com [67.220.225.50] über maximal 30 Abschnitt
e:
1 28 ms 28 ms 28 ms lo1.br64.dus.de.hansenet.net [213.191.64.108]
2 26 ms 28 ms 27 ms ae1-102.cr02.dus.de.hansenet.net [62.109.110.126
]
3 30 ms 30 ms 30 ms so-6-1-0-0.cr02.fra.de.hansenet.net [213.191.87.
170]
4 30 ms 29 ms 30 ms ae1-102.pr01.fra.de.hansenet.net [62.109.109.240
]
5 31 ms 31 ms 31 ms fra32-hansenet-4.fra.seabone.net [89.221.34.45]
6 125 ms 124 ms 123 ms new4-new11-racc1.new.seabone.net [195.22.216.235
]
7 119 ms 133 ms 120 ms te-4-2.car3.Newark1.Level3.net [4.71.148.9]
8 124 ms 124 ms 123 ms ae-32-52.ebr2.Newark1.Level3.net [4.68.99.62]
9 123 ms 122 ms 123 ms ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101
]
10 146 ms 146 ms * ae-2-2.ebr2.Chicago2.Level3.net [4.69.132.69]
11 148 ms 145 ms 143 ms ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
12 141 ms 142 ms 142 ms ae-2-52.edge3.Chicago3.Level3.net [4.68.101.52]
13 169 ms 183 ms 148 ms BIG-PIPE-IN.edge3.Chicago3.Level3.net [4.53.96.1
06]
14 141 ms 142 ms 141 ms 66.163.65.9
15 153 ms 154 ms 154 ms rc2sh-pos3-0.mt.shawcable.net [66.163.76.146]
16 155 ms 155 ms 155 ms 66.163.66.90
17 158 ms 159 ms 159 ms rx0sh-scratch-telecom.mt.bigpipeinc.com [66.244.
223.182]
18 155 ms 157 ms 155 ms hp17.hostpapa.com [67.220.225.50]
Ablaufverfolgung beendet.
C:\>
Best regards
I am sorry, I would really like to fix the problem but I have paid for the hosting for the year and I can't afford to swap it at the moment. If the problem is with networksolutions.net as Jim points out above then that might be a problem your end anyway?
i will try to contact networksolutions.net and tell about the problems... maybe they have a solution that this problem get fixed hopefully very soon
Let us know how you get on mate, I mean it is obviously a concern for me if people cant access the site, as far as fixing it is concerned I am limited to just complaining about it for now.. Money has changed hands already, we will not be with this host this time next year though.
The problem is only with some routes - for instance my route to dbf doesn't contain seabone.net. It may only be Va!n's ISP who peers with them, or their upstream. It's impossible to tell who else is seeing these problems.
Jim
I had a similar problem with RCM a few weeks ago, I couldnt reach them at all, then all of a sudden it began working again, I don't post much there anyway but it was a bit fruistrating as I am supposedly re-writing their website for them (as soon as they have sound some gfx).
Hopefully the problems will go away for you soon too Va!n.
I had some problems tonight, site unreachable for about 10-15mins then it was back. Hope its nothing serious :)
Ive been having problems reaching the site on and off all day.
Me too. Something broke at 7.30am EST (I think that's about 10.30pm GMT). Not sure what.
Jim
yup. second that.
Same again today too.
Yup, same this morning, hostpapa or their ISP this time.
:(
Okay, well it looks like I will have to move us. This is going to cost me a fair bit of cash but more worryingly a lot of stress so please bear with me for a few weeks while I choose a better host and plan our move.
I'll probably need to put DBF offline for a couple of days while I move us to a new site, I have to chop the database up and it's fucking huge.
It's anoying that its having problems but it's one of those things that can happen, hopefully you can find a solution without losing to much to stress :)
It was a nightmare last time I moved the site tbh, and it's even more complicated this time, I was really hoping that it could be avoided, but the downtime is really pissing me off too so I have to do something.
Personally I can live with a site not always being up. Its not like I don't have other things to fill my time. So to me its not been that big of a deal that the forum was unavailable for a few hours this one time.
Seems that they had power failures....
QuoteDear HostPapa Customer,
Please be advised that on August 9 and 10, 2009, one of HostPapa’s datacentres experienced intermittent outages to both its regular and backup power supplies. This was due to a local area power blackout as a result of extreme weather conditions.
As a result of this issue, some of our customers’ servers and the main HostPapa website experienced intermittent downtime. Our System Administrators and the power company local to our datacentre worked diligently during this period to resolve the situation and get all systems and customer servers back to full operational status as quickly as possible.
HostPapa apologizes to all affected customers for any inconvenience that this intermittent power outage may have caused. Should you have any comments or inquiries about outages experienced with your own website(s) during this period, please open a support ticket at http://hostpapasupport.com and we will respond promptly.
Thank you for choosing to do business with HostPapa.
Sincerely,
The HostPapa Support Team
Hmmmm.
Give it a second chance, and see if this happens again. Today has been ok my end.
Yeah, what Clyde says. I would give them a second chance, too!
Totally agree with what Clyde and Benny say Nick .:goodpost:
Save your cash,valuable time and whole lot of stress untill its absolutely nesscessary.
The world we live in now we all expect everything to happen immediately, so having to wait to log on sometimes makes it all the more worthwhile.You certainly aprreciate this place more when you reallise you can't access it.
Keep up the good work mate.
Ok then I'll let it ride for now.. If it goes bad again I'll reconsider it. Thanks.