How Verizon fixed a recent backbone provider issue

Re:How Verizon fixed a recent backbone provider issue by aroch on Friday February 06, 2015 @07:55AM (#9008744)

The cynic in me wonders if this is blog post was written solely to serve as positive PR for Verizon in the face of their horrible transit/peering infrastructure management (ie. letting links run hot so they can charge transit providers more money for each increase in commit or letting peering ports run very hot because they don't want to spend the few thousand to add another 10G because they'd rather be paid for transit) before the FCC vote.

Edgecast is owned by Verizon, so cynical-me is having a hard time believing this is not a plant.

[ Parent | on HN ]

Re:How Verizon fixed a recent backbone provider issue by shdon on Friday February 06, 2015 @08:02AM (#9008770)

No company is all bad. I'm sure there are plenty of techs at Verizon and its subsidiaries that are just trying to do the best job they possibly can and are excited and rightfully proud to diagnose and fix such a problem. Looks like they did some good detective work and deserve the bragging rights.

We see similar posts pop up once in a while with other such situations (CloudFlare springs to mind). It just happens to be Verizon in this case.

[ Parent | on HN ]

Re:How Verizon fixed a recent backbone provider issue by PhantomGremlin on Saturday February 07, 2015 @12:44AM (#9013213)

> No company is all bad.

I think there are a few that are. I see very little good in a company like Philip Morris. They manufacture a delivery system for an addictive drug that, as a side effect, results in countless cancer deaths.

I couldn't possibly see myself working for a company like that.

OTOH under the right circumstances I'd work for Verizon. Their evil is venial compared to merchants of death. But a man's gotta eat, and that's why we prostitute ourselves out to these evil behemoths. And why we rationalize that we're "just trying to do the best job we possibly can".

[ Parent | on HN ]

Re:How Verizon fixed a recent backbone provider issue by rayiner on Friday February 06, 2015 @09:34AM (#9009123)

If we injected politics into every tech article, there would be no tech articles here. Article on how Graph Search works under the hood? "But did you know Facebook makes their money peddling consumerism to kids?" Etc. At the end of the day, the technology involved in flinging all those terabits of Facebook/Twitter/Netflix content around the aether is legitimately interesting, whatever the FCC vote may be.

[ Parent | on HN ]

Re:How Verizon fixed a recent backbone provider issue by beachstartup on Friday February 06, 2015 @11:25AM (#9009711)

... dude, it's a company blog post. they're writing about what they do in their noc. it's basic SEO and marketing, not some telco conspiracy.

[ Parent | on HN ]

Re:How Verizon fixed a recent backbone provider issue by dredmorbius on Friday February 06, 2015 @03:23PM (#9011299)

Given the "being good stewards of the Internet" headline: yeah, total submarine.

http://www.paulgraham.com/submarine.html

[ Parent | on HN ]

Re:How Verizon fixed a recent backbone provider issue by PhantomGremlin on Saturday February 07, 2015 @12:32AM (#9013188)

You're not the only cynic on HN. When I read this I immediately thought of the somewhat different "infrastructure management" that occurred when Verizon extorted Netflix a while ago.

That blog post would have been written something like this:

Verizon: Those sure are nice packets you're asking us to deliver to our mutual customers. It'd be a shame if something happened to them at the interface between our networks.

Netflix: Ouch. Ouch. Ouch. Thank you for bending us over and screwing us. Here, take some of our money. Please make the pain stop.

[ Parent | on HN ]

Re:How Verizon fixed a recent backbone provider issue by jacquesm on Friday February 06, 2015 @08:49AM (#9008886)

They're quite up-front about edgecast being owned by verizon (see large logo at the top left of the page) and the lead sentence.

This is a pretty good write-up of what happens behind the scenes when debugging a network issue.

[ Parent | on HN ]