Verizon Claims First to 100 Gigabit Deploys Ciena Technology Within Long Haul Network Verizon has been conducting 100 Gigabit core network trials with Siemens, Alcatel-Lucent and Nortel for some time, and back in April issued a statement promising that "selected segments" of its U.S. backbone network would be 100 Gigabit by the end of the second quarter of this year. While a little late, Verizon this week announced that they've taken 100 Gigabit links live on "a portion" of their national network, with plans to deploy this next-generation technology on more than 10 routes in 2011. Verizon had already deployed a 555-mile stretch of 100 Gigabit capability running from Paris to Frankfurt, and their 100G upgrade here in the States will occur in three segments: Chicago to New York, Sacramento to Los Angeles, and Minneapolis to Kansas City. The deployment here in the States will use Juniper Networks routers and Ciena's 100G coherent optical transport solution.
|
 | | When will they do XGPON for faster speeds? My 150/75 connection from FIOS isn't enough. If they upgrade their backbones to 100g links they can handle giving me some more speed right? =P -- 150/75 mbit Verizon FiOS connection FTW! | |
|  |  openbox9 join:2004-01-26 Alexandria, VA kudos:2 | Re: When will they do XGPON for faster speeds? At least you added an emoticon else people might take you serious  | |
|  |  |  |
 Reviews:
·Optimum Online
·Verizon FiOS
| cheaper switches the hand-me-downs will go to secondary markets outside the northeast and be considered an UPGRADE. nevertheless, there needs to be certain upgrades in the illinois, to nevada and points west links. my guess is it's still cheaper for verizon to contract 3rd party tier-1 providers rather than deploy well outside their footprint (part of the reason for distance throttling within the USA).
also, a free bump in speed tiers would be nice to offer within the next 6 months for customer retention.
 | |
