Read one status
bngbox status
Speaks in subscriber terms: which phase of session setup is affected, how many sessions, since when, which runbook.
BNGbox · Software & Care
You run your network. We stand behind it.
A cloud-native BNG is only an advantage if your team can work with it in production. Your own team or the systems integrator who already looks after your network runs operations. BISDN provides the software, patches and level-2/3 support behind it, from Berlin, on business days from 9am to 5pm.
Reply the same working dayRemote access outbound only, recordedSoftware & Care availableSupport from Berlin, DE · EN
The division of responsibility
Three parties, clear responsibilities.
Subscribers, services, network and data centre remain your responsibility, using the BNGbox GUI and the tools you use today. Your team or your integrator runs the platform. BISDN supports them with software, patches and support.
Your subscribers and services
Tariffs, RADIUS profiles, customer connections and first-level support, in the BNGbox GUI.
You
Your network and data centre
Routers, OLTs, uplinks, power and hardware with vendor support. You know them best.
You
The BNGbox platform
Kubernetes, the BNGbox components, monitoring and upgrades. Run by your team or your integrator, with level-2/3 support from BISDN.
You or your integrator
| Task | You or your integrator | BISDN |
|---|---|---|
| Hardware, data centre, power, connectivity | You | Reference list and advice |
| Operating system and Kubernetes | Operations | Level-2/3 support |
| BNGbox components: installation, configuration, upgrades | You, following documentation and runbooks | Releases, patches, support during upgrades |
| Subscriber and service configuration | You | Level-2/3 support |
| Platform monitoring and alerting | You | Tools and runbooks |
| Incidents: first level, subscriber side | You | Documentation |
| Incidents: platform, second and third level | You report, with a support bundle | BISDN, reply the same working day |
| Security patches and CVE handling | You apply | BISDN delivers |
| Configuration backup and restore | You, with our tool | Tool and documentation |
| Capacity planning and service review | You | On request |
What your operations team actually does
A three step incident management process
Generate one bundle
bngbox support-bundle
Collects logs, state and versions with subscriber identities pseudonymised, for BISDN technician review.
Make one call
Support hotline, business days 9am to 5pm
A BISDN developer takes up the case with the support bundle in hand and replies the same working day.
$ bngbox status
Platform OK
Control plane OK
Session setup DEGRADED
PPPoE: 12% of setups stall in phase 5
(VPP programming), 340 sessions
affected since 04:12 UTC
Likely component: bisdn-vpp-worker
Runbook: RB-05
Support bundle: ready, ticket #4821
Sessions active 48,212 (CP) / 47,872 (UP)Example output. The tool is under development.
Remote access on your terms
Supporting you securely
Outbound only
Your cluster opens an encrypted tunnel to BISDN.
Every session recorded
Audit logging provides a clear record for you.
Four eyes for emergencies
Elevated access requires approval by a second person at BISDN and expires automatically.
Kill switch
You can cut the connection at any time. The platform keeps running with local alerting.
Data minimisation
No subscriber identities leave your site. Support bundles are pseudonymised, logs stay with you.
Contractually fixed
Access rules, logging and data handling are part of the agreement and data processing annex.
What we need from you
Support requires both sides. These are your responsibilities.
These are the three things we need from you.
Hardware
Servers from our reference list
Qualified servers and network cards with vendor support and a spare node on site.
People
A named contact and a first level
A technical contact with a deputy, and a team that resolves individual subscriber issues using the GUI and runbooks.
Access
The tunnel and a maintenance window
Keep the remote access channel active so we can see what you see during an incident, and plan a regular maintenance window for upgrades, usually one night per quarter.
Wholesale
Wholesale as a Service: a BNG your resellers can order
Providers who serve other providers ask us the same question their resellers ask them: who runs this, and what can I sell? Your integrator and Software & Care answer the first half today. The second half is the next step.
One platform, one slice per reseller. Each reseller gets its own BNGbox slice with its own management GUI and a defined support path, on hardware you own, operated by you or your integrator. Slices, subscriber licences and access rights follow the contract and are provisioned automatically.
An honest timeline. Today, this means one slice per platform. Multiple reseller slices on one cluster and contract-driven provisioning are in development. The first wholesale customers help shape them and get a support path they did not have to build themselves.
Kubernetes cluster at the wholesale provider
Slice
Reseller A
own GUI · 10k sessions
Slice
Reseller B
own GUI · 5k sessions
Slice
Reseller C
ordered · provisioning
↔ provisioned from the contract · supported by BISDN · in development
Next step
Ask us for a demo
Half a day with your operations team, rather than your architects: in our lab, we stop components of a running BNGbox under load, and you see the alarms, status and recovery. Afterwards, we discuss your responsibilities, our response time and data handling, in writing.