Hi guys…
JodoHost is running REALLY slow or failign to connect from here… pings are > 4000ms! The forums are slow, my sites are slow or not connecting.
I’ve tried pinging other hosts in Florida, all are pinging around 300ms which is normal from here (Perth, Oz)
What’s going on?!
I have not been noticing an issues at all nor has any issues been reported to us from australia
Please send us a traceroute in a ticket and try using a different ISP
Pardon me, but I’ve just reported one. Here, and in a ticket.
I can ping other hosts in Florida without any issue. In fact one of the hosts I pinged uses the same DC as you. The only problem is when pinging JodoHost.
I’ll send you a tracert. Sorry, but I’m not very happy with that response, it sounds rather dismissive. I’m having big problems accessing JodoHost and client sites, and would like you to investigate the issue.
pings from here in central texas are all about 50ms.
Tracert follows:
1 1 ms 1 ms 1 ms 192.168.0.254
2 31 ms 30 ms 30 ms nexthop.wa.iinet.net.au [203.59.14.16]
3 30 ms 34 ms 34 ms Gi2-0-0-7.per-qv1-bdr2.chime.net.au [203.59.49.176]
4 33 ms 31 ms 31 ms GigabitEthernet3-2.qvb1.lnk.telstra.net [139.130.25.37]
5 30 ms 31 ms 31 ms GigabitEthernet7-0.wel-core3.Perth.telstra.net [203.50.115.129]
6 61 ms 61 ms 63 ms Pos-channel2.way-core4.Adelaide.telstra.net [203.50.6.193]
7 73 ms 70 ms 73 ms Pos5-0.exi-core1.Melbourne.telstra.net [203.50.6.161]
8 86 ms 88 ms 88 ms Pos15-0.chw-core2.Sydney.telstra.net [203.50.6.37]
9 85 ms 85 ms 85 ms 10GigabitEthernet1-0.oxf-core1.Sydney.telstra.net [203.50.6.2]
10 88 ms 87 ms 84 ms 10GigabitEthernet2-2.syd-core03.Sydney.net.reach.com [203.50.13.30]
11 86 ms 86 ms 87 ms i-7-0.syd-core04.net.reach.com [202.84.221.86]
12 86 ms 85 ms 86 ms i-5-0.syd-core02.net.reach.com [202.84.144.249]
13 234 ms 233 ms 235 ms i-0-0.wil-core02.net.reach.com [202.84.144.101]
14 236 ms 236 ms 235 ms i-6-2.wil04.net.reach.com [202.84.251.186]
15 * * 1160 ms reach.ar1.LAX2.gblx.net [208.50.13.237]
16 3997 ms 1242 ms * so2-0-0-2488M.ar2.MIA1.gblx.net [67.17.67.114]
17 * 1110 ms 3963 ms 69.28.191.90
18 1099 ms 3908 ms 1077 ms 204.14.107.232
Looks like the bottleneck is at Global Crossing… ping to REACH is ok, ping to GBLX is crap…
Is Global Crossing any good? How come Jodo doesn’t use Cogent? The other sites I can get to in Florida seem to use Cogent…
The issue seems with your route at the gblx.net router. They are probably having some issues. I am forwarding this to the NOC so that we can try doing whatever they can to expedite a resolution from our side.
But otherwise this is completely out of our control
Ouch Los Angeles to Miami looks bad, hopefully it will get resolved automatically.
Pings from England average 119ms
[QUOTE=BluJag]
Pings from England average 119ms
[/QUOTE]
It’s not polite to gloat. 
ahhh these things are so frustrating. Isn’t the internet supposed to work even after a nuclear bomb or something?
Sorry for pointing at Jodo.. obviously not their problem… all the other hosts I pinged go thru Cogent, which is working fine. From here to Jodo I go thru Global Crossing for some reason.
How many providers is Jodo connected with? Isn’t there supposed to be some redundancy in place?
Oh definately there is redundancy. If global crossing went totally down, you’d be routed differently. But since they are up and are having issues.. and you are being routed by them you are having issues too..
We are doing everything we can from here to resolve this issue at the soonest
Antic, it uses BGP, but sometimes when it is outside our realm of control it does not detect any issues.
And for Cogent, it is not considered good bandiwdth in many circles, and we don’t currently utilize it for the JH services, we will have it in the mix once we get to NAP