Re: Network Diagnostic Tool

2016-11-17 Thread Angel Lopez
Hi Mehrdad Arshad Rad, Thanks for this awesome! tool congrats On Wed, Nov 16, 2016 at 9:31 PM, Jason Hellenthal wrote: > https://twitter.com/jhackenthal/status/799091998594650112 > > > On Nov 12, 2016, at 22:05, J. Hellenthal wrote: > > > > That

Re: pay.gov and IPv6

2016-11-17 Thread Carl Byington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 2016-11-17 at 15:32 -0500, Lee wrote: > That's fine, but until someone is willing to work with them don't > expect it to get fixed. I am working with pay.gov.c...@clev.frb.org, trying to explain the problem. They seem to think I should

Re: Facebook Geo Routing Issues

2016-11-17 Thread Josh Reynolds
Or due to capacity issues. On Nov 16, 2016 7:53 PM, "Mike Hammett" wrote: > I'm in Chicago and I saw mine going to Miami as well (per rDNS). Haven't > looked into it at all. > > I did see a video where they said they occasionally purposely give people > less than ideal

Paging Olav van Doorn, Jan Willem Meijer, and Rutger Bevaart

2016-11-17 Thread Ronald F. Guilmette
If anybody can give me an email for any of these principals of Xconnect42, Inc. (Neatherlands) aka AS260, I'd appreciate it. I tried to reach somebody (anybody) at their company via the address I found online for the company but never got any response. That was a week

Re: pay.gov and IPv6

2016-11-17 Thread Lee
On 11/17/16, Matthew Kaufman wrote: > I sent email there and to another contact I had at the time. and the response was? > And I'm not going to break my users by turning IPv6 back on, so someone > else will need to work with them. That's fine, but until someone is willing

Re: pay.gov and IPv6

2016-11-17 Thread Matthew Kaufman
I sent email there and to another contact I had at the time. And I'm not going to break my users by turning IPv6 back on, so someone else will need to work with them. Matthew Kaufman On Thu, Nov 17, 2016 at 9:48 AM Lee wrote: > On 11/16/16, Matthew Kaufman

Re: pay.gov and IPv6

2016-11-17 Thread Lee
On 11/16/16, Matthew Kaufman wrote: > The good news is that I reported this particular site as a problem two and > three years ago, both, and it isn't any worse. did you contact Pay.gov Customer Service at: 800-624-1373 (Toll free, Option #2) or send an email to