Questions we get before the first call

The device model or the service you want tested, the KPIs that matter to you (throughput, latency, sessions, convergence time, SLA thresholds) and the deadline. With that an engineer drafts a test plan within one business day and a quote follows in 1–3 business days.

Yes, before any configuration or device detail is exchanged. We work under your template or ours. Clients are never named on the site or in sales calls, whatever the size of the project.

Routers, switches, firewalls and NGFW, SD-WAN and VPN gateways, Wi-Fi access points and controllers, mobile core and transport functions, AI fabric switches with RoCEv2, virtual appliances and cloud services, web portals with the infrastructure in front of them. Attack traffic runs only on the bench, against the unit under test; live infrastructure and penetration testing are out of scope.

Often yes. Vendors and distributors lend evaluation units for a bake-off; we receive the unit, cable it in the rack and return it after the run. You get one report across all candidates, measured the same way.

One rack in Armenia. Your engineers open a session in a browser over HTTPS and see the generators, the counters and the device console live. On request a load module ships to your site and connects back to the rack.

L2-3 generators at 1G, 10G and 100G, L4-7 and security engines at 200G and above, WAN emulators per link, a Wi-Fi bench up to Wi-Fi 6 with Wi-Fi 7 in progress, 100G ports for RoCEv2 agreed per setup, plus rack space and virtual capacity for your device.

No. Bench time always comes with a TEST4NET engineer who wires the setup, runs the tests and signs the report. You can drive the session yourself under a bench-access plan; the instruments stay in our rack.

Yes. A hosted unit stays cabled with KVM and serial access, so a new firmware or policy can be re-tested in days instead of re-shipping the box. Storage terms are part of the plan.

Eight hours of bench time with an engineer, including setup, runs and the daily note. Most RFC 2544 runs on one unit fit in 1–3 days; a firewall profile under RFC 9411 takes 3–5; a Y.1564 service set runs 2 to 24 hours of traffic plus setup.

RFC 2544, RFC 2889, RFC 9411 with RFC 3511, RFC 6349 and ITU-T Y.1564 have their own pages. RFC 5180, ITU-T Y.1731 and TR-398 run on request. Protocol tests (BGP, OSPF, IS-IS, EVPN, IPsec, TLS) follow the test plan agreed with you.

Commercial traffic generators and analysers from the major test vendors, our own stateful generator for application mixes, WAN emulators and a Wi-Fi bench. The plan names the tool behind each test; there is no single default vendor.

We note the failing step, capture counters and packets, and repeat the run so the failure is reproducible. You decide whether to stop, fix and re-run, or continue with the rest of the plan. Re-runs on the same setup are billed as bench time, not as a new project.

Yes. The session is shared in the browser, our engineer is on chat, and you can drive parts of the run under supervision. Daily notes say what passed and what did not.

Every run with its settings, the raw counters, the pass or fail against the agreed thresholds, captures where relevant, and a summary page a manager can read in a minute. A test plan matrix at the front shows what was covered.

The report is yours. You can quote it in a tender, a vendor negotiation or a board paper. We never publish it and never name you; if you want a joint public benchmark, that is a separate agreement.

Working files are kept for the duration of the engagement plus the retention period in the Privacy Policy, then deleted. You receive the full set with the report.

By the test plan: bench days, engineer days and any shipping. Bench access plans are priced per month. Prices are quoted per project and are not published on the site.

Two products are in beta: a stateful traffic generator priced per gigabit and WANemu for link impairment. Until the public release they are shown on demo and offered through a beta list; after it a licence for your own lab is planned.

Attacks on live infrastructure, penetration testing, equipment rental without an engineer, and projects that need a named public reference. Attack and threat traffic runs only on the bench, against the unit under test, as part of security resilience testing.

Operators, integrators and vendors in Armenia, Kazakhstan, Turkey, Serbia, Europe, the Middle East, Latin America, South-East Asia and Australia. Work is done remotely over the bench; devices ship to the rack.