Seeing all kinds of up and down from the Spectrum Cable side in NE Ohio
across dozens of client sites. Pings to 4.2.2.x and access to services
like Discord and Slack get interrupted while pings to 8.8.8.8 stay
working. I lose access to all my Newark Linodes whenever it happens.
On Tue, Sep 7,
Amazon goofed up their DNS for a bit, the A record for www.amazon.com
wasn't there and the raw amazon.com was redirecting to www.
Some discussion on HN: https://news.ycombinator.com/item?id=23341170
On Thu, May 28, 2020 at 3:49 PM Dan Walters via Outages
wrote:
> Simile.amazon.com and
I seem to have lost all my systems in Linode's Newark location. Can't ping
or connect to from anywhere, including other Linode-hosted systems in
Dallas and London. Linode's web console tool also can't connect.
___
Outages mailing list
I saw the issues from my own systems in New York and New Jersey, both of
which connect to the New York POP by default, and also from another
vendor's system in Philadelphia which I assume also uses New York. I was
seeing ~12% packet loss on every call routed through them.
It doesn't appear to be
Anyone else experiencing major quality issues on Bandwidth? I'm having
really bad connections both inbound and outbound from multiple locations in
different states.
___
Outages mailing list
Outages@outages.org
I was watching my Houston site MTR and just saw it start taking a different
route that avoids NTT/L3 and at that same time my pings cleared up all
around the country. I'm now going on three minutes clean.
On Mon, Nov 6, 2017 at 2:25 PM Boyd, Ian via Outages
wrote:
> I have
I was definitely seeing it this morning, had a few customers unable to
reach a certain vendor due to DNS not responding and my own Reddit browsing
was unreliable, but it cleared up and has been solid since a bit after 9:00
Eastern.
Dyn status page says they consider the problem resolved as of
Not that we likely need more confirmation at this point, but I'm seeing it
on Cleveland-area DIDs. Definitely some kind of SHTF situation at Level3.
On Tue, Oct 4, 2016 at 10:28 AM Kevin Miller via Outages <
outages@outages.org> wrote:
> All of our Level3 DIDs in PHL and JFK do not seem to
I'm seeing the same. It's not a local DNS error, it's a HTML error page
that contains the following text:
---
Service Unavailable - DNS failure
The server is temporarily unable to service your request. Please try again
later.
Reference #11.832d1bb8.1464798760.162f8dd4
---
If I'm not mistaken
I have a few dozen clients on VI and haven't heard any complaints yet. I
was just able to test call all of my normal test lines through my VI trunk
without any issues as well. Not to say that confirms or denies anything,
they do seem to have a habit of coming up with interesting ways to fail.
Same experience here, including the DR site not being of any use. It
responds with a "100 Trying" and then 20 seconds later a "504 Server
Timeout".
Between this and the issue I posted about the other day (which they
confirmed was a bug in their system that caused parts of it to think
certain
16 at 7:13 PM Sean Hayes via Outages <outages@outages.org>
wrote:
> Appears to be reachable to Miami, FL and the Florida Keys via VI.
>
> On May 4, 2016 6:58 PM, "Sean Harlow via Outages" <outages@outages.org>
> wrote:
>
> >
>
> > I'm seeing no
I'm seeing no SIP responses on most of my calls attempting to go out VoIP
Innovations and while I'm not 100% sure yet (discovered this while not in a
great place to test) it does not look like I'm getting incoming calls from
them either.
I'm being told that traceroutes to them are looping what
13 matches
Mail list logo