Anyone seeing issues with Level 3 between anywhere
and Tampa, particularly Atlanta and Dallas? We've
seen lots of outbound issues and customers calling
about their sites being down or slow. Ultimately
turned our two links to them off and then everyone
says looks better. I opened a ticket with them and
of course they say no one has reported any issues
whatsoever. I sent them a bunch of traces and will
try turning them back on later tonight since these
non-issues tend to resolve themselves if I wait for
a single homed customer to yell loud enough for them
to fix it.
I'm seeing the same thing in the Atlanta market. I can trace to 1 IP in a
prefix but not another. Almost like maybe there's some FIB horkage across a
multi-path link or something. Fired off an e-mail, awaiting status for
now.
Anyone seeing issues with Level 3 between anywhere
and Tampa, particularly Atlanta and Dallas?
We just have co-lo in Tampa, but our upstream's connectivity is through
Level3 and we've been seeing intermittent packet loss up there all day. We
alerted our upstream but no updates so far. It hasn't been bad enough for
our customers to call and complain though.
Internap just reported problems with L3 out of Miami:
"we are seeing latency, minor packet loss and path problems to a
number of destinations and other PNAPs via our Level3 (AS3356) upstream
connection in the MIA003 PNAP. "
We've also been seeing some "weird" (hard to track down) issues all day
with Level 3 in both Tampa and Atlanta, especially from our NMS systems
monitoring systems all over the place.
My contact at Level 3 didn't know of anything going on and couldn't really
find anything. Anyone else have a Level 3 response?
I too have a cage at Hampton Oaks, 10M up and 10M tail to me over OC-12,
and I had problems 15-1630ish to wired.com and zimbra.com, among other
sites; mtr had no appreciable loss tracing, but upper layer protocols
were hincky. It was clear by the next morning...
We have gigE to Level3 in Orlando, and saw something happen around 1pm today. Customers were complaining of latency and packet loss, and our traffic to/from L3 dropped noticably if only for a few minutes.