I have been unable to access my.openhab.org for two days. Is anyone else having a problem?
I found it very slow just now, but accessible.
Hi watou.
I’m getting ‘This page can’t be displayed’ in Internet Explorer and ‘Error the request timed out’ on my iPhone.
If I ping my.openhab.org it returns ip:176.58.106.188 but times out on every attempt.
Output from tracert below:
Tracing route to my.openhab.org [176.58.106.188]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 5 ms 5 ms 5 ms host-92-14-56-1.as43234.net [92.14.56.1]
3 6 ms 6 ms 6 ms host-78-151-238-121.as13285.net [78.151.238.121]
4 6 ms 6 ms 6 ms host-78-151-238-124.as13285.net [78.151.238.124]
5 6 ms 6 ms 6 ms host-78-144-13-147.as13285.net [78.144.13.147]
6 * * * Request timed out.
7 6 ms 6 ms 6 ms border90-01.lon2.telecity.net [85.90.226.205]
8 7 ms 6 ms 7 ms 192.168.192.6
9 * *
It looks like line 7 is is returning an internal address for the next step. Is telicity the openhab server?
Any idea what could be failing?
Roy
I just hit my.openhab.org again just now from Chrome and it returned instantly. Hard to say what the root cause might be from your end.
Is 176.58.106.188 the correct ip address for the openhab site?
I’ve sent a copy of the tracert to Telecity Group International to see if it’s a problem with one of their routers.
Would you mind posting a tracert from your location?
Despite this odd traceroute, the site is working well for me right now.
traceroute to my.openhab.org (176.58.106.188), 64 hops max, 52 byte packets
1 10.44.16.1 (10.44.16.1) 170.023 ms 167.801 ms 168.151 ms
2 198.105.216.130.static.midphase.com (198.105.216.130) 584.819 ms
198.105.216.131.static.midphase.com (198.105.216.131) 170.961 ms
198.105.216.130.static.midphase.com (198.105.216.130) 168.237 ms
3 206.130.126.13.west-datacenter.net (206.130.126.13) 169.114 ms
206.130.126.25.west-datacenter.net (206.130.126.25) 170.714 ms
206.130.126.13.west-datacenter.net (206.130.126.13) 169.270 ms
4 be4192.ccr21.slc01.atlas.cogentco.com (38.104.174.129) 169.667 ms 168.815 ms 168.313 ms
5 be2126.ccr21.den01.atlas.cogentco.com (154.54.25.65) 180.232 ms
be2127.ccr22.den01.atlas.cogentco.com (154.54.25.69) 179.878 ms
be2126.ccr21.den01.atlas.cogentco.com (154.54.25.65) 180.645 ms
6 be2128.ccr21.mci01.atlas.cogentco.com (154.54.25.174) 190.757 ms
be2130.ccr22.mci01.atlas.cogentco.com (154.54.26.122) 190.940 ms 191.347 ms
7 be2831.ccr41.ord01.atlas.cogentco.com (154.54.42.166) 202.468 ms 202.479 ms
be2832.ccr42.ord01.atlas.cogentco.com (154.54.44.170) 203.578 ms
8 be2718.ccr22.cle04.atlas.cogentco.com (154.54.7.130) 210.762 ms
be2717.ccr21.cle04.atlas.cogentco.com (154.54.6.222) 212.681 ms 213.176 ms
9 be2890.ccr42.jfk02.atlas.cogentco.com (154.54.82.246) 226.326 ms 285.823 ms
be2889.ccr41.jfk02.atlas.cogentco.com (154.54.47.50) 303.065 ms
10 be2317.ccr41.lon13.atlas.cogentco.com (154.54.30.186) 314.654 ms
be2490.ccr42.lon13.atlas.cogentco.com (154.54.42.86) 399.588 ms
be2317.ccr41.lon13.atlas.cogentco.com (154.54.30.186) 349.782 ms
11 be2869.ccr22.lon01.atlas.cogentco.com (154.54.57.162) 309.499 ms
be2871.ccr21.lon01.atlas.cogentco.com (154.54.58.186) 322.117 ms
be2868.ccr21.lon01.atlas.cogentco.com (154.54.57.154) 298.553 ms
12 be2572.rcr21.b015591-1.lon01.atlas.cogentco.com (154.54.38.106) 294.167 ms 293.196 ms
be2602.rcr21.b015591-1.lon01.atlas.cogentco.com (154.54.38.110) 302.877 ms
13 149.11.30.62 (149.11.30.62) 291.467 ms 301.688 ms 293.692 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
Hi watou,
Thanks for your help, looks like it’s a router problem for anyone accessing the site from a talktalk connection.
It’s been reported to their network team. I’ll post the result on here in case anyone looks this up in the future.
Roy
1 Like
It was tortuous getting talktalk to accept it as a problem but either they have fixed it or my previous mail to telicity got them to reboot their router.
1 Like