Author Topic: Anyone else experiencing a very slow site tonight? (Read 16709 times)

Yaloopy · « **Reply #20 on:** August 06, 2009 »

new4-new50-racc1.new.seabone.net [195.22.216.239] again.

I had problems last night as well.

Jim · « **Reply #21 on:** August 06, 2009 »

  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

va!n · « **Reply #22 on:** August 06, 2009 »

@jim: ah okay. thx

va!n · « **Reply #23 on:** August 07, 2009 »

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?

Code: [Select]

<!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

Shockwave · « **Reply #24 on:** August 08, 2009 »

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?

va!n · « **Reply #25 on:** August 08, 2009 »

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

Shockwave · « **Reply #26 on:** August 08, 2009 »

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.

Jim · « **Reply #27 on:** August 09, 2009 »

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

Shockwave · « **Reply #28 on:** August 09, 2009 »

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.

TinDragon · « **Reply #29 on:** August 09, 2009 »

I had some problems tonight, site unreachable for about 10-15mins then it was back. Hope its nothing serious

Clyde · « **Reply #30 on:** August 10, 2009 »

Ive been having problems reaching the site on and off all day.

Jim · « **Reply #31 on:** August 10, 2009 »

Me too. Something broke at 7.30am EST (I think that's about 10.30pm GMT). Not sure what.
Jim

benny! · « **Reply #32 on:** August 10, 2009 »

yup. second that.

Clyde · « **Reply #33 on:** August 10, 2009 »

Same again today too.

Jim · « **Reply #34 on:** August 11, 2009 »

Yup, same this morning, hostpapa or their ISP this time.

Shockwave · « **Reply #35 on:** August 11, 2009 »

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.

TinDragon · « **Reply #36 on:** August 11, 2009 »

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

Shockwave · « **Reply #37 on:** August 11, 2009 »

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.

zawran · « **Reply #38 on:** August 11, 2009 »

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.

Shockwave · « **Reply #39 on:** August 11, 2009 »

Seems that they had power failures....

Quote

Dear 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.