pink fish road repairs

Something odd is going on for sure, but it is not impacting everyone by any stretch. I had problems getting on myself this morning, but it's been fine for me since. I've contacted the hosting company support, but they are not seeing any issue so far. My suspicion is that it's an IP routing issue somewhere.

If you are having issues could you please try opening a Terminal window (Mac) or CMD window / DOS prompt (Windows) and try the following:

ping www.pinkfishmedia.net

If it comes up 'request timed out' or somesuch it is an IP related issue as the server is currently alive and kicking and has about 200 pfm members logged in (which is a little less than usual, but only down 50-75 or so on this time of night). Hit 'ctrl-C' to stop the ping command if it just keeps on going.

If the above 'request timed out' thing is the case could you next try running:

(Mac) traceroute www.pinkfishmedia.net

(PC) tracert www.pinkfishmedia.net

and cut and paste the results here.

I'd like to see if / where the traceroute is failing.

Many thanks.

Tony.
 
Here you go !

Tracing route to pinkfishmedia.net [208.84.117.46]

over a maximum of 30 hops:



1 1 ms 1 ms <1 ms 192.168.0.1

2 40 ms 26 ms 26 ms cr0.ndcan.uk.easynet.net [87.87.251.88]

3 22 ms 23 ms 23 ms ip-87-87-160-129.easynet.co.uk [87.87.160.129]

4 27 ms 26 ms 25 ms te0-1-0-5.er10.enslo.ov.easynet.net [89.200.135.91]

5 33 ms 33 ms 33 ms prs-b7-link.telia.net [213.248.89.117]

6 34 ms 36 ms 35 ms prs-bb1-link.telia.net [80.91.245.30]

7 34 ms 35 ms 35 ms prs-b2-link.telia.net [80.91.245.19]

8 115 ms 216 ms 215 ms global-124046-prs-b2.telia.net [213.248.98.122]

9 * * * Request timed out.

10
 
Thanks for that. Your route is very different to mine (which is working):

1 192.168.0.1 (192.168.0.1) 2.958 ms 1.512 ms 1.430 ms
2 host82-14-174-3.not-set-yet.ntli.net (82.14.174.3) 17.202 ms 17.517 ms 17.061 ms
3 host82-14-172-65.not-set-yet.ntli.net (82.14.172.65) 16.979 ms 17.014 ms 16.923 ms
4 host82-14-174-97.not-set-yet.ntli.net (82.14.174.97) 16.701 ms 18.293 ms 17.132 ms
5 manc-core-1a-ge-410-0.network.virginmedia.net (86.28.65.49) 17.049 ms 16.924 ms 17.360 ms
6 manc-bb-1a-as0-0.network.virginmedia.net (213.105.175.1) 18.175 ms 16.742 ms 16.915 ms
7 manc-bb-1b-ae0-0.network.virginmedia.net (62.253.187.178) 17.358 ms 16.846 ms 16.166 ms
8 te-4-3.ar3.cdg2.gblx.net (204.246.200.177) 38.133 ms 33.768 ms 34.282 ms
9 64.210.15.138 (64.210.15.138) 170.312 ms 171.169 ms 170.553 ms
10 eclipse.hosting4less.com (208.84.117.46) 170.231 ms !Z 170.507 ms !Z 170.617 ms !Z

I suspect this means there is a router table error at telia.net, though why I do not know. I also have no idea what if anything I can do to fix it. I've let pfm's hosting company know and pointed them to this thread, but it's pretty clear that the issue is external to them, i.e. there is a route failure between your ISP and them. IP has a way of fixing itself so hopefully it will realign with time, certainly mine was broken this morning, and now is fixed, and neither I nor the hosting company have done anything...

Tony.

PS Telia [213.248.98.122] is in Sweden, so why it's falling over there is beyond me.
 
Been buggered for me all day as well....

Excuse the ping time, i've got a heavy download running in the background....


1 (192.168.0.1) 5.185 ms 3.724 ms 3.649 ms
2 cr0.nslng.uk.easynet.net (87.87.252.17) 306.727 ms 270.924 ms 235.299 ms
3 ip-87-87-169-97.easynet.co.uk (87.87.169.97) 287.106 ms 258.246 ms 257.314 ms
4 te0-6-0-0.er10.enslo.ov.easynet.net (89.200.135.83) 314.090 ms 261.959 ms 198.860 ms
5 prs-b7-link.telia.net (213.248.89.117) 276.549 ms 256.304 ms 232.404 ms
6 prs-bb1-link.telia.net (80.91.252.141) 292.989 ms
prs-bb1-link.telia.net (80.91.249.36) 319.898 ms
prs-bb2-link.telia.net (80.91.250.57) 316.988 ms
7 prs-b2-link.telia.net (80.91.246.243) 314.961 ms 339.790 ms 352.481 ms
8 global-124046-prs-b2.telia.net (213.248.98.122) 323.941 ms
208.178.58.57 (208.178.58.57) 277.814 ms 579.550 ms
9 * * *
10 * * *
 
Actually it might be easynet, who seem to host quite a lot of the sky broadband service.

it seems to be that they are routing it out of the country to telia for no sensible reason.


Is it by chance all the sky customers who are being routed to the broken link screen?
 
Doug, you seem to be getting a hop further, 208.178.58.57 is in Phoenix AZ, so at least that's in the same country as pfm's server (which is in California).

It would certainly be interesting to know which ISPs are having the issue. I'm on Virgin ADSL and it's currently working fine.

Tony.

PS If anyone knows how to fix this / who to shout at please let me know!
 
Yup, i'm with Sky. Seems to be working a-ok this morning.....hopefully whatever was up with it is now fixed!
 
Doug, could you please post a traceroute now it's working for you, I'm curious to see if it's now taking a completely different path. I've still got people with problems getting to the site and I'm no closer to understanding why or finding who's responsibility it is to fix it.

Tony.
 
Isn't it clever to understand how the internet works, and there for me I was just thinking it was a form of magic ;)

Just my little joke, but it seems to me you need to join sat nav technology to internet routing :D I would hate to end up in Sweden if I was trying to get to California.

Best of luck finding a cure.

PS - I have no trouble getting in, even though I am not a member ;-))
 
I'm in today Tony, and I am a Sky Customer. I'm not savvy enough to do that techie thingie you asked for though...:o
 
Thanks Alan, that's excellent news. I'm hoping the issue has resolved itself for everyone now. Routers are meant to self-recover from these things, but as we've seen it can take an annoying amount of time for things to propagate.

Tony.
 
back on for me too.

Tracing route to pinkfishmedia.net [208.84.117.46]

over a maximum of 30 hops:



1 1 ms 1 ms <1 ms 192.168.0.1

2 55 ms 33 ms 32 ms cr0.ndcan.uk.easynet.net [87.87.251.88]

3 23 ms 22 ms 24 ms ip-87-87-160-129.easynet.co.uk [87.87.160.129]

4 27 ms 26 ms 26 ms te0-1-0-5.er10.enslo.ov.easynet.net [89.200.135.91]

5 33 ms 36 ms 34 ms prs-b7-link.telia.net [213.248.89.117]

6 34 ms 34 ms 34 ms prs-bb1-link.telia.net [80.91.245.30]

7 34 ms 34 ms 34 ms prs-b2-link.telia.net [80.91.245.19]

8 33 ms 32 ms 32 ms global-124046-prs-b2.telia.net [213.248.98.122]

9 178 ms 182 ms 178 ms 64.210.15.138

10 175 ms 176 ms 178 ms eclipse.hosting4less.com [208.84.117.46]



Trace complete.
 

Latest posts

Back
Top