Verizon / FiOS network

Mailman List Mirror (Read Only)
1

Hi,

Anyone noticing anything weird with the Verizon / FiOS network?

Seems like many people on their network are having trouble getting to us
(on Sidera / RCN) but not everyone.

Traceroutes appear sane, so just wondering if anyone else is running into
similar troubles.

Ryan

2

it's, obviously, simpler to help diagnose this when you provide some
semblance of destination address, port, protocol...

just sayin'!

-chris
(fios user who could help, if only there was enough info to go on)

3

HTTP/HTTPS over 80, 443. Sample IP: 146.115.38.21

4

Not able to connect to 146.115.38.21 via fios or verizon 3g so the problem doesn't seem to be fios specific.

5

From FiOS and non-FiOS locations I get the same result:

HTTP: timeout
HTTPS: connects and loads (Zimbra webmail page)
also can ping via ICMP just fine

Traceroute from fios is via Level3 from the DC area to Boston where it is handed off to RCN and then 2 hops to the destination

6

HTTP doesnt appear to be open from any network I try Verizon or otherwise so
I'm not sure its network related

7

Firewalled at or near 146.115.38.21. It allows ICMP, TCP 25 and TCP
443 but not TCP 80.

[lily:kroot:/home/kroot:!] traceroute -T -p 25 146.115.38.21
traceroute to 146.115.38.21 (146.115.38.21), 30 hops max, 40 byte packets
1 L300.WASHDC-VFTTP-91.verizon-gni.net (173.73.47.1) 1.295 ms
0.989 ms 1.111 ms
2 G0-3-4-3.WASHDC-LCR-22.verizon-gni.net (130.81.48.122) 1.431 ms
1.838 ms 1.533 ms
3 so-3-1-0-0.RES-BB-RTR2.verizon-gni.net (130.81.151.232) 1.580 ms
1.628 ms 1.601 ms
4 0.ae2.BR1.IAD8.ALTER.NET (152.63.32.158) 3.524 ms 3.716 ms 3.448 ms
5 * * *
6 vlan52.ebr2.Washington12.Level3.net (4.69.146.222) 2.449 ms
3.238 ms 2.441 ms
7 4.69.148.49 (4.69.148.49) 9.562 ms 9.403 ms 9.354 ms
8 ae-1-8.bar2.Boston1.Level3.net (4.69.140.97) 14.749 ms 14.622 ms
14.627 ms
9 RCN-CORPORA.bar2.Boston1.Level3.net (4.53.50.14) 17.960 ms
17.906 ms 17.924 ms
10 port-chan8.aggr1.sbo.ma.rcn.net (207.172.15.151) 18.603 ms
18.589 ms 18.866 ms
11 207.172.19.247 (207.172.19.247) 13.466 ms 13.524 ms 13.580 ms
12 webmail.tripadvisor.com (146.115.38.21) 17.950 ms 17.897 ms 17.935 ms

[lily:kroot:/home/kroot:!] traceroute -T -p 80 146.115.38.21
traceroute to 146.115.38.21 (146.115.38.21), 30 hops max, 40 byte packets
1 L300.WASHDC-VFTTP-91.verizon-gni.net (173.73.47.1) 2.072 ms
1.712 ms 1.506 ms
2 G0-3-4-3.WASHDC-LCR-22.verizon-gni.net (130.81.48.122) 2.180 ms
1.991 ms 2.021 ms
3 so-3-1-0-0.RES-BB-RTR2.verizon-gni.net (130.81.151.232) 1.693 ms
1.479 ms 1.676 ms
4 0.ae2.BR1.IAD8.ALTER.NET (152.63.32.158) 3.441 ms 3.616 ms 3.426 ms
5 * * *
6 vlan52.ebr2.Washington12.Level3.net (4.69.146.222) 2.415 ms
2.994 ms 2.729 ms
7 4.69.148.49 (4.69.148.49) 9.822 ms 9.314 ms 9.478 ms
8 ae-1-8.bar2.Boston1.Level3.net (4.69.140.97) 14.695 ms 14.982 ms
14.598 ms
9 RCN-CORPORA.bar2.Boston1.Level3.net (4.53.50.14) 18.395 ms
18.315 ms 18.179 ms
10 port-chan8.aggr1.sbo.ma.rcn.net (207.172.15.151) 18.366 ms
18.476 ms 18.511 ms
11 207.172.19.247 (207.172.19.247) 13.857 ms 14.040 ms 13.508 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 *^C

8

My original email wasn't too clear. This host specifically does not allow
80, but does allow 443. What I was trying to explain is that we are
seeing the issue occur on several hosts on both 80 and 443.

Sorry for the confusion.

Ryan