at home, the page recognises the connection.
An OLT loses power and the phones light up. Agents answer the same question again and again, and the customers with a real line fault wait behind them.
"Slow" can be the Wi-Fi, a 100M router port, a cable, the area or a popular app. Without evidence, support guesses and sends a technician.
The first sign of an outage is often a complaint. By then the customer has already decided the network is bad.
The subscriber opens your operator-branded check page. The gateway maps the live connection to the line, so the page knows which line it is looking at without asking for a login, and shows one plain answer. It never shows a name, an address or a device, and it keeps no record. Rolling out per operator. Pick a situation.
The gateway maps the live connection to the line. Nothing to remember, nothing to reset, and it only ever answers about the connection it is asked from.
No name, no address, no device list on the page, and no record of the check is kept.
"May be slowing things" is a hint. "Likely a 100M port" says likely. Unknown says unknown, never "all fine".
When the router is down there is no home connection to recognise. So the subscriber sets a 6-digit PIN once, at home. Later, from mobile data, they log in with username and PIN and see what the network sees: since when the router is gone, how it went (signal lost points to power or fibre at home), whether it is trying to log in or being rejected, the area, the line, and what to do. Try it with the demo login.
Lockout after repeated wrong PINs. The same answer for a wrong username or a wrong PIN, so nobody can test who is a customer.
Only from home (the recognised connection) or by the operator. Never by email or by guessing.
Demo login: user-1042 / PIN 482915. In the demo, 3 wrong PINs lock the form; the real limit is set by the product. Rolling out per operator.
NOC2 sends incident notifications to Telegram or email. Each message says what, where (gateway, OLT or VLAN label, city), how many subscribers since when, and whose fault is likely. One message at the start, one at the end, never spam. Quiet hours, and rules per type, gateway, severity and channel.
Start message, then silence, then the end message. Names, numbers and times are invented.
Every month, each company gets a PDF: reliability, capacity, plan delivery, routers to replace, caches, service incidents, DNS health and the month-over-month trend. Turn the pages.
Illustrative report for "Example ISP". Every figure is invented.
The anonymous public status page shows popular services as "No widespread problems seen", a zone only during a confirmed problem, and "Not enough data" when it does not know. No operator names, no numbers except times.
The status page answers the internet. The self-check answers the subscriber's own line. Alerts and the monthly report answer your team. All from the same measurements.
"My internet is down" answers itself when the page says "problem in your area, 72% back".
When they do call, the agent already knows: line, Wi-Fi, router, area or app.
And "it's our area" too. Evidence for both sides of the conversation.
An alert with where, how many and why, before the first complaint.
OLTs, links, routers and caches to fix, ranked, in a PDF management will read.
No names on the page, no records kept, the same answer for any wrong login.
We will set up a branded self-check page and alerts on a live NOC2 and walk through a monthly report, on your questions.
Examples on this page are illustrative and anonymised. "Example ISP", gateway names, OLT and VLAN labels, cities, usernames, PINs, times, counts and percentages are invented demo values, not readings from any network. WhatsApp and Telegram are trademarks of their respective owners; BNGSOFT is not affiliated with them.
Product page: Support & operations · Talk to us