NetHosted Community

Hi,

Is there any issues on Titan, as it seems slow at responding, for http, imap, cPanel and WHM

_________________
Regards,
Garry
Eleven years with NetHosted (October 2016)

Hi Garry,

We're currently investigating this for you and will update you ASAP. Thanks!

Kind regards,
Brad

_________________
| Brad Dodimead
| Sales & Support Technician, NetHosted Ltd.
| Earn £30 every time you refer someone to us!
| Follow us on Twitter:
| Members, tell us what of NetHosted!

Hi,

It seems to be responded better now.
I think it could of been a routing issues, see trace routes below

If you noticed in the first one it, goes to France, Amsterdam, then back to London, according to the hostnames.

The 2nd trace route it what I am use to seeing.


C:\Users\Owner>tracert http://www.gazblog.com

Tracing route to gazblog.com [213.129.84.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms routerlogin.net [192.168.0.1]
2 * * * Request timed out.
3 8 ms 7 ms 7 ms nott-core-2a-xe-1132-0.network.virginmedia.net [
62.255.231.65]
4 * * * Request timed out.
5 * * * Request timed out.
6 12 ms 25 ms 12 ms nrth-bb-1c-ae1-0.network.virginmedia.net [62.254.42.222]
7 31 ms 33 ms 31 ms fran-ic-2-ae0-0.network.virginmedia.net [62.254.42.178]
8 30 ms 33 ms 29 ms fra-012-inter-1.interoute.net [80.81.192.9]
9 31 ms 29 ms 29 ms ae1-0.ams-koo-score-2-re0.interoute.net [84.233.190.49]
10 29 ms 29 ms 29 ms ae0-0.ams-koo-score-1-re0.interoute.net [84.233.190.1]
11 34 ms 29 ms 29 ms ae1-0.lon-001-score-1-re0.interoute.net [84.233.190.58]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * 18 ms titan.solardns.com [213.129.84.167]

Trace complete.



C:\Users\Owner>tracert http://www.gazblog.com

Tracing route to gazblog.com [213.129.84.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms routerlogin.net [192.168.0.1]
2 * * * Request timed out.
3 10 ms 8 ms 7 ms nott-core-2a-xe-1132-0.network.virginmedia.net [
62.255.231.65]
4 * * * Request timed out.
5 * * * Request timed out.
6 18 ms 13 ms 13 ms nrth-bb-1b-ae1-0.network.virginmedia.net [62.254.42.218]
7 16 ms 15 ms 15 ms tele-ic-4-ae0-0.network.virginmedia.net [62.253.174.18]
8 * * * Request timed out.
9 15 ms 15 ms 15 ms xe2-2-ve-83.thn-pe-2.thn.thebunker.net.202.88.80
.in-addr.arpa [80.88.202.138]
10 17 ms 16 ms 15 ms eth4-2.thn-bgp-1.thn.core.thebunker.net [37.200.112.58]
11 15 ms 15 ms 17 ms tengeth2-2.thn-bgp-2.thn.core.thebunker.net [213.129.95.153]
12 20 ms 18 ms 17 ms eth4-3.gc-bgp-1.gc.core.thebunker.net [37.200.112.225]
13 17 ms 17 ms 18 ms eth2-1.gc-pe-1.gc.core.thebunker.net [37.200.112.81]
14 17 ms 17 ms 17 ms gc-abr-1-b-g027.thebunker.net [37.200.112.201]
15 18 ms 17 ms 17 ms titan.solardns.com [213.129.84.167]

Trace complete.

C:\Users\Owner>

_________________
Regards,
Garry
Eleven years with NetHosted (October 2016)

Hi Garry,

Ah, I see. We're currently investigating with the datacentre into the cause of this, though I'm glad to hear it has returned back to normal now. Thanks.

Kind regards,
Brad

_________________
| Brad Dodimead
| Sales & Support Technician, NetHosted Ltd.
| Earn £30 every time you refer someone to us!
| Follow us on Twitter:
| Members, tell us what of NetHosted!