mlsanityData to 7 Oct 2026

FaulT-Bench: Towards Benchmarking Network Troubleshooting LLM Agents under Unreliable User Tickets

arXiv 2608.27021 ↗First posted 27 Aug 2026cs.NI cs.AIcited by 0

On the map: LLM agents and tool use → Software engineering coding agents

Abstract (arXiv)

LLM-based agents are increasingly proposed for network fault diagnosis, but existing benchmarks evaluate them only on accurate tickets and always assume a fault is present, conditions rarely met in practice. We present FaulT-Bench, a benchmark of 200 troubleshooting scenarios across eight network topologies, five reimplemented from public practitioner labs, spanning genuine faults, false fault reports, incorrect device attribution, and incorrect root-cause claims. To isolate how ticket wording affects diagnosis, we further rewrite 72 false-premise tickets into five reporter personas that vary reporter confidence and verifiable detail one factor at a time, holding the network state fixed. Our automated harness deploys each scenario in Kathar'a, lets agents interact through the NIKA tool interface, and scores free-text diagnoses with an LLM judge across outcome, fix, and reasoning quality. Evaluating SADE, ReAct, and Claude Code, we find all three are near-saturated on accurate tickets and robust to misdirection, yet degrade sharply when the network is healthy and the ticket is wrong, probing until a benign condition can be promoted to a root cause rather than concluding nothing is wrong. Persona rewrites show that how a ticket is written matters more than what it claims: a confidently wrong report is handled about as well as an accurate one, while a vague, underspecified report degrades performance sharply. The three agents also fail differently, from constant over-diagnosis to unanswered runs, at very different cost. These results position FaulT-Bench as a benchmark for developing agentic systems that can reason reliably over the noisy, unreliable tickets of real-world network troubleshooting.

Key facts. No citing papers in the map yet (data through 7 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. Builds on 8 of its 44 references that are in the map. First posted on arXiv 27 Aug 2026.

Builds on

8 of 44 references.

References · 8

  1. 2022ReAct: Synergizing Reasoning and Acting in Language Modelscited by 8,355
  2. 2023G-Eval: NLG Evaluation using GPT-4 with Better Human Alignmentcited by 2,205
  3. 2025AbstentionBench: Reasoning LLMs Fail on Unanswerable Questionscited by 129
  4. 2024Can LLMs Understand Computer Networks? Towards a Virtual System Administratorcited by 11
  5. 2025NetArena: Dynamic Benchmarks for AI Agents in Network Automationcited by 8
  6. 2025A Network Arena for Benchmarking AI Agents on Network Troubleshootingcited by 8
  7. 2026TelcoAgent-Bench: A Multilingual Benchmark for Telecom AI Agentscited by 4
  8. 2026SADE: Symptom-Aware Diagnostic Escalation for LLM-Based Network Troubleshootingcited by 3

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026AgentFixer: From Failure Detection to Fix Recommendations in LLM Agentic Systems
  2. 2026A Multi-Dataset Benchmark for Evaluating LLM Agents in Microservice Failure Diagnosis
  3. 2026LogDx-CI: Benchmarking Log Reduction Tools for LLM Root-Cause Diagnosis
  4. 2026CUJBench: Benchmarking LLM-Agent on Cross-Modal Failure Diagnosis from Browser to Backend
  5. 2026AgentDebugX: An Open-Source Toolkit for Failure Observability, Attribution, and Recovery in LLM Agents
  6. 2025Towards a Playground to Democratize Experimentation and Benchmarking of AI Agents for Network Troubleshooting
  7. 2026From Anomalies to Failures: Constructing Causal Error Graphs for Agentic Trace Diagnosis
  8. 2026AgentTether: Graph-Guided Diagnosis and Runtime Intervention for Reliable LLM Agent Operation