Hi Chris,
HTTP does not allow a response code of 0. I have seen the many
times with PHP/cURL, as it uses HTTP 0 to indicate a timeout. Can you
attempt posting a failing status via curl on the command line and see
if that works? That should at least rule out any network issues.
Thanks
Steve's comment that he's seen this over the past few days over set
timespans - in our case, the problems are most prevalent between noon
and 6PM, eastern.
Also, here's my full traceroute:
Packets
Pings
Host
FYI - I have not seen this issue at so far today.. but will keep an
eye out.
On Feb 20, 8:27 am, Matt Sanford wrote:
> The times may help me do some network troubleshooting, what timezone
> is that?
>
> On Feb 20, 2009, at 08:13 AM, swggy wrote:
>
>
>
> > I've been seeing the same thing - it s
