On Dec 2, 2014, at 1:43 PM, Tim Warnock
Public shaming rarely works in one’s favor. :)
We’re committed to exposing aggregate graphs on the IX portion of the platform in the near future. The numbers aren’t going to make anyone swoon, but transparency is the key, not volume.
Denver Maddux CEO Megaport
Hi Denver,
It was never about public shaming, but at least the other participants of the exchange would be able to see what's going on.
I'm not an advocate of having graphs truly publically accessible, but behind a portal you should be able to see the other participants port usage. Its immensely valuable for troubleshooting.
Also - some IXs have a policy that if you run your port hot and refuse to upgrade they can terminate your service. I've not seen it done in practice however (after all - who would want to turn off a paying customer.)
Tim
Hey Tim, I was being light-hearted about public shaming. At earlier points of my career I was a big fan of the full disclosure of all ports from exchanges, but most of us understand the varying business sensitivities each of us have to honor wherever we work these days. Perception of implied performance due to visibility of port status across a fabric will always be an area for debate. There are certainly ways to alleviate some of the concerns by providing fabric level and metro area link status thereby eliminating some areas of concern and helping to faster pinpoint performance issues. I’m happy to keep opening the data for Megaport publicly, and as our membership grows, where most useful and keeping privacy concerns in mind. Cameron suggested a great option of opting in or out of showing volunteered data behind the portal login, which we’ll just get done. Denver