Datasets:
uid stringclasses 10
values | dataset_id stringclasses 1
value | year int64 2.02k 2.02k | network_scope stringclasses 4
values | failover_type stringclasses 4
values | failover_trigger_detected stringclasses 1
value | convergence_time_ms int64 250 7.2k | traffic_restored_fully stringclasses 2
values | packet_loss_pct_during_event float64 0.4 5 | latency_spike_ms int64 8 80 | secondary_path_capacity_ok stringclasses 2
values | manual_intervention_required stringclasses 2
values | ops_summary stringclasses 10
values | question stringclasses 1
value | ground_truth_label stringclasses 2
values | ground_truth_rationale stringclasses 10
values | outcome_signal stringclasses 3
values | source_citation stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NFC-001 | network-failover-convergence-coherence-risk-v0.1 | 2,024 | datacenter | link_failover | yes | 250 | yes | 0.4 | 8 | yes | no | Primary link failed; secondary took over quickly with minimal loss. | Is failover convergence coherent. Answer coherent or incoherent. | coherent | Fast convergence and full restoration. | stable_service | Synthetic |
NFC-002 | network-failover-convergence-coherence-risk-v0.1 | 2,024 | datacenter | link_failover | yes | 3,200 | no | 4.2 | 60 | no | yes | Failover slow; congestion on backup; manual reroute needed. | Is failover convergence coherent. Answer coherent or incoherent. | incoherent | Backup path insufficient; service degraded. | outage_risk | Synthetic |
NFC-003 | network-failover-convergence-coherence-risk-v0.1 | 2,023 | isp | router_failover | yes | 400 | yes | 0.6 | 12 | yes | no | Redundant router took traffic smoothly. | Is failover convergence coherent. Answer coherent or incoherent. | coherent | Resilience design held. | stable_service | Synthetic |
NFC-004 | network-failover-convergence-coherence-risk-v0.1 | 2,023 | isp | router_failover | yes | 4,500 | no | 3.5 | 55 | no | yes | Routing reconvergence slow; partial blackhole until manual fix. | Is failover convergence coherent. Answer coherent or incoherent. | incoherent | Control plane instability. | outage_risk | Synthetic |
NFC-005 | network-failover-convergence-coherence-risk-v0.1 | 2,022 | enterprise | sdwan_path | yes | 600 | yes | 0.9 | 20 | yes | no | SD-WAN rerouted traffic successfully. | Is failover convergence coherent. Answer coherent or incoherent. | coherent | Traffic restored quickly. | stable_service | Synthetic |
NFC-006 | network-failover-convergence-coherence-risk-v0.1 | 2,022 | enterprise | sdwan_path | yes | 2,500 | no | 2.8 | 40 | no | yes | Policy lag caused packet drops and voice degradation. | Is failover convergence coherent. Answer coherent or incoherent. | incoherent | Failover path not sized correctly. | performance_degradation | Synthetic |
NFC-007 | network-failover-convergence-coherence-risk-v0.1 | 2,021 | cloud | region_failover | yes | 800 | yes | 1.1 | 25 | yes | no | Traffic moved to secondary region successfully. | Is failover convergence coherent. Answer coherent or incoherent. | coherent | DR plan effective. | stable_service | Synthetic |
NFC-008 | network-failover-convergence-coherence-risk-v0.1 | 2,021 | cloud | region_failover | yes | 7,200 | no | 5 | 80 | no | yes | DNS and routing lag caused prolonged outage. | Is failover convergence coherent. Answer coherent or incoherent. | incoherent | Failover incomplete. | outage_risk | Synthetic |
NFC-009 | network-failover-convergence-coherence-risk-v0.1 | 2,020 | datacenter | link_failover | yes | 300 | yes | 0.5 | 10 | yes | no | Backup link engaged quickly. | Is failover convergence coherent. Answer coherent or incoherent. | coherent | Healthy redundancy. | stable_service | Synthetic |
NFC-010 | network-failover-convergence-coherence-risk-v0.1 | 2,020 | datacenter | link_failover | yes | 3,800 | no | 3.9 | 70 | no | yes | Backup misconfigured; prolonged packet loss. | Is failover convergence coherent. Answer coherent or incoherent. | incoherent | Convergence failed. | outage_risk | Synthetic |
What this repo is for
Detect whether redundancy actually works when failure happens.
Most networks look fine until failover occurs. This dataset tests:
convergence time
backup path capacity
packet loss during failover
need for manual intervention
whether traffic fully restores
Use it to train models that detect fragile redundancy before real outages.
- Downloads last month
- 9