|  |  NormanSPremium,MVM join:2001-02-14 San Jose, CA kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| Re: cheaper switches said by tmc8080:my guess is it's still cheaper for verizon to contract 3rd party tier-1 providers rather than deploy well outside their footprint (part of the reason for distance throttling within the USA). Doesn't Verizon own the old MCI/UUnet Tier 1 backbone now? -- Norman ~Oh Lord, why have you come ~To Konnyu, with the Lion and the Drum | |
|  |  |  Reviews:
·Optimum Online
·Verizon FiOS
| Re: cheaper switches said by NormanS:said by tmc8080:my guess is it's still cheaper for verizon to contract 3rd party tier-1 providers rather than deploy well outside their footprint (part of the reason for distance throttling within the USA). Doesn't Verizon own the old MCI/UUnet Tier 1 backbone now? yeah, but many of these routes are not contiguous (ny-cali) (florida to arizona) or upgraded since verizon bought MCI/worldcom for 5/100ths it's true cost. it's not surprising that data routes through multiple tier-1 companies in midwestern states. just do some traceroutes & see..
you'll end-up popping onto a cogego or at&t, comcast tier-1 provider sooner or later. not even google handles 100% of end-to-end traffic. | |
|  |  |  |  NormanSPremium,MVM join:2001-02-14 San Jose, CA kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| Re: cheaper switches said by tmc8080:not even google handles 100% of end-to-end traffic. Who does?
FWIW, when I was using 'at&t Yahoo! HSI' for Internet, I rode ATTIS transit to their exit to other peers. Formerly SBCIC, they used to peer heavily with Level 3. Not so much after SBC bought AT&T and rebranded. But ATTIS transit connected directly to Google, MSN, and Yahoo! transit. No Tier 1 providers.
My new ISP, Sonic.net, LLC, appears to be similar, in that they connect direct to Google, MSN, and Yahoo!.
Trace route to Google: [code] 09/13/11 16:47:57 Slow traceroute www.google.com Trace www.google.com (74.125.224.146) ... 173.228.18.1 RTT: 26ms TTL:255 (173-228-18-1.dsl.dynamic.sonic.net ok) 70.36.243.21 RTT: 26ms TTL:254 (gig1-6.cr1.lsatca11.sonic.net bogus rDNS: host not found [authoritative]) 69.12.211.5 RTT: 26ms TTL:252 (0.xe-7-1-0.gw.pao1.sonic.net bogus rDNS: host not found [authoritative]) 64.142.0.185 RTT: 27ms TTL:251 (0.xe-6-0-0.gw3.equinix-sj.sonic.net bogus rDNS: host not found [authoritative]) 206.223.116.21 RTT: 27ms TTL:251 (eqixsj-google-gige.google.com bogus rDNS: host not found [authoritative]) 216.239.49.168 RTT: 28ms TTL:249 (No rDNS) 64.233.174.119 RTT: 28ms TTL:249 (No rDNS) 74.125.224.146 RTT: 27ms TTL: 57 (No rDNS) [/code]
Trace route to MSN: [code] 09/13/11 16:50:47 Slow traceroute www.msn.com Trace www.msn.com (65.55.17.25) ... 173.228.18.1 RTT: 25ms TTL:255 (173-228-18-1.dsl.dynamic.sonic.net ok) 70.36.243.21 RTT: 26ms TTL:254 (gig1-6.cr1.lsatca11.sonic.net bogus rDNS: host not found [authoritative]) 69.12.211.5 RTT: 27ms TTL:252 (0.xe-7-1-0.gw.pao1.sonic.net bogus rDNS: host not found [authoritative]) 64.142.0.185 RTT: 26ms TTL:251 (0.xe-6-0-0.gw3.equinix-sj.sonic.net bogus rDNS: host not found [authoritative]) 206.223.116.17 RTT: 34ms TTL:251 (8075.microsoft.com bogus rDNS: host not found [authoritative]) 207.46.47.253 RTT: 27ms TTL:249 (ge-0-3-0-59.sjc-64cb-1b.ntwk.msn.net probable bogus rDNS: host not found [non-authoritative]) 207.46.46.51 RTT: 29ms TTL:249 (xe-7-0-2-0.bay-16c-1b.ntwk.msn.net probable bogus rDNS: host not found [non-authoritative]) 207.46.43.50 RTT: 28ms TTL:249 (xe-1-0-2-0.bay-16c-1a.ntwk.msn.net probable bogus rDNS: host not found [non-authoritative]) 207.46.40.48 RTT: 51ms TTL:249 (ge-0-3-0-0.co1-64c-1a.ntwk.msn.net probable bogus rDNS: host not found [non-authoritative]) 207.46.40.165 RTT: 51ms TTL:248 (xe-5-2-0-0.co1-96c-1b.ntwk.msn.net probable bogus rDNS: host not found [non-authoritative]) * * * failed * * * failed [/code]
Trace route to Yahoo!: [code] 09/13/11 16:52:04 Slow traceroute www.yahoo.com Trace www.yahoo.com (98.137.149.56) ... 173.228.18.1 RTT: 32ms TTL:255 (173-228-18-1.dsl.dynamic.sonic.net ok) 70.36.243.21 RTT: 26ms TTL:254 (gig1-6.cr1.lsatca11.sonic.net bogus rDNS: host not found [authoritative]) 69.12.211.5 RTT: 31ms TTL:252 (0.xe-7-1-0.gw.pao1.sonic.net bogus rDNS: host not found [authoritative]) 64.142.0.185 RTT: 27ms TTL:251 (0.xe-6-0-0.gw3.equinix-sj.sonic.net bogus rDNS: host not found [authoritative]) 206.223.116.16 RTT: 27ms TTL:250 (PAT2.SJC.yahoo.com fraudulent rDNS) 216.115.107.59 RTT: 28ms TTL:249 (ae-0-d161.msr1.sp1.yahoo.com ok) 67.195.128.79 RTT: 28ms TTL:249 (et-18-25.fab4-1-gdc.sp2.yahoo.com ok) 67.195.130.102 RTT: 27ms TTL:248 (te-9-3.bas1-1-prd.sp2.yahoo.com ok) 98.137.149.56 RTT: 28ms TTL: 56 (ir1.fp.vip.sp2.yahoo.com ok) [/code]
I don't think those three need to provide transcontinental transit. They seem to have server farms near the major transit hubs in the U.S., and only need to route locally from nearby users to their data centers.
OTOH, where I saw a lot of Level 3 transit with ATTIS, I see a lot of nLayer Communications transit with Sonic.net.
Trace route to Excite: [code] 09/13/11 16:41:05 Slow traceroute www.excite.com Trace www.excite.com (74.113.233.95) ... 173.228.18.1 RTT: 25ms TTL:255 (173-228-18-1.dsl.dynamic.sonic.net ok) 70.36.243.21 RTT: 25ms TTL:254 (gig1-6.cr1.lsatca11.sonic.net bogus rDNS: host not found [authoritative]) 69.12.211.5 RTT: 25ms TTL:252 (0.xe-7-1-0.gw.pao1.sonic.net bogus rDNS: host not found [authoritative]) 69.22.130.85 RTT: 29ms TTL:252 (xe-1-0-6.ar1.pao1.us.nlayer.net bogus rDNS: host not found [authoritative]) 69.22.153.18 RTT: 26ms TTL:251 (ae0-70g.cr1.pao1.us.nlayer.net bogus rDNS: host not found [authoritative]) 69.22.143.165 RTT: 26ms TTL:250 (ae1-50g.cr1.sjc1.us.nlayer.net bogus rDNS: host not found [authoritative]) 206.223.116.86 RTT: 27ms TTL:248 (mpr1.sjc7.us bogus rDNS: host not found [authoritative]) 64.125.27.90 RTT: 28ms TTL:248 (xe-4-1-0.er1.sjc2.us.above.net bogus rDNS: host not found [authoritative]) 64.125.28.18 RTT: 27ms TTL:247 (64.125.28.18.available.above.net bogus rDNS: host not found [authoritative]) 64.125.24.17 RTT: 36ms TTL:247 (xe-2-1-0.cr1.lax112.us.above.net bogus rDNS: host not found [authoritative]) 64.125.26.121 RTT: 71ms TTL:243 (xe-3-2-0.cr1.iah1.us.above.net bogus rDNS: host not found [authoritative]) 64.125.30.70 RTT: 71ms TTL:244 (xe-1-0-0.cr2.iah1.us.above.net bogus rDNS: host not found [authoritative]) 64.125.28.49 RTT: 97ms TTL:242 (xe-2-1-0.cr2.dca2.us.above.net bogus rDNS: host not found [authoritative]) 64.125.26.242 RTT: 96ms TTL:244 (xe-1-0-1.er2.iad10.us.above.net bogus rDNS: host not found [authoritative]) 64.124.202.18 RTT: 96ms TTL:243 (64.124.202.18.t00569-01.above.net bogus rDNS: host not found [authoritative]) * * * failed * * * failed [/code
Trace route to DSLR: [code] 09/13/11 16:40:35 Slow traceroute www.dslreports.com Trace www.dslreports.com (209.123.109.175) ... 173.228.18.1 RTT: 25ms TTL:255 (173-228-18-1.dsl.dynamic.sonic.net ok) 70.36.243.21 RTT: 26ms TTL:254 (gig1-6.cr1.lsatca11.sonic.net bogus rDNS: host not found [authoritative]) 69.12.211.5 RTT: 25ms TTL:252 (0.xe-7-1-0.gw.pao1.sonic.net bogus rDNS: host not found [authoritative]) 69.22.130.85 RTT: 29ms TTL:252 (xe-1-0-6.ar1.pao1.us.nlayer.net bogus rDNS: host not found [authoritative]) 69.22.153.18 RTT: 28ms TTL:251 (ae0-70g.cr1.pao1.us.nlayer.net bogus rDNS: host not found [authoritative]) 69.22.143.169 RTT: 27ms TTL:250 (ae1-60g.cr1.sfo1.us.nlayer.net bogus rDNS: host not found [authoritative]) 69.22.142.96 RTT: 42ms TTL:249 (xe-0-0-3.cr1.slc1.us.nlayer.net bogus rDNS: host not found [authoritative]) 69.22.142.101 RTT: 77ms TTL:248 (xe-5-2-0.cr1.ord1.us.nlayer.net bogus rDNS: host not found [authoritative]) 69.22.142.75 RTT: 93ms TTL:246 (xe-9-2-0.cr1.ewr1.us.nlayer.net bogus rDNS: host not found [authoritative]) 69.31.94.118 RTT: 95ms TTL:246 (ae1-70g.ar2.ewr1.us.nlayer.net bogus rDNS: host not found [authoritative]) 69.31.95.130 RTT: 93ms TTL: 53 (as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net bogus rDNS: host not found [authoritative]) 209.123.10.122 RTT: 95ms TTL: 52 (0.e1-4.tbr1.oct.nac.net bogus rDNS: host not found [authoritative]) 209.123.10.2 RTT: 94ms TTL:243 (vlan804.esd1.oct.nac.net bogus rDNS: host not found [authoritative]) 209.123.109.175 RTT: 95ms TTL: 50 (www.dslreports.com ok) [/code]
I am not sure I can find an East Coast destination with the same transit network from the S.F. Bay Area to the end.
FWIW, SBC was never a Tier 1 network operator until they bought AT&T. -- Norman ~Oh Lord, why have you come ~To Konnyu, with the Lion and the Drum | |
|  |  |  |  iansltx join:2007-02-19 Golden, CO kudos:2 | Show me a traceroute that "bounces" from VZ to someone else and back. | |
|
 | | The last mile still sucks in many locations BFD. Meanwhile Verizon can't deliver more than 3Mbps here in CenTex.  | |
|  |  bidger join:2009-12-23 Elmira, NY | Re: The last mile still sucks in many locations 1.5Mbps down here. I might have stayed @ 3. | |
|
 | |
|
|