Article
News
5
min read
Brad Bonavida

A Single BACnet Routing Bottleneck at Microsoft Led to 118,000 Hours of Missed Runtime Before Anyone Recognized It as a Systemic Issue

February 17, 2026

CBRE didn’t realize how much runtime Microsoft’s 80-building campus had been missing until after it fixed a nearly undetectable problem.

Months of high-volume routine comfort escalations, mainly hot/cold calls, went undiagnosed despite intensive controls troubleshooting. The culprit turned out to be a network bottleneck that had been quietly degrading operations for more than a year.

The campus runs 16,000 devices from 40 manufacturers across 800 BACnet channels, layered with four BMS platforms and an Iconics FDD application. When schedule overrides sometimes worked and sometimes didn’t, the teamrepeatedly escalated to the BMS vendor. “Traditional troubleshooting continually failed,” said April Yi of CBRE.

Packet-level analysis through Optigo Network's Visual BACnet tool eventually revealed repeated “busy router” messages associated with a single Allerton controller, which served as the bridge between two sides of the campus. The controller wasn’t misconfigured, and no system was incorrectly integrated. However, as the system had evolved over the years, network traffic patterns between FDD and BAS became suboptimal, allowing the problem to slip through the cracks.

After reassigning Iconics servers to reduce traffic through this single-controller bottleneck, the busy router diagnostic cleared, and response times improved.

Then the team looked backward.

From June 2023 through August 2025, they identified nearly 118,000 hours during which systems didn’t run as scheduled between 7:00 and 11:00 AM. “Thirty-eight percent of those assets did not turn on for more than 50% of the scheduled days,” Yi said.

Energy use dipped. Complaints rose.

The lesson wasn’t about a bad controller. “The red blinking light is not always where the problem is,” said Ping Yao of Optigo Networks. Without historical network visibility, the missed runtime looked like gremlins in BAS controllers.

‍

‍

Watch the full recording

Register for the next Nexus Labs event

Sign up for the newsletter to get 5 stories like this per week:

Sign Up for Access or Log In to Continue Viewing

Sign Up for Access or Log In to Continue Viewing

CBRE didn’t realize how much runtime Microsoft’s 80-building campus had been missing until after it fixed a nearly undetectable problem.

Months of high-volume routine comfort escalations, mainly hot/cold calls, went undiagnosed despite intensive controls troubleshooting. The culprit turned out to be a network bottleneck that had been quietly degrading operations for more than a year.

The campus runs 16,000 devices from 40 manufacturers across 800 BACnet channels, layered with four BMS platforms and an Iconics FDD application. When schedule overrides sometimes worked and sometimes didn’t, the teamrepeatedly escalated to the BMS vendor. “Traditional troubleshooting continually failed,” said April Yi of CBRE.

Packet-level analysis through Optigo Network's Visual BACnet tool eventually revealed repeated “busy router” messages associated with a single Allerton controller, which served as the bridge between two sides of the campus. The controller wasn’t misconfigured, and no system was incorrectly integrated. However, as the system had evolved over the years, network traffic patterns between FDD and BAS became suboptimal, allowing the problem to slip through the cracks.

After reassigning Iconics servers to reduce traffic through this single-controller bottleneck, the busy router diagnostic cleared, and response times improved.

Then the team looked backward.

From June 2023 through August 2025, they identified nearly 118,000 hours during which systems didn’t run as scheduled between 7:00 and 11:00 AM. “Thirty-eight percent of those assets did not turn on for more than 50% of the scheduled days,” Yi said.

Energy use dipped. Complaints rose.

The lesson wasn’t about a bad controller. “The red blinking light is not always where the problem is,” said Ping Yao of Optigo Networks. Without historical network visibility, the missed runtime looked like gremlins in BAS controllers.

‍

‍

Watch the full recording

Register for the next Nexus Labs event

Sign up for the newsletter to get 5 stories like this per week:

⭐️ Pro Article

Sign Up for Access or Log In to View

⭐️ Pro Article

Sign Up for Access or Log In to View

Are you interested in joining us at NexusCon 2026? Register now so you don’t miss out!

Join Today

Are you a Nexus Pro member yet? Join now to get access to our community of 600+ members.

Join Today

Have you taken our Smart Building Strategist Course yet? Sign up to get access to our courses platform.

Enroll Now
Conversation
Comments (-)
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Guest
•
6 hours ago
Delete

This is a great piece!

REPLYCANCEL
or register to comment as a member
POST REPLY
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Guest
•
6 hours ago
Delete

I agree.

REPLYCANCEL
or register to comment as a member
POST REPLY
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Get the renowned Nexus Newsletter

Access the Nexus Community

Head over to Nexus Connect and see what’s new in the community. Don’t forget to check out the latest member-only events.

Go to Nexus Connect

Upgrade to Nexus Pro

Join Nexus Pro and get full access including invite-only member gatherings, access to the community chatroom Nexus Connect, networking opportunities, and deep dive essays.

Sign Up