Glenn Dekheyser

Dug into it a bit and really went all out and said, please hire me.

It got fixed after I left, but they essentially came to Equinix, honestly.

They did eventually come to Equinix.

I didn't have anything to do with that project, but I did see it.

They ended up rationalizing their network and getting low latent, and it ended up getting architected the right way underneath the stuff that we had originally put in.

So the stuff we sold didn't change.

It was just the Direct Connect configuration going out of the right region.

making sure that the last mile stuff was set up correctly, their internal routing was set correctly.

Stuff that we say, it's the network guy.

Well, that network guy's gotten a lot more important to us than they ever used to be.

So better make friends with them.

Stop blaming them for stuff.

I wish there was a universal answer for that.

What we do at Equinix, when we have a customer that wants to optimize that outcome, we do a workshop with them.

It's a free workshop, but we spend a day with the customer, sometimes two, going through their use cases, going through their current configuration, where they're at.

Even that end user you were talking about before, who shouldn't have to know about the storage.

They do need to know where their data is, discovering where the data sets are, and we'll get into AI in a minute, because I think AI really changes the game on all this.

But let's talk legacy IT, standard work cases, where these applications are, where their users are, where their customers and partners are, anybody they connect to digitally.

All of this stuff is part of the workshop, and then you figure out, okay, well, how are you doing things today?

Are you using MPLS?