We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly. Other sites are fine. We connect through Level3 and Bell Canada. --- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8 tel. 519-985-8410 fax. 519-985-8409
On Thu, 14 May 2009, Clayton Zekelman wrote:
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
Likewise. Which of course affects the whole flipping world since everyone uses google analytics and stuff. My path is also through level 3 - don't know if it's confined to them. Jason -- Jason Slagle - RHCE /"\ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . \ / ASCII Ribbon Campaign . X - NO HTML/RTF in e-mail . / \ - NO Word docs in e-mail .
Sounds like it is Level3 specific. At 12:04 PM 5/14/2009, Jason Slagle wrote:
On Thu, 14 May 2009, Clayton Zekelman wrote:
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
Likewise. Which of course affects the whole flipping world since everyone uses google analytics and stuff.
My path is also through level 3 - don't know if it's confined to them.
Jason
-- Jason Slagle - RHCE /"\ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . \ / ASCII Ribbon Campaign . X - NO HTML/RTF in e-mail . / \ - NO Word docs in e-mail .
No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.325 / Virus Database: 270.12.29/2114 - Release Date: 05/14/09 06:28:00
--- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8 tel. 519-985-8410 fax. 519-985-8409
I happened to have a traceroute to www.google.com at around 08:14 PDT. It seems like we started seeing trouble on the boundary of AT&T and Google. The traceroute originated from San Mateo, CA. ]$ traceroute -I www.google.com traceroute: Warning: www.google.com has multiple addresses; using 74.125.65.104 traceroute to www.l.google.com (74.125.65.104), 64 hops max, 60 byte packets 1 x.x.x.x 0.456 ms 0.482 ms 0.469 ms 2 x.x.x.x 1.819 ms 1.461 ms 1.314 ms 3 svl-core-02.inet.qwest.net (205.171.14.74) 1.308 ms 1.302 ms 1.844 ms 4 sjp-brdr-03.inet.qwest.net (67.14.34.6) 2.718 ms 1.698 ms 1.747 ms 5 192.205.36.1 (192.205.36.1) 3.862 ms 3.764 ms 4.529 ms 6 cr2.sffca.ip.att.net (12.123.15.162) 68.652 ms 64.727 ms 64.703 ms 7 cr2.la2ca.ip.att.net (12.122.31.133) 65.914 ms 65.231 ms 65.678 ms 8 cr2.dlstx.ip.att.net (12.122.28.177) 65.753 ms 65.369 ms 65.352 ms 9 cr1.attga.ip.att.net (12.122.28.173) 66.036 ms 65.543 ms 65.158 ms 10 12.123.22.5 (12.123.22.5) 64.126 ms 64.159 ms 64.212 ms 11 * * * 12 72.14.233.56 (72.14.233.56) 267.820 ms * * 13 * * 209.85.254.247 (209.85.254.247) 270.569 ms 14 209.85.253.209 (209.85.253.209) 287.797 ms * 276.602 ms 15 * gx-in-f104.google.com (74.125.65.104) 283.802 ms * $ $ whois 12.123.22.5 AT&T WorldNet Services ATT (NET-12-0-0-0-1) 12.0.0.0 - 12.255.255.255 AT&T Worldnet Services ATTSVI-12-122-0-0 (NET-12-122-0-0-1) 12.122.0.0 - 12.123.255.255 # ARIN WHOIS database, last updated 2009-05-13 19:10 # Enter ? for additional hints on searching ARIN's WHOIS database. $ $ whois 72.14.233.56 OrgName: Google Inc. OrgID: GOGL Address: 1600 Amphitheatre Parkway City: Mountain View StateProv: CA PostalCode: 94043 Country: US NetRange: 72.14.192.0 - 72.14.255.255 CIDR: 72.14.192.0/18 NetName: GOOGLE NetHandle: NET-72-14-192-0-1 Parent: NET-72-0-0-0-0 NetType: Direct Allocation NameServer: NS1.GOOGLE.COM NameServer: NS2.GOOGLE.COM NameServer: NS3.GOOGLE.COM NameServer: NS4.GOOGLE.COM Comment: RegDate: 2004-11-10 Updated: 2007-04-10 RTechHandle: ZG39-ARIN RTechName: Google Inc. RTechPhone: +1-650-318-0200 RTechEmail: arin-contact@google.com OrgTechHandle: ZG39-ARIN OrgTechName: Google Inc. OrgTechPhone: +1-650-318-0200 OrgTechEmail: arin-contact@google.com # ARIN WHOIS database, last updated 2009-05-13 19:10 # Enter ? for additional hints on searching ARIN's WHOIS database. $ -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Clayton Zekelman Sent: Thursday, May 14, 2009 09:20 To: Jason Slagle Cc: outages@outages.org Subject: Re: [outages] Google Issue Sounds like it is Level3 specific. At 12:04 PM 5/14/2009, Jason Slagle wrote:
On Thu, 14 May 2009, Clayton Zekelman wrote:
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
Likewise. Which of course affects the whole flipping world since everyone uses google analytics and stuff.
My path is also through level 3 - don't know if it's confined to them.
Jason
-- Jason Slagle - RHCE /"\ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . \ / ASCII Ribbon Campaign . X - NO HTML/RTF in e-mail . / \ - NO Word docs in e-mail .
No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.325 / Virus Database: 270.12.29/2114 - Release Date: 05/14/09 06:28:00
--- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8 tel. 519-985-8410 fax. 519-985-8409 _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On Thu, 14 May 2009, Clayton Zekelman wrote:
My path is also through level 3 - don't know if it's confined to them.
Non - L3 paths show no issues (well, at least a few of my non-L3 google paths show no issues.) -- W. Kevin Hunt CCIE #11841 Linux+ SME
-----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of W. Kevin Hunt Sent: Thursday, May 14, 2009 11:28 AM To: Jason Slagle; outages@outages.org Subject: Re: [outages] Google Issue
On Thu, 14 May 2009, Clayton Zekelman wrote:
My path is also through level 3 - don't know if it's confined to them.
Non - L3 paths show no issues (well, at least a few of my non-L3 google paths show no issues.) -- W. Kevin Hunt CCIE #11841 Linux+ SME
I have not seen any reports of issues all day with peering to google in Dallas, Seattle or Virginia. The contents of this email message and any attachments are confidential and are intended solely for the addressee. The information may also be legally privileged. This transmission is sent in trust for the sole purpose of delivery to the intended recipient. If you have received this transmission in error; any use, reproduction or dissemination of this transmission is strictly prohibited. If you are not the intended recipient, please immediately notify the sender by reply email and delete this message and all associated attachments.
We are having the same issue in Louisiana via AT&T. Sent from my iPhone On May 14, 2009, at 11:03 AM, "Clayton Zekelman" <clayton@mnsi.net> wrote:
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
--- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8
tel. 519-985-8410 fax. 519-985-8409
_______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
I called Level 3 and they wouldn't provide or did not have a master ticket on it but they did confirm there was a 'major' outage but nothing more unfortunately. That's what I know. Seems fine from other carriers -> google. Clayton Zekelman wroteth on 5/14/2009 8:56 AM:
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
--- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8
tel. 519-985-8410 fax. 519-985-8409 _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
We can't reach Google services from our level3 connection (T3) or our Verizon Connection (50 Mbits) Works fine from our Comcast Fiber and from my home Comcast Cable modem even though it routes through Level 3. Bob Roswell System Source broswell@syssrc.com (410) 771-5544 ext 4336 -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Clayton Zekelman Sent: Thursday, May 14, 2009 11:56 AM To: outages@outages.org Subject: [outages] Google Issue We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly. Other sites are fine. We connect through Level3 and Bell Canada. --- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8 tel. 519-985-8410 fax. 519-985-8409 _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Same here. We tested through Level3 and through TransitRail. I called the Google NOC and they told me they were having a problem, but they didn't elaborate. On Thu, May 14, 2009 at 10:56 AM, Clayton Zekelman <clayton@mnsi.net> wrote:
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
--- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8
tel. 519-985-8410 fax. 519-985-8409 _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Byron L. Hicks University of Texas System 512-377-9857 AIM: byronhicks
Google confirms the outage: http://www.google.com/appsstatus# We're aware of a problem with Google Mail affecting a small subset of users. The affected users are unable to access Google Mail. We will provide an update by May 14, 2009 1:00:00 PM UTC-4 detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change. *This may also be affecting other services -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Clayton Zekelman Sent: Thursday, May 14, 2009 11:56 AM To: outages@outages.org Subject: [outages] Google Issue We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly. Other sites are fine. We connect through Level3 and Bell Canada. --- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8 tel. 519-985-8410 fax. 519-985-8409 _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Clayton Zekelman Sent: Thursday, May 14, 2009 11:56 AM To: outages@outages.org Subject: [outages] Google Issue
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
No complaints here. GMail, Google search, Maps, etc are all very snappy. Accessing via Level3: Tracing the route to google.ca (64.233.161.104) 1 ge-6-11-117.car1.Toronto2.Level3.net (4.59.180.17) [AS 3356] 152 msec 204 msec 8 msec 2 ae-11-11.car2.Toronto2.Level3.net (4.69.140.250) [AS 3356] 4 msec 8 msec 4 msec 3 ae-2-2.car2.Montreal2.Level3.net (4.69.140.254) [AS 3356] 12 msec 12 msec 12 msec 4 ae-11-11.car1.Montreal2.Level3.net (4.69.141.2) [AS 3356] 12 msec 12 msec 12 msec 5 ae-5-5.ebr4.NewYork1.Level3.net (4.69.141.6) [AS 3356] 20 msec 20 msec 20 msec 6 ae-84-84.csw3.NewYork1.Level3.net (4.69.134.122) [AS 3356] 20 msec ae-94-94.csw4.NewYork1.Level3.net (4.69.134.126) [AS 3356] 28 msec ae-74-74.csw2.NewYork1.Level3.net (4.69.134.118) [AS 3356] 32 msec 7 ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73) [AS 3356] 20 msec ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77) [AS 3356] 20 msec ae-61-61.ebr1.NewYork1.Level3.net (4.69.134.65) [AS 3356] 20 msec 8 ae-3-3.ebr4.Washington1.Level3.net (4.69.132.93) [AS 3356] 36 msec 24 msec 32 msec 9 ae-94-94.csw4.Washington1.Level3.net (4.69.134.190) [AS 3356] 28 msec ae-64-64.csw1.Washington1.Level3.net (4.69.134.178) [AS 3356] 28 msec ae-74-74.csw2.Washington1.Level3.net (4.69.134.182) [AS 3356] 28 msec 10 ae-3-89.edge1.Washington1.Level3.net (4.68.17.144) [AS 3356] 24 msec ae-4-99.edge1.Washington1.Level3.net (4.68.17.208) [AS 3356] 24 msec ae-1-69.edge1.Washington1.Level3.net (4.68.17.16) [AS 3356] 88 msec 11 GOOGLE-INC.edge1.Washington1.Level3.net (4.79.22.38) [AS 3356] 24 msec GOOGLE-INC.edge1.Washington1.Level3.net (4.79.228.38) [AS 3356] 28 msec 28 msec 12 209.85.240.136 [AS 15169] 24 msec 209.85.241.50 [AS 15169] 28 msec 209.85.240.136 [AS 15169] 24 msec 13 72.14.236.200 [AS 15169] 24 msec 64.233.175.219 [AS 15169] 24 msec 64.233.175.111 [AS 15169] 24 msec 14 216.239.49.214 [AS 15169] 48 msec 216.239.48.190 [AS 15169] 28 msec 28 msec 15 google.ca (64.233.161.104) [AS 15169] 28 msec 28 msec 24 msec --- Ross Halliday Network Operations WTC Communications Office: 613-547-6939 x203 Helpdesk: 866-547-6939 option 2 http://www.wtccommunications.ca
No issues have been reported here (Philadelphia). L3 transit as well. - Chris
Hi,
No issues have been reported here (Philadelphia). L3 transit as well.
Same for Level 3 Minneapolis: traceroute to www.l.google.com (72.14.205.103), 64 hops max, 44 byte packets ... 4 ae-11-11.car1.Minneapolis1.Level3.net (4.69.136.101) 0.411 ms 0.383 ms 0.492 ms 5 ae-4-4.ebr1.Chicago1.Level3.net (4.69.136.106) 8.993 ms 16.052 ms 17.954 ms 6 ae-2-2.ebr2.NewYork2.Level3.net (4.69.132.66) 29.721 ms 29.572 ms 29.770 ms 7 ae-6-6.ebr4.NewYork1.Level3.net (4.69.141.21) 30.120 ms 34.887 ms 36.207 ms 8 ae-94-94.csw4.NewYork1.Level3.net (4.69.134.126) 40.179 ms 34.878 ms 35.866 ms 9 ae-1-69.edge1.NewYork1.Level3.net (4.68.16.14) 30.148 ms 30.198 ms 30.038 ms 10 GOOGLE-INC.edge1.NewYork1.Level3.net (4.71.172.86) 30.600 ms GOOGLE-INC.edge1.NewYork1.Level3.net (4.71.172.82) 29.240 ms 29.159 ms 11 209.85.255.68 (209.85.255.68) 29.509 ms 29.973 ms 29.795 ms 12 216.239.43.146 (216.239.43.146) 49.621 ms 49.817 ms 49.480 ms 13 66.249.94.90 (66.249.94.90) 45.374 ms 66.249.94.92 (66.249.94.92) 50.097 ms 49.688 ms 14 72.14.232.66 (72.14.232.66) 49.797 ms 48.529 ms 54.174 ms 15 qb-in-f103.google.com (72.14.205.103) 50.752 ms 50.131 ms 48.525 ms Cheers, Robert
Robert, I live in Delaware, and I was out of service. I don't think this was a network issue, (I have unconfirmed reports that say it wasn't), and was on Google's infrastructure. I think if you were affected, it depended on what Google data center you were connected to. J On Thu, May 14, 2009 at 1:53 PM, Robert Joosten <robert@ml.erje.net> wrote:
Hi,
No issues have been reported here (Philadelphia). L3 transit as well.
Same for Level 3 Minneapolis:
traceroute to www.l.google.com (72.14.205.103), 64 hops max, 44 byte packets ... 4 ae-11-11.car1.Minneapolis1.Level3.net (4.69.136.101) 0.411 ms 0.383 ms 0.492 ms 5 ae-4-4.ebr1.Chicago1.Level3.net (4.69.136.106) 8.993 ms 16.052 ms 17.954 ms 6 ae-2-2.ebr2.NewYork2.Level3.net (4.69.132.66) 29.721 ms 29.572 ms 29.770 ms 7 ae-6-6.ebr4.NewYork1.Level3.net (4.69.141.21) 30.120 ms 34.887 ms 36.207 ms 8 ae-94-94.csw4.NewYork1.Level3.net (4.69.134.126) 40.179 ms 34.878 ms 35.866 ms 9 ae-1-69.edge1.NewYork1.Level3.net (4.68.16.14) 30.148 ms 30.198 ms 30.038 ms 10 GOOGLE-INC.edge1.NewYork1.Level3.net (4.71.172.86) 30.600 ms GOOGLE-INC.edge1.NewYork1.Level3.net (4.71.172.82) 29.240 ms 29.159 ms 11 209.85.255.68 (209.85.255.68) 29.509 ms 29.973 ms 29.795 ms 12 216.239.43.146 (216.239.43.146) 49.621 ms 49.817 ms 49.480 ms 13 66.249.94.90 (66.249.94.90) 45.374 ms 66.249.94.92 (66.249.94.92) 50.097 ms 49.688 ms 14 72.14.232.66 (72.14.232.66) 49.797 ms 48.529 ms 54.174 ms 15 qb-in-f103.google.com (72.14.205.103) 50.752 ms 50.131 ms 48.525 ms
Cheers, Robert _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- joel esler | Sourcefire | gtalk: jesler@sourcefire.com | 302-223-5974 | http://twitter.com/joelesler
There are some reports that it may actually be at AT&T outage. The other possibility is that it hit only some Google data centers. I never saw a problem here in Maryland. See http://isc.sans.org/diary.html?storyid=6388. -- Jim Goltz <jgoltz@mail.nih.gov> CIT/DCSS/HSB/ASIG 12/2216
-----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Clayton Zekelman Sent: Thursday, May 14, 2009 11:56 To: outages@outages.org Subject: [outages] Google Issue
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
--- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8
tel. 519-985-8410 fax. 519-985-8409
_______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
FWIW, just had someone report they are unable to send E-Mail using Gmail w/Thunderbird. I investigated, discovered they cannot connect to smtp.gmail.com (on either port 465 or 587). This was using an AT&T DSL connection near Atlanta, GA. I am able to hit smtp.gmail.com from other places just fine, though. Possibly related? On Thu, May 14, 2009 at 11:56 AM, Clayton Zekelman <clayton@mnsi.net> wrote:
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
--- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8
tel. 519-985-8410 fax. 519-985-8409 _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Jeremy G. Gault, KD4NED Network Administrator WinWorld Corporation (423) 473-8084 (voice) (423) 790-0603 (fax)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 pop.gmail.com wasn't responding 20 minutes back from LA region, I thought it was our filters. Its up / running now. Looking forward to the incident report from google. regards, /virendra Jeremy G. Gault wrote:
FWIW, just had someone report they are unable to send E-Mail using Gmail w/Thunderbird. I investigated, discovered they cannot connect to smtp.gmail.com (on either port 465 or 587). This was using an AT&T DSL connection near Atlanta, GA. I am able to hit smtp.gmail.com from other places just fine, though.
Possibly related?
On Thu, May 14, 2009 at 11:56 AM, Clayton Zekelman <clayton@mnsi.net> wrote:
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
--- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8
tel. 519-985-8410 fax. 519-985-8409 _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
------------------------------------------------------------------------
_______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFKDEuUpbZvCIJx1bcRAof8AKCbPiu0TnIb0blJwwC3QlX6Oe7npACfcj16 EY2wsZxmKejYnbbtRS7qNJk= =W4m6 -----END PGP SIGNATURE-----
Noticing issues in Phoenix. We're on Cogent and Carpathia. On Thu, 2009-05-14 at 11:56 -0400, Clayton Zekelman wrote:
We've been noticing issues for the past hour accessing Google's sites. Sluggish responses mostly.
Other sites are fine. We connect through Level3 and Bell Canada.
--- Clayton Zekelman Managed Network Systems Inc. (MNSi) 344-300 Tecumseh Rd. E. Windsor, Ontario N8X 5E8
tel. 519-985-8410 fax. 519-985-8409
_______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages -- "Prediction is very difficult, especially about the future." Niels Bohr -- Ray Sanders Linux Administrator Village Voice Media Office: 602-744-6547 Cell: 602-300-4344
participants (19)
-
Ambrose Curtis -
Andrew Wu -
Anthony Ledesma -
Bob Roswell -
Bret Esquivel -
Byron Hicks -
Chris Burwell -
Clayton Zekelman -
Goltz, Jim (NIH/CIT) [E] -
Jason Slagle -
Jeremy G. Gault -
Joel Esler -
Ray Sanders -
Robert Joosten -
Ross Halliday -
Steve Ryan -
Todd Snyder -
virendra rode -
W. Kevin Hunt