| [northeast] Verizon FiOS webmail I live in the Herndon VA area. I access my Verizon FiOS email via webmail.verizon.net. For the last couple of days the Verizon webmail response has been very slow. Speeds to other web sites are OK. The slow webmail occurs on my other PC at home too, so I don't think it is PC related. Anyone else having this problem? |
|
| Also, YouTube downloads are very slow too! |
|
 NY TelPremium
join:2004-04-09
Smithtown, NY
kudos:3
 ·AT&T CallVantage
| reply to HerbW
said by HerbW :
I live in the Herndon VA area. I access my Verizon FiOS email via webmail.verizon.net. For the last couple of days the Verizon webmail response has been very slow. Speeds to other web sites are OK. The slow webmail occurs on my other PC at home too, so I don't think it is PC related. Anyone else having this problem?
I find that the entire mail program is slow so I use GMAIL but if you must use the VZ mail, why not use a pop3 email program such as Outlook, Outlook Express, Windows Live Mail, Thunderbird etc.......
--
Love when you can - cry when you have to, be who you must, that's a part of the plan, await your arrival with simple survival and one day we'll all understand... |
|
 Smith6612Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:21 | reply to HerbW
Can you show us a speed test from www.speedtest.net and run a trace route to google.com for us? |
|
|
|
| »www.speedtest.net/result/340913989.png
C:\>tracert google.com
Tracing route to google.com [209.85.171.99]
over a maximum of 30 hops:
1 |
|
Smith6612Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:21 | Your speed test is showing the same slow speeds that other people have been getting around this site. Can you give us the first digit if your IP address like 172.***.***.***? |
|
HerbW
join:2008-10-18
Herndon, VA | Here's first few lines from trace route that was missing.
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 2 ms 1 ms 1 ms 96.231.199.1
3 3 ms 3 ms 2 ms G11-1-661.LCR-06.WASHDC.verizon-gni.net [130.81.
104.180]
4 3 ms 3 ms 3 ms P15-3.LCR-01.PTLDOR.verizon-gni.net [130.81.28.1
46] |
|
2 edits | reply to HerbW
There is a backbone router down in Vienna, VA. Run Internet Traffic Report (www.internettrafficreport.com/namerica.htm) to see its status.
I live near Herndon and have had the same problem for 3 days. Any traffic through that router gets rerouted and delayed. Traffic which doesn't use that router, like to New York, doesn't have a slowdown. Upload speeds do not seem to be affected. |
|
 birdfeedrPremium,MVM
join:2001-08-11
Warwick, RI
kudos:5
1 edit | said by heritageguy:There is a backbone router down in Vienna, VA. Run Internet Traffic Report (www.internettrafficreport.com/namerica.htm) to see its status. I'm curious, and asking because I don't know.
How do you know it's a backbone router, and that that particular router outage is causing issues with traffic in the mid-Atlantic area?
Is that router outage causing the FiOS webmail problem, subject of the OP? And why don't they just fix it already?
The router's URL points to 207.254.32.14 and whois says it belongs to Amerion. How are they connected to Verizon?
Added: Amerion.com and bossig.com point to the same outfit. Amerion looks like they are a dial-up ISP. |
|
birdfeedrPremium,MVM
join:2001-08-11
Warwick, RI
kudos:5 | reply to Smith6612
Why traceroute to google? Makes more sense to traceroute to webmail.verizon.net
Report: TraceRoute
Generated on 10/19/2008 at 12:47:11 PM by Essential NetTools
Tracing route to webmail.verizon.net over a maximum of 25 hops:
#1 71.245.76.1 [L100.VFTTP-04.PRVDRI.verizon-gni.net]: TTL expired in transit, 4 ms
#2 130.81.54.20 [Unavailable]: TTL expired in transit, 3 ms
#3 130.81.28.130 [P15-3.LCR-01.DLLSTX.verizon-gni.net]: TTL expired in transit, 7 ms
#4 130.81.19.74 [Unavailable]: TTL expired in transit, 18 ms
#5 130.81.19.78 [Unavailable]: TTL expired in transit, 85 ms
#6 130.81.20.157 [so-1-0-0-0.CORE-RTR1.DFW03.verizon-gni.net]: TTL expired in transit, 57 ms
#7 206.46.225.85 [po1.ctn-border1.vzlink.com]: TTL expired in transit, 55 ms
#8 206.46.225.18 [po121.ctn-core1.vzlink.com]: TTL expired in transit, 55 ms
#9 206.46.228.34 [Unavailable]: TTL expired in transit, 55 ms
#10 206.46.232.14 [Unavailable]: Echo reply, 62 ms
Statistics: Out: 10; In: 10; Loss: 0%; Times(min/avg/max): 3/40/85
From here, webmail traffic stays on the verizon-controlled network. |
|
HerbW
join:2008-10-18
Herndon, VA | Here is the trace route to verizon:
C:\>tracert www.verizon.net
Tracing route to www.verizon.net [206.46.232.39] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 2 ms 1 ms 2 ms 96.231.199.1
3 3 ms 3 ms 3 ms G11-1-661.LCR-06.WASHDC.verizon-gni.net [130.81.104.180]
4 43 ms 43 ms 43 ms so-1-0-0-0.CORE-RTR1.DFW03.verizon-gni.net [130.81.20.157]
5 43 ms 43 ms 43 ms po1.ctn-border1.vzlink.com [206.46.225.85]
6 50 ms 50 ms 49 ms po121.ctn-core1.vzlink.com [206.46.225.18]
7 50 ms 49 ms 50 ms 206.46.229.17
8 * 43 ms 44 ms 206.46.232.39
Trace complete. |
|
| reply to birdfeedr
said by birdfeedr:said by heritageguy:There is a backbone router down in Vienna, VA. Run Internet Traffic Report (www.internettrafficreport.com/namerica.htm) to see its status. I'm curious, and asking because I don't know. How do you know it's a backbone router, and that that particular router outage is causing issues with traffic in the mid-Atlantic area? Read the introduction to Internet Traffic Reports.com Is that router outage causing the FiOS webmail problem, subject of the OP? And why don't they just fix it already? The router's URL points to 207.254.32.14 and whois says it belongs to Amerion. How are they connected to Verizon? Added: Amerion.com and bossig.com point to the same outfit. Amerion looks like they are a dial-up ISP. |
|
| Sorry, I'm new to this board and its mechanics.
First, before someone else jumps in. These are my assumptions and they fit with the problem that I am seeing. This slowdown SEEMS to correspond to the router outage. I am offering this as a possible explanation for this issue.
1a. Read the introduction to Internet Traffic Reports.com. It's a listing of backbone routers in the world(at least a sampling). If a router goes bad they have to get another one. Usually takes time if they don't have a spare on hand.
1b. Verizon's feed doesn't just run on Verizon's network. It uses the Internet backbone. If local service normally runs through that router, the local service gets redirected and takes longer.
2. If they have a backbone router, they have a backbone router. Doesn't matter what services they offer.
I talked to Verizon several times about this issue. They say that it's not on their network so there's nothing that they can do. If, indeed, this missing router is the problem then they are correct. The proof or disproof will be if normal service is retored when the router is replaced. |
|
birdfeedrPremium,MVM
join:2001-08-11
Warwick, RI
kudos:5 | I may be wrong and misunderstanding their premise, but Internet Traffic Watch implies they are monitoring backbone routers. I think most of them are more likely edge routers, not major backbone.
Above.net *is* represented.
Check out »/routerwatch for a similar display of possible router problems. These are tested as part of line quality performance tests. |
|
