I noticed today that Mediacom is not able to access frontier.com from Ames, IA.
This is similar to the problem noted by poolShark at http://www.dslreports.com/forum/r29264007-Site-not-responding. I had a similar problem last year.
Here is a trace route from the Mediacom connection:
Tracing route to frontier.com [66.133.172.205]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 8 ms 9 ms 10.154.104.1
3 13 ms 13 ms 11 ms 172.30.68.97
4 11 ms 12 ms 16 ms 172.30.1.145
5 60 ms 52 ms 51 ms 12.250.192.101
6 26 ms 29 ms 24 ms cr2.kc9mo.ip.att.net [12.122.150.206]
7 26 ms 30 ms 27 ms cr2.sl9mo.ip.att.net [12.122.28.90]
8 28 ms 25 ms 24 ms cr2.cgcil.ip.att.net [12.122.2.21]
9 23 ms 23 ms 22 ms ggr2.cgcil.ip.att.net [12.122.132.141]
10 23 ms 25 ms 26 ms 12.250.102.30
11 50 ms 50 ms 51 ms ae2---0.cor01.chcg.il.frontiernet.net [74.40.4.1
37]
12 50 ms 51 ms 50 ms ae1---0.cor02.roch.ny.ny.frontiernet.net [74.40.
5.21]
13 50 ms 52 ms 52 ms ae1---0.car03.roch.ny.frontiernet.net [74.40.1.1
06]
14 49 ms 52 ms 49 ms 50.121.70.129
15 * * * Request timed out.
poolShark noted that the node which did not respond resolves to 50.121.70.226. This node does not respond to a ping from my PC:
Pinging 50.121.70.226 with 32 bytes of data:
Request timed out.
Mediacom techs asserted to poolShark that this was an intermittent problem within Frontier's system. That may be, but it is a problem that appears specific to routing from Mediacom.
↧