On 21 October 2016 at 09:12, Terry Hardie via Outages
wrote:
> Even though their page says the outage is resolved, I'm still getting
> DNS failures (return SERVFAIL, not no answer) to their anycast
> networks from California:
I can't reach github.com from Cox in Las Vegas but at work I can.
;;
On 20 May 2016 at 10:51, chris via Outages wrote:
> they were hard down for about 5-10 mins including their own phone numbers,
> website, SIP, everything
Confirming as well.
--
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
_
On 15 October 2015 at 13:54, Frank Bulk via Outages wrote:
> Confirmed on Twitter, too.
Please share link to twitter post.
--
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
Outages mailing list
Outages@out
On 15 October 2015 at 13:46, Pete E via Outages wrote:
> Anyone else seeing issues with UltraDNS? We don't use them but some of our
> providers do and it appears to be a problem resolving hosts.
>
Ah, this explains why I just got an alert that says 'The domain name
does not exist'
Thanks!
--
-
On 28 September 2015 at 14:34, Grant Ridder via Outages
wrote:
> I am seeing time outs to github.com (resolves to 192.30.252.128) from SF bay
> area.
no problems from las vegas, nevada with level3 connection either
loading the http site or git protocol.
github.com. 6 IN A 19
On 27 August 2015 at 12:54, Scott Weeks via Outages wrote:
>
> --- outages@outages.org wrote:
>
> Root Cause: An unknown issue in Chicago, IL was impacting IP services.
> Fix Action: Adjustments were made to resolve the issue and restore services.
>
> Summary:
> The IP NOC responded to an unknown
On 27 August 2015 at 12:48, Bobin Joseph via Outages
wrote:
> Anybody else having complete outage on Level3? We lost complete internet in
> DFW and SAN
>
We were not down but significant routing issues in Las Vegas.
> Thanks,
> Bobin
>
___
Outages mai
Hi Scott,
On 23 December 2014 at 07:20, Scott Lambert via Outages
wrote:
> 08:55:31 Tue Dec 23 $ telnet d61692a.ess.barracudanetworks.com 25
> Trying 64.235.150.197...
> telnet: connect to address 64.235.150.197: Connection refused
> Trying 64.235.154.66...
> telnet: connect to address 64.235.154.
Dear Dovid,
From: Dovid B via Outages
Sent: Wed, 24 Sep 2014 12:26:25 -0400
To: outages@outages.org
Subject: [outages] Issues to Digital Ocean?
>
> Is anyone else having a problem getting to Digital Ocean?
>
They're very active on twitter and their