Sarai Hannah Ajai's ASUS Router – Temporary Network Visibility Anomaly Preserving Uncertainty Pending Technical Verification

INCIDENT REPORT

ASUS Router – Temporary Network Visibility Anomaly

Preserving Uncertainty Pending Technical Verification

Reporting Party: Sarai Hannah Ajai

Documented Identity: Adult female (self-reported)

Device Involved: ASUS RT-AX1800S Wireless Router

Related Equipment: Netgear modem (ISP-provided), personal mobile and household devices

Incident Type: Network Status / Device Visibility Anomaly (Undetermined Cause)

1. Date and Time of Incident

December 23, 2025, approximately 7:19 PM (local time)

2. Location

Private residential apartment (Unit 2**), personal home network environment.

3. Description of Incident

At approximately 7:19 PM on December 23, 2025, while reviewing the ASUS Router mobile application installed on my iPhone, I observed that the application displayed only one connected device associated with my ASUS RT-AX1800S router. At that time, the application also displayed a “No Connection” status indicator.

This display was unexpected, as my household normally operates with approximately 15–16 connected devices (mobile phones, computers, and smart devices), all of which are configured to connect exclusively through the ASUS router. Despite the application display, my devices continued to have functional internet access.

The ASUS Router application indicated the presence of a valid WAN IP address assigned via DHCP, suggesting that upstream connectivity may have remained active. However, the discrepancy between the number of devices displayed and the expected device count could not be immediately explained.

4. Actions Taken

At approximately 7:23 PM, I rebooted the ASUS router. Following the reboot:

• The ASUS Router application refreshed.

• The expected number of devices (approximately 15–16) appeared correctly.

• Devices were shown as connected through password-protected Wi-Fi networks.

• No unknown or unfamiliar devices were observed.

Normal operation appeared to resume after the reboot.

5. Key Facts Observed

To the best of my knowledge and observation:

• No router credentials were changed.

• No Wi-Fi SSIDs were renamed or altered.

• No unknown devices appeared after reboot.

• No configuration changes were made by me prior to the event.

• Internet access on client devices remained functional during the anomaly.

• The event resolved fully after a routine router reboot.

6. Basis for Documentation

This incident is documented due to:

• The temporary discrepancy between expected and displayed connected devices.

• The brief “No Connection” status shown in the ASUS Router application.

• The importance of maintaining accurate records of network behavior.

• The absence of a clear, immediately identifiable cause.

At this time, the behavior is understood to be consistent with a temporary software, synchronization, or state-reporting issue, though no conclusion is asserted.

7. Scope and Limitations

This report:

• Does not assert unauthorized access, hacking, or malicious activity.

• Does not assert physical interference with network equipment.

• Does not attribute cause beyond observable facts.

• Is intended solely to preserve a factual record pending any future technical review.

8. Evidence and Documentation Notes

• Screenshots from the ASUS Router mobile application showing:

o Initial device count discrepancy

o Router status information

o Post-reboot device list

• Router model and configuration details (available upon request)

• Device count comparison before and after reboot

9. Follow-Up (If Required)

This report may be referenced if further clarification is requested from:

• ASUS technical support

• Internet service provider

• Device manufacturer or network diagnostics review

• Personal records for continuity of documentation

10. Statement of Accuracy

I affirm that the information contained in this report is true and correct to the best of my knowledge and recollection. This report documents observable network behavior without speculation or attribution pending further verification.

Report Prepared On: December 23, 2025

Printed Name: Sarai Hannah Ajai