Web Hosting Talk : Web Hosting Main Forums : Industry Announcements : Providers and Network Outages and Updates : FluidHosting.com down?

[ComputerBob]

I've been unable to reach FluidHosting.com, either of my 2 domains that are hosted there, or any of my email accounts there for at least the past 7 or 8 hours. They may have been unreachable for a lot longer than that, but I didn't try to reach them overnight last night.

Pings show "Unknown host fluidhosting.com" or "Request timed out."

Traceroutes give me the following results:

Tracing route to fluidhosting.com [66.150.201.71]
over a maximum of 30 hops:

1 190 ms 175 ms 173 ms REMOVED FOR SECURITY
2 180 ms 179 ms 175 ms REMOVED FOR SECURITY
3 177 ms 172 ms 169 ms REMOVED FOR SECURITY
4 179 ms 171 ms 172 ms tpa10-core1-g2-0.atlas.algx.net [165.117.177.1]

5 220 ms 218 ms 218 ms atl10-core2-so-6-2-0-0.atlas.algx.net [165.117.6
8.185]
6 205 ms 230 ms 229 ms dca10-core1-so-7-0-0-0.atlas.algx.net [165.117.2
00.6]
7 233 ms 194 ms 227 ms dca10-core3-g2-0.atlas.algx.net [165.117.175.197
]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.

.... on and on and on.

I can't tell if FluidHosting.com is down, or if there's a bad router somewhere between me and the FluidHosting servers.

Can anyone else here reach either FluidHosting.com or my Web site?

[mainarea]

Target Name: FluidHosting.com
IP: 66.150.201.71
Date/Time: 3/29/2004 5:26:59 PM

1 1 ms 1 ms [192.168.0.1]
2 12 ms 12 ms [10.113.72.1]
3 13 ms 11 ms fe-2-8-rr01.ebrunswick.nj.nj02.comcast.net [68.87.48.61]
4 13 ms 13 ms srp-8-1-ar01.plainfield.nj.nj02.comcast.net [68.87.48.193]
5 12 ms 11 ms pos-7-1-cr01.plainfield.nj.core.comcast.net [68.87.19.249]
6 15 ms 13 ms [12.119.12.13]
7 14 ms 14 ms tbr2-p012402.n54ny.ip.att.net [12.123.219.133]
8 14 ms 11 ms ggr1-p370.n54ny.ip.att.net [12.123.1.125]
9 13 ms 17 ms p4-0.att.nwrknj01.us.bb.verio.net [192.205.32.242]
10 18 ms 15 ms p16-0-1-1.r20.nycmny01.us.bb.verio.net [129.250.2.217]
11 60 ms 31 ms p16-2-0-0.r00.bstnma01.us.bb.verio.net [129.250.5.25]
12 35 ms 20 ms ge-0-0-0.a00.bstnma01.us.ra.verio.net [129.250.27.225]
13 69 ms 22 ms so-0-2-1.a00.bstnma01.us.ce.verio.net [199.103.138.42]
14 50 ms 28 ms border8.ge1-1-bbnet1.bsn.pnap.net [63.251.128.13]
15 28 ms 22 ms fluidhosting-1.border7-8.bsn.pnap.net [66.150.201.250]
16 56 ms 21 ms fluidhosting.com [66.150.201.71]

Works from my cable line & 2 servers (PA and TX).

- Matt

[ComputerBob]

Thanks! That was a big help!

With that info in mind, I tried using a different access number for my ISP (also local, but in a different town) and I was instantly able to reach my site, email, etc.

Here's the Traceroute from the different access number:

Tracing route to fluidhosting.com [66.150.201.71]
over a maximum of 30 hops:

1 179 ms 176 ms 173 ms REMOVED
2 175 ms 178 ms 174 ms REMOVED
3 180 ms 121 ms 115 ms REMOVED
4 178 ms 171 ms 172 ms REMOVED
5 199 ms 134 ms 193 ms atm9-0.6.atlngapk22w.cr.deltacom.net [66.35.174.
41]
6 195 ms 189 ms 192 ms acr2-so-6-1-0.atlanta.cw.net [208.172.65.169]
7 204 ms 205 ms 199 ms agr3-loopback.atlanta.cw.net [208.172.66.103]
8 200 ms 141 ms 194 ms dcr1-so-0-2-0.atlanta.cw.net [208.172.75.9]
9 225 ms 219 ms 179 ms acr1-loopback.boston.cw.net [208.172.50.61]
10 361 ms 226 ms 223 ms 208.172.51.54
11 266 ms 220 ms 221 ms internap.boston.cw.net [208.172.49.138]
12 231 ms 227 ms 218 ms border8.ge1-1-bbnet1.bsn.pnap.net [63.251.128.13
]
13 225 ms 222 ms 220 ms fluidhosting-1.border7-8.bsn.pnap.net [66.150.20
1.250]
14 240 ms 221 ms 225 ms fluidhosting.com [66.150.201.71]

Trace complete.

That's really strange. My ISP's two local access numbers are using two totally different routes to get to FluidHosting. Now I have to decide whether I want to wait on hold for 30 minutes to call them and try to explain the problem to them.

[rusko]

it looks like allegiance is/was dropping your packets, bob. how very characteristic of them. maybe XO will fix it, but given how long XO takes to do things..

in short, fluidhosting/internap were not down. something on *your* route to them was. stick with the new access number =]

paul

[ComputerBob]

Thanks, Paul!

[bsaunder]

Its not just you - I have Qwest DSL and T1 and are not able to reach fluidhosting.com or any of my sites.

Ping comes up with request timed out

[FHDave]

bsaounder,

Which of your website is not coming up? We are currently working on our control panel / main website server. None of the other servers (database, email, web) are affected.

[bsaunder]

Originally posted by FHDave
bsaunder,

Which of your website is not coming up? We are currently working on our control panel / main website server. None of the other servers (database, email, web) are affected.

Ok - its all back up now other than fluidhosting.com. Also just got a note from Qwest saying they had some issues that were just resolved - I'm sure it was a local issue and not a fluidhosting issue.