Taperssection.com
Gear / Technical Help => Post-Processing, Computer / Streaming / Internet Devices & Related Activity => Topic started by: Fatah Ruark (aka MIKE B) on July 06, 2014, 08:31:26 PM
-
This starting happening last night. Thought the server was just getting hammered from phish's set...but it hasn't come up yet. According to: http://www.downforeveryoneorjustme.com/phish.net ...the site is up.
Looks like I am able to make it part of the way there when using www.phish.net . Also I can get all the way there if I enter the ip address. If I use http://198.58.123.117 I get a login pop up. If I use https://198.58.123.117 I can get the site to come up (without the css so it's pretty ugly) but it's useless after that because the links all use phish.net/xxxxx as the address.
Any idea what the problem might be? Seems strange that I get nothing with the URL, but I can reach the IP (but only really by https).
It looks like when I use phish.net I get stuck at a networklayer.com which appears to be owned by Softlayer which is owned by IBM. Could it be a problem with one of their routers? 66.228.118.182 appears to be the culprit with phish.net...but it doesn't seem to go through that IP when I use phish.net's IP address.
The other thing I noticed is when I enter tracert phish.net it shows 75.126.168.185 as the IP (which I'm assuming is what the nameserver I hit returns). Could that be a problem?
I should know more about this since I work in telecom...but I don't really do a lot of IP related work (pretty much only helping customers with my minimal knowledge).
Here is the traceroute from phish.net:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mike>tracert phish.net
Tracing route to phish.net [75.126.168.185]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 9 ms 8 ms c-76-120-96-1.hsd1.co.comcast.net [76.120.96.1]
3 9 ms 8 ms 8 ms xe-10-1-0-32767-sur03.arvada.co.denver.comcast.n
et [68.85.107.189]
4 10 ms 10 ms 9 ms ae-21-0-ar01.denver.co.denver.comcast.net [68.86
.179.57]
5 10 ms 10 ms 10 ms ae-10-0-ar01.aurora.co.denver.comcast.net [68.86
.179.154]
6 10 ms 15 ms 15 ms he-3-9-0-0-cr01.denver.co.ibone.comcast.net [68.
86.92.21]
7 11 ms 10 ms 10 ms xe-3-0-1-0-pe01.910fifteenth.co.ibone.comcast.ne
t [68.86.82.30]
8 11 ms 10 ms 14 ms xe-0-0-0.bbr01.cf01.den01.networklayer.com [75.1
49.228.102]
9 25 ms 25 ms 24 ms ae12.bbr02.eq01.dal03.networklayer.com [173.192.
18.138]
10 25 ms 26 ms 26 ms ae1.dar02.sr01.dal01.networklayer.com [173.192.1
8.213]
11 26 ms 26 ms 25 ms po2.fcr02.sr04.dal01.networklayer.com [66.228.11
8.182]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Here is the traceroute from the IP address for phish.net:
C:\Windows\system32>tracert 198.58.123.117
Tracing route to ln17.endpoint.com [198.58.123.117]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 16 ms 9 ms 8 ms c-76-120-96-1.hsd1.co.comcast.net [76.120.96.1]
3 8 ms 8 ms 8 ms xe-10-1-0-32767-sur03.arvada.co.denver.comcast.n
et [68.85.107.189]
4 11 ms 11 ms 10 ms ae-21-0-ar01.denver.co.denver.comcast.net [68.86
.179.57]
5 10 ms 10 ms 9 ms ae-10-0-ar01.aurora.co.denver.comcast.net [68.86
.179.154]
6 13 ms 11 ms 11 ms te-1-1-0-4-cr01.chicago.il.ibone.comcast.net [68
.86.95.205]
7 10 ms 10 ms 11 ms xe-4-0-1-0-pe01.910fifteenth.co.ibone.comcast.ne
t [68.86.82.182]
8 12 ms 11 ms 11 ms xe-0-0-0.bbr01.cf01.den01.networklayer.com [75.1
49.228.102]
9 53 ms 47 ms 51 ms ae12.bbr02.eq01.dal03.networklayer.com [173.192.
18.138]
10 25 ms 26 ms 26 ms po32.dsr02.dllstx3.networklayer.com [173.192.18.
231]
11 25 ms 25 ms 25 ms po32.dsr02.dllstx2.networklayer.com [70.87.255.7
0]
12 25 ms 25 ms 25 ms po2.car02.dllstx2.networklayer.com [70.87.254.86
]
13 25 ms 25 ms 25 ms router2-dal.linode.com [67.18.7.94]
14 25 ms 26 ms 26 ms ln17.endpoint.com [198.58.123.117]
Trace complete.
-
It loaded right away for me just now. I'm in Raleigh.
-
mines been intermittent.
-
Maybe Verizon is trying to squeeze some protection money out of them
-
Maybe Verizon is trying to squeeze some protection money out of them
fair enough, I'm on a Verizon backbone...
-
phish.net definitely has an A record of 198.58.123.117:
;; ANSWER SECTION:
phish.net. 600 IN A 198.58.123.117
traceroute from my solaris VPS completes:
[root@joynetmicro ~]# traceroute phish.net
traceroute to phish.net (198.58.123.117), 30 hops max, 40 byte packets
1 72.2.112.3 (72.2.112.3) 0.261 ms 72.2.112.2 (72.2.112.2) 0.213 ms 72.2.112.3 (72.2.112.3) 0.228 ms
2 165.225.143.14 (165.225.143.14) 0.234 ms 165.225.143.16 (165.225.143.16) 0.234 ms 165.225.143.10 (165.225.143.10) 0.223 ms
3 165.225.143.102 (165.225.143.102) 1.558 ms 165.225.143.106 (165.225.143.106) 11.973 ms 8.388 ms
4 border11.ge10-3.joyent-3.wdc002.pnap.net (66.150.126.201) 0.361 ms 0.335 ms 0.331 ms
5 core1.te5-1-bbnet1.wdc002.pnap.net (216.52.127.7) 0.687 ms 0.644 ms core1.te5-2-bbnet2.wdc002.pnap.net (216.52.127.71) 0.726 ms
6 xe-0-2-0-10.r04.asbnva02.us.bb.gin.ntt.net (168.143.97.169) 0.713 ms 0.662 ms 0.711 ms
7 ae-3.r05.asbnva02.us.bb.gin.ntt.net (129.250.7.9) 0.963 ms 0.691 ms 0.799 ms
8 ae14.bbr02.eq01.wdc02.networklayer.com (168.143.97.102) 0.546 ms 0.905 ms 0.490 ms
9 ae7.bbr01.eq01.wdc02.networklayer.com (173.192.18.194) 0.785 ms 1.344 ms 1.100 ms
10 ae0.bbr01.tl01.atl01.networklayer.com (173.192.18.153) 12.882 ms * 12.963 ms
11 ae13.bbr02.eq01.dal03.networklayer.com (173.192.18.134) 32.516 ms 32.435 ms 33.375 ms
12 po32.dsr01.dllstx3.networklayer.com (173.192.18.229) 33.770 ms 34.676 ms 34.096 ms
13 po32.dsr02.dllstx2.networklayer.com (70.87.255.70) 34.570 ms 33.944 ms po31.dsr01.dllstx2.networklayer.com (70.87.255.66) 34.268 ms
14 po1.car02.dllstx2.networklayer.com (70.87.254.82) 34.728 ms po2.car02.dllstx2.networklayer.com (70.87.254.86) 33.929 ms 34.357 ms
15 router1-dal.linode.com (67.18.7.90) 33.740 ms router2-dal.linode.com (67.18.7.94) 34.278 ms router1-dal.linode.com (67.18.7.90) 33.851 ms
16 ln17.endpoint.com (198.58.123.117) 32.834 ms 32.555 ms 33.889 ms
do you have a smart phone? do you have wifi? what happens with you access phish.net from your smart phone on and off wifi?
-
No problem getting there on the smartphone.
I suspect I'm just going to have to wait this out until someone fixes their router.
-
UPDATE:
Did a hard reset on my router. All is well now.
Very strange that when I did the traceroute that I made it out past Comcast and then stalled. You would think if it was a problem with my router I wouldn't get any sites. I couldn't get to phish.net or strava.com (records bike GPS routes). Could have been some other sites but only found 2. No trouble getting here or any other sites I use on a regular basis. Glitch in the matrix I guess.
I'll have to hit up one of the IP experts at work to figure out what really happened.