Tracing route to
www.costaricaticas.com [72.52.194.157]
1 <1 ms <1 ms <1 ms 10.101.10.1
2 * * * Request timed out.
3 16 ms 68 ms 14 ms xe-8-0-0-32767-sur03.pompanobeach.fl.pompano.comcast.net [68.85.83.233]
4 18 ms 19 ms 14 ms te-0-1-0-3-ar03.northdade.fl.pompano.comcast.net [68.87.162.249]
5 34 ms 35 ms 18 ms he-2-9-0-0-cr01.miami.fl.ibone.comcast.net [68.86.94.253]
6 33 ms 50 ms 31 ms pos-0-10-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.88.217]
7 77 ms 50 ms 51 ms he-2-11-0-0-cr01.chicago.il.ibone.comcast.net [68.86.89.5]
8 103 ms 51 ms 51 ms he-1-3-0-0-cr01.350ecermak.il.ibone.comcast.net[68.86.88.30]
9 51 ms 49 ms 49 ms be-11-pe03.350ecermak.il.ibone.comcast.net [68.86.84.102]
10 53 ms 49 ms 50 ms 66.208.216.86
11 59 ms 56 ms 75 ms lw-dc2-core6-te9-2.rtr.liquidweb.com [209.59.157.226]
12 73 ms 58 ms 57 ms lw-dc2-core4-ge2-16.rtr.liquidweb.com [209.59.157.110]
13 59 ms 59 ms 57 ms lw-dc2-sec1-dist2-po2.rtr.liquidweb.com [209.59.157.130]
14 61 ms 58 ms 58 ms pluto.hosting-pp.com [72.52.194.157]
Trace complete.
I've been monitoring this for the past few days. There is a routing delay in liquidweb, which must be the principal provider for the site. Step 2 is where my provider is attempting to compute a routing path and is getting delays from the assigned gateway. I am seeing it for other liquidweb customers as well.
They are probably repairing something internal. If the site is hosted on a VM, then it could be a rolling upgrade of the environment.
We'll just have to wait and see.