Before We Start

People are going to ask what I want out of this. Money? A lawsuit? My job back?

None of the above.

I’m not bitter. I’m not on a revenge tour. I’m a web developer with thirty years of experience who ran a technical audit, found something serious, tried to do the right thing, and got told to mind my own business. Twice. So now I’m doing the next right thing — which is making sure the appropriate authorities know what I know.

The formal disclosures have already been filed. That process is underway. This post exists because the public deserves to understand how this kind of thing happens — and because if you work at a fiber ISP right now, there is a chance this is happening at your company too.

How Fiber Internet Actually Works

To understand what I found, you need to understand one piece of hardware: the ONT.

When a fiber internet company installs service at your home or apartment, a technician installs a small device on your wall called an ONT — Optical Network Terminal. It’s the endpoint of the fiber optic cable running into your building. It converts the light signal from the fiber into data your router can use.

When that ONT is powered on and active, it reports back to the company’s network management system in real time. It’s essentially saying: I’m here. I’m at this address. I’m live. I’m delivering internet service.

Fiber ISPs manage thousands — sometimes hundreds of thousands — of these devices across their networks. To do that at scale, they expose an API (Application Programming Interface) that allows internal systems to query the status of every ONT on the network. Which ones are active. Which ones are offline. What address each one is at.

Now — separately — the company has a billing system. That’s where customer accounts live. Customer name. Email address. Service address. What plan they’re on. What they owe each month.

In a properly functioning company, every active ONT maps to a customer record in the billing system. One device. One customer. One invoice per month. That’s the contract. That’s the revenue.

What I Found — The ONT Audit

As a web developer with access to internal systems, I had legitimate access to both the ONT API and the billing system exports. And being the kind of technically curious person I am, I decided to match them up.

Here’s exactly what I did:

The result was unambiguous. Over 3,000 active ONTs had zero corresponding customer records in the billing system.

Three thousand physical devices. Delivering live fiber internet. To real addresses. Right now. With no invoice. No customer account. No revenue.

The rolling revenue calculation was staggering. I built it month by month, going back through the estimated service period for each account. The number climbed fast. Really fast. Because that’s what happens when you multiply three thousand accounts by seventy dollars a month by dozens of months — the math compounds in a way that doesn’t feel real until you’re staring at it.

The Financial Breakdown

Let me show you exactly how $90 million disappears. It’s simpler than you’d think.

That last line is the one that keeps me up at night. Every single month that passes without this being addressed, another $209,880 evaporates. Permanently. Because of the most important financial reality in this entire story:

Why the Money Is Gone Forever

You cannot retroactively bill a customer for service they received but were never invoiced for. They have no contract. They received no bills. They made no agreement to pay retroactively.

Under basic contract law and consumer protection law — you simply cannot collect it. A court would throw that invoice out before you finished explaining the situation.

So every dollar represented in that table — roughly $90 million and counting — is gone. It was never real revenue. It can never become real revenue. The gap between what was represented and what was real is permanent and unrecoverable.

What Happened When I Reported It

I did what any responsible employee would do. I brought it up.

Why This Matters Beyond One Company

Here’s the part that keeps me talking about this even after everything.

This isn’t a sophisticated fraud. Nobody sat in a boardroom and hatched a scheme. What happened here is something much more mundane and much more dangerous: two systems that didn’t talk to each other, and a leadership team that didn’t want to hear about it.

The provisioning side of the business spins up service. A technician installs an ONT, activates it on the network, and moves on. The billing side of the business creates customer accounts. Somewhere in that handoff — for thousands of accounts — the billing record never got created. The ONT went live. The billing account didn’t.

Nobody noticed. Or nobody wanted to notice. And when someone did notice and raised it — repeatedly — the institutional response was silence.

The Investor and Lender Dimension

This story would be significant on its own as a billing operations failure. But there’s a layer on top of it that moves this into entirely different legal territory.

This company received a significant preferred equity investment from a major institutional investor — based in part on represented customer counts and revenue figures. It subsequently secured a $235 million debt facility from a major international bank — also based on represented operational scale.

If the approximately 3,000+ unverified, unbilled accounts were included in any customer count or revenue representation made to either of those parties during due diligence or ongoing reporting — then both transactions were consummated on the basis of materially inaccurate financial information.

Under ASC 606 — the GAAP standard for revenue recognition — revenue can only be recognized when performance obligations are satisfied and collectibility is probable. Customers who have never been invoiced fail that test. Their inclusion in any revenue or customer count representation constitutes a material misstatement of financial condition.

That is not a billing operations problem anymore. That is a securities and investor fraud problem.

The Legal Framework

I want to be clear about something: I am not a lawyer. None of this is legal advice. But I do know how to read case law, and the precedents in this area are not ambiguous.

What I’ve Done About It

I have formally submitted this disclosure to the appropriate federal and state regulatory authorities. That process is underway. I am not going to detail the specific filings publicly at this time, but the relevant agencies are aware of what I’ve described in this post.

I have also submitted a formal whistleblower disclosure letter — addressed to the company’s HR department, with simultaneous copies transmitted to the SEC, FTC, FCC Enforcement Bureau, Illinois Attorney General, Illinois Commerce Commission, Champaign County State’s Attorney’s Office, the company’s Board of Directors, and both financial parties whose capital is at risk.

That letter includes a formal litigation hold demand. Every person who received it is now legally obligated to preserve relevant records. Any destruction of records following receipt of that notice constitutes obstruction of justice.

What I Want

I reported this internally — twice — and was told to mind my own business. A colleague reported it independently and was ignored. The issue remains unresolved. The revenue gap keeps growing. The investors and lenders whose capital is at risk have a right to know what I know.

So I’m making sure they know.

This is Part 1 of the Whistleblower Series on SolarBluSeth.com. When this story becomes fully public — and it will — I’ll be here to walk through every detail. Subscribe to this blog, follow me on YouTube, and drop a comment below if you’ve seen something similar at your own company.

Because I suspect this is more common than anyone wants to admit.