To answer your specific question - In the regions we use 3356 (NYC and SFO/Bay Area) 3356 have been solid. I’d even say they have less issues than the other usual tier 1 providers... for example 1299 had a hell of a week last week around SFO was 3356 was stable.
Can’t comment on what I’d say are small regions like Tampa though. On Sat, May 19, 2018 at 5:56 PM David Hubbard <dhubb...@dino.hostasaurus.com> wrote: > Yes, I do, as stated in my initial email. My inquiry is about whether > this level of downtime, and lack of redundancy for a given region, is > normal for 3356. There are some markets where diverse paths are not so > easy to acquire. > ________________________________ > From: Robert DeVita <radev...@mejeticks.com> > Sent: Saturday, May 19, 2018 5:36:23 PM > To: David Hubbard; nanog@nanog.org > Subject: Re: Curiosity about AS3356 L3/CenturyLink network resiliency (in > general) > > If this is a know issue and has happened before and point to point > circuits aren’t effected you always have the opportunity to diversify your > own network and get private lines back to Miami, Jax, Atlanta or Dallas to > create your own diversity don’t you? > > Robert DeVita > Managing Director > Mejeticks > c. 469-441-8864 > e. radev...@mejeticks.com > _____________________________ > From: David Hubbard <dhubb...@dino.hostasaurus.com> > Sent: Wednesday, May 16, 2018 12:03 PM > Subject: Curiosity about AS3356 L3/CenturyLink network resiliency (in > general) > To: <nanog@nanog.org> > > > I’m curious if anyone who’s used 3356 for transit has found shortcomings > in how their peering and redundancy is configured, or what a normal > expectation to have is. The Tampa Bay market has been completely down for > 3356 IP services twice so far this year, each for what I’d consider an > unacceptable period of time (many hours). I’m learning that the entire > market is served by just two fiber routes, through cities hundreds of miles > away in either direction. So, basically two fiber cuts, potentially 1000+ > miles apart, takes the entire region down. The most recent occurrence was a > week or so ago when a Miami-area cut and an Orange, Texas cut (1287 driving > miles apart) took IP services down for hours. It did not take point to > point circuits to out of market locations down, so that suggests they even > have the ability to be more redundant and simply choose not to. > > I feel like it’s not unreasonable to expect more redundancy, or a much > smaller attack surface given a disgruntled lineman who knows the routes > could take an entire region down with a planned cut four states apart. > Maybe other regions are better designed? Or are my expectations > unreasonable? I carry three peers in that market, so it hasn’t been > outage-causing, but I use 3356 in other markets too, and have plans for > more, but it makes me wonder if I just haven't had the pleasure of similar > outages elsewhere yet and I should factor that expectation into the design. > It creates a problem for me in one location where I can only get them and > Cogent, since Cogent can't be relied on for IPv6 service, which I need. > > Thanks > > > > >