Sarai Hannah Ajai Incident Report - Formal Incident Report Regarding Suspected Duplicate Apple iPhone 17 Device Association, Possible Device Mirroring or Cloning, Find My Location Irregularities, Verizon Orbic RC400L / Rayhunter Evidence, and General Building-Location Estimate

 Formal Incident Report Regarding Suspected Duplicate Apple iPhone 17 Device Association, Possible Device Mirroring or Cloning, Find My Location Irregularities, Verizon Orbic RC400L / Rayhunter Evidence, and General Building-Location Estimate

Redacted 

Prepared by: Sarai Hannah Ajai
Location: *****, ***** ******
Residence Reference: Apartment Unit 2**
Device / Service Involved: Apple iPhone 17; Verizon Orbic RC400L mobile hotspot; Rayhunter monitoring environment
Network Name Referenced: Verizon_RC400L-7E
Date of Report: May 12, 2026
Purpose of Report: Personal record, Verizon escalation, Apple security review, FCC/FTC complaint support, attorney review, law-enforcement review, and evidence preservation


I. Executive Summary

I, Sarai Hannah Ajai, am preparing this formal incident report to document a suspected device-security, wireless-network, and location-data irregularity involving my Apple iPhone 17, my Verizon Orbic RC400L mobile hotspot, the Rayhunter monitoring environment, and Apple Find My location information.

The primary concern is that my Verizon Orbic RC400L / Rayhunter-related device environment appeared to show two Apple iPhone 17-labeled devices connected to or associated with the Verizon_RC400L-7E Wi-Fi network. One Apple iPhone 17 is my known and authorized device. The second Apple iPhone 17-labeled entry was unexpected and is therefore documented as a suspected duplicate, mirrored, cloned, misidentified, stale, or otherwise unexplained device entry.

This report does not state as a final forensic conclusion that an unauthorized person definitively cloned, mirrored, or possessed a second Apple iPhone 17. Instead, this report preserves the observed facts, the screenshots, the Find My app location irregularity, the hallway photographs, the public Fargo Parcels property record, and the general building-estimation analysis used to compare the approximate Find My location dot against the interior common-area hallway near Apartment Unit 2**.

The strongest safe conclusion from the current evidence is:

Based on the Find My app screenshot, the blue dot appears to represent a general estimated location near the apartment building or exterior area, rather than a confirmed location inside Apartment Unit 2**. Because Find My location dots are approximate and can vary based on GPS, Wi-Fi, cellular, and indoor-location limitations, the screenshot should be treated only as a general location estimate. Based on this estimate, the screenshot does not specifically place the device inside Unit 2**.


II. Incident Background

For a period of time, I have experienced repeated concerns involving my Apple iPhone 17, Verizon wireless service, and device-location behavior. These concerns include:

  1. suspected device mirroring or cloning;
  2. unexplained or irregular device-location information;
  3. service instability;
  4. concern that an unauthorized device may be associated with my personal Wi-Fi or Verizon hotspot environment;
  5. concern that my Apple iPhone 17 identity or device name may be duplicated;
  6. concern that a second iPhone 17-labeled entry appeared in connection with the Verizon Orbic RC400L hotspot;
  7. concern that the Find My location point did not clearly correspond to the physical location of my authorized iPhone inside Unit 2**.

Because of these concerns, I used a Verizon Orbic RC400L mobile hotspot and Rayhunter monitoring environment to preserve technical evidence. I also took screenshots and photographs to document the physical building area, hallway layout, and approximate Find My app location position.


III. Devices, Network, and Evidence Sources Involved

A. Known Authorized Apple iPhone 17

My known authorized device is my personal Apple iPhone 17. This device is expected to appear in Apple Find My and may appear in Wi-Fi/router records when I intentionally connect it to a network.

B. Suspected Second Apple iPhone 17-Labeled Entry

The second Apple iPhone 17-labeled entry is unexpected. I did not knowingly authorize a second Apple iPhone 17 to connect to my Verizon Orbic RC400L hotspot or to appear as a duplicate device entry.

The second entry may represent several possible conditions, including but not limited to:

  1. a true second physical iPhone 17;
  2. a mirrored or cloned device indicator;
  3. an Apple Private Wi-Fi Address-related duplicate;
  4. a stale DHCP or hotspot client entry;
  5. a router interface display issue;
  6. an old device record not actively connected;
  7. a renamed or misidentified device;
  8. an unauthorized Wi-Fi association;
  9. an Apple ID / Find My device-list irregularity;
  10. a Verizon account, SIM/eSIM, or device-authentication issue.

This report preserves the second iPhone 17-labeled entry as a suspicious technical indicator requiring further review.

C. Verizon Orbic RC400L / Verizon_RC400L-7E

The Verizon Orbic RC400L mobile hotspot is the device environment where the suspected duplicate Apple iPhone 17-labeled entry was observed. The relevant Wi-Fi network name referenced in this report is:

Verizon_RC400L-7E

D. Rayhunter Monitoring Environment

Rayhunter was used as a supplemental monitoring environment on the Verizon Orbic RC400L. Rayhunter evidence is relevant to the broader technical context, but the Rayhunter dashboard and the Wi-Fi connected-device list should be evaluated as separate evidence categories.

The Rayhunter environment relates to cellular-monitoring evidence. The Verizon Orbic Wi-Fi connected-device evidence relates to local Wi-Fi client association. Both categories are relevant, but neither category alone conclusively proves device cloning.

E. Apple Find My App Screenshot

The Find My screenshot is relevant because it shows a blue location dot associated with the device-location environment. The screenshot is being used only as a general estimated location reference, not as a precise indoor measurement.

F. Hallway / Common-Area Photographs

The hallway photographs document the physical common-area layout near Apartment Unit 2**. They show the interior hallway, visible exit-area direction, wall fixtures, carpeted floor, doors, wood-paneled wall sections, and fixed reference points.

G. Fargo Parcels Screenshot

The Fargo Parcels screenshot is relevant because it documents public property information, including:

  • Total Building Sq. Ft.: 23,908
  • Property Type: Apartment
  • Land Use: Apartment
  • Number of Apartment Units: 24
  • Lot Area: 45,566 sq. ft. / 1.046 acres

This information was used only for a general building-estimation model, not for an exact architectural measurement.


IV. Timeline and Observed Events

On or about May 12, 2026, I captured screenshots and photographs relevant to this incident. The uploaded Find My screenshot displays a time of approximately 6:21, and the Fargo Parcels screenshot displays a desktop timestamp of approximately Tuesday, May 12, 6:47 PM.

The relevant observations include:

  1. A Verizon Orbic RC400L / Rayhunter-related device environment appeared to show two Apple iPhone 17-labeled devices associated with the Verizon_RC400L-7E Wi-Fi network.
  2. One iPhone 17-labeled device was my known and authorized Apple iPhone 17.
  3. The second iPhone 17-labeled entry was unexpected.
  4. A Find My app screenshot showed a blue estimated location dot near the building/home location area.
  5. Hallway photographs were taken from or near the common-area hallway outside Apartment Unit 2**.
  6. The common hallway width was measured at approximately 72 inches, or 6 feet.
  7. Public Fargo Parcels property data was reviewed to obtain the total building square footage.
  8. A general building-estimation calculation was performed to compare the approximate Find My dot location against the building and hallway context.

V. Primary Technical Concern: Two iPhone 17-Labeled Devices on Verizon_RC400L-7E

The primary technical concern is that the Verizon Orbic RC400L / Rayhunter-related device environment appeared to show two Apple iPhone 17-labeled devices connected to or associated with the Verizon_RC400L-7E Wi-Fi network.

My known Apple iPhone 17 should appear when intentionally connected. However, the appearance of a second iPhone 17-labeled device is suspicious because I did not knowingly authorize a second Apple iPhone 17 to connect to my hotspot.

The second entry may be benign or may be significant. It may be caused by router caching, Apple Private Wi-Fi Address behavior, a duplicate device name, stale device history, or a normal software display issue. It may also indicate unauthorized access, mirroring, cloning, or device-identity irregularity. Because the cause is not yet confirmed, the evidence should be preserved and reviewed by Verizon, Apple, or a qualified technical reviewer.


VI. Find My App Location Estimate and Analysis

A. Purpose of the Find My Analysis

The Find My app screenshot was reviewed to determine whether the blue location dot could reasonably be used to place the suspected second Apple iPhone 17 inside Apartment Unit 2**.

The conclusion is that the Find My screenshot does not provide enough precision to place the suspected device inside Unit 2**.

The Find My dot is useful only as a general location estimate.

B. Strongest Safe Conclusion

The strongest safe conclusion is:

Based on the Find My app screenshot, the blue dot appears to represent a general estimated location near the apartment building or exterior area, rather than a confirmed location inside Apartment Unit 2**. Because Find My location dots are approximate and can vary based on GPS, Wi-Fi, cellular, and indoor-location limitations, the screenshot should be treated only as a general location estimate. Based on this estimate, the screenshot does not specifically place the device inside Unit 2**.

C. Basis for the Estimate

The estimate was reached by comparing:

  1. the Find My blue dot position;
  2. the home/building icon position shown in the Find My screenshot;
  3. the apparent building-area map representation;
  4. the uploaded interior hallway photographs;
  5. the physical common-area hallway width measurement of 72 inches / 6 feet;
  6. the public Fargo Parcels building square-footage record;
  7. the general building-estimation calculation;
  8. and the visual relationship between the dot and the likely building/exterior area.

The dot appears near the building/home marker, but it does not provide an exact apartment-unit coordinate. It does not show a measured distance from Unit 2**, does not identify the interior hallway, does not identify a specific apartment door, and does not include a reliable indoor map scale.

D. What the Find My Dot Can and Cannot Support

Question

Careful Answer

Does the dot appear to confirm a location inside Unit 2**?

No, not from the screenshot alone.

Does the dot appear more general/exterior than exact indoor?

Yes, based on visual review.

Can we prove the second iPhone was outside the apartment?

No, not from Find My alone.

Can we say the dot does not specifically identify Unit 2**?

Yes.

Can the dot be treated as an exact hallway or apartment location?

No.

Can the dot be used as a general estimated location reference?

Yes.

E. Find My Accuracy Limitation

Apple Find My location dots can vary because of:

  1. GPS signal limitations;
  2. Wi-Fi positioning;
  3. cellular positioning;
  4. indoor building interference;
  5. map-rendering limitations;
  6. device battery and connection state;
  7. delayed location updates;
  8. multi-device account display behavior;
  9. and the difference between a device’s true physical location and an app’s estimated map position.

For those reasons, the Find My screenshot should not be described as an exact physical measurement.

F. Location Conclusion

The Find My app screenshot does not specifically identify Apartment Unit 2** as the location of the suspected second Apple iPhone 17. The best conclusion is that the dot is a general near-building or exterior-area estimate only.


VII. Building and Common-Area Measurement Analysis

A. Public Property Measurement Source

The Fargo Parcels screenshot shows:

Total Building Sq. Ft.: 23,908

This number is a property-record figure. It is not a hallway-only measurement. It may include apartment interiors, walls, stairways, mechanical areas, utility areas, and other building components.

B. Correction to the Original Calculation

An earlier rough calculation divided the total building square footage by three floors. That was too broad because the property reportedly includes three buildings, each with three floors.

Therefore, the more careful general-estimation model is:

23,908 total building sq. ft. ÷ 3 buildings ÷ 3 floors ÷ 2 sides

This equals:

1,328.22 sq. ft. per side, per floor

C. Hallway Width Measurement

The common-area hallway width was measured at approximately:

72 inches = 6 feet

Because the hallway width is known, estimated length can be calculated from square footage using:

Length = Area ÷ Width

D. General Estimated Side Length

Using the estimated side/floor allocation:

1,328.22 sq. ft. ÷ 6 ft. width = 221.37 linear feet

This produces an estimated general side/floor length of:

Approximately 221.37 linear feet

This is not a tape-measured hallway length. It is a general building-estimation figure based on public parcel data and the 6-foot hallway width.

E. Visible Hallway Estimate Near Unit 205

From the uploaded hallway photograph taken near Apartment Unit 2**, the visible hallway segment toward the end/exit direction appears substantially shorter than the full estimated 221.37-foot side length.

Based on visual review, the visible hallway segment from near Unit 2** toward the end/exit direction appears approximately:

35 to 45 linear feet

Using the measured 6-foot hallway width, the visible segment would estimate to:

Estimated Visible Length

Calculation

Estimated Visible Common-Area Sq. Ft.

35 ft

35 × 6

210 sq. ft.

40 ft

40 × 6

240 sq. ft.

45 ft

45 × 6

270 sq. ft.

Therefore, the visible hallway segment near Unit 2** is estimated at approximately:

210 to 270 square feet, with a midpoint estimate of approximately 240 square feet.

F. Why the Building Estimate Does Not Prove an Interior Dot Location

The building estimate helps provide scale, but it does not convert the Find My dot into a precise indoor location.

The Find My dot does not show:

  1. a tape-measured distance;
  2. a unit boundary;
  3. a hallway line;
  4. a floor number;
  5. an apartment number;
  6. a reliable indoor map;
  7. or a confirmed position inside Unit 2**.

Therefore, the building estimate supports only a general comparison. It does not prove that the suspected second device was inside Unit 2**.


VIII. Interior Hallway Photographs and Physical Reference Points

The uploaded hallway photographs show the common-area hallway outside or near Unit 2**. They document:

  1. a narrow interior hallway;
  2. wall-to-wall width reported as approximately 72 inches / 6 feet;
  3. hallway carpet;
  4. wall-mounted lights;
  5. apartment doors;
  6. a visible exit sign;
  7. a wood-paneled wall section;
  8. utility-panel areas;
  9. vents and fixed wall features;
  10. the general direction from Unit 2** toward the end/exit area.

These photographs are useful to document the physical environment. They support an approximate hallway-layout analysis. However, they do not by themselves prove where the suspected second iPhone was located.


IX. Technical Interpretation of the Location Evidence

The location evidence should be described with precision.

A. Supported Statements

The evidence supports these statements:

  1. The Find My screenshot shows a blue estimated location dot.
  2. The dot appears near the apartment building/home-location area.
  3. The dot should be treated as approximate.
  4. The dot does not specifically identify Unit 2**.
  5. The hallway photos document the interior common-area layout near Unit 2**.
  6. The measured hallway width is approximately 72 inches / 6 feet.
  7. Public property data supports a general building-scale estimate.
  8. The general building estimate does not convert the Find My dot into a precise indoor position.

B. Unsupported Statements

The current evidence does not support these statements as final conclusions:

  1. that the second iPhone 17 was definitely inside Unit 2**;
  2. that the second iPhone 17 was definitely outside the building;
  3. that the second iPhone 17 was definitely in the hallway;
  4. that a specific person possessed the device;
  5. that the Find My dot gives an exact foot measurement;
  6. that the Find My dot identifies a specific apartment unit;
  7. that the Find My screenshot alone proves device cloning;
  8. that the hallway photographs alone prove the device’s physical location.

C. Careful Final Location Interpretation

The careful final interpretation is:

The Find My app screenshot appears to show a general estimated location near the apartment building or exterior area. It does not specifically place the suspected second Apple iPhone 17 inside Apartment Unit 2**. The dot should be treated only as an approximate location indicator because Find My location points can vary based on GPS, Wi-Fi, cellular, and indoor-location limitations.


X. Service Instability and Device-Behavior Concerns

The suspected duplicate iPhone 17-labeled entry is part of a broader pattern of service and device concerns. These include:

  1. abnormal or unstable service behavior;
  2. location irregularities;
  3. suspected mirroring or cloning;
  4. concern that Apple Find My does not consistently match expected physical location;
  5. concern that the Verizon Orbic RC400L showed more iPhone 17-labeled device activity than expected;
  6. concern that my Apple iPhone 17 may be subject to unauthorized account or device duplication;
  7. concern that a Wi-Fi client, Apple ID session, SIM/eSIM profile, or device identity may be misused or misrepresented.

These issues require technical review. A user-facing screenshot can preserve evidence, but Verizon, Apple, or a qualified reviewer would be needed to evaluate device identifiers, timestamps, DHCP leases, MAC/private addresses, SIM/eSIM records, Apple ID trusted devices, and account-security history.


XI. Technical Limitations and Alternative Explanations

Several non-criminal or technical explanations may account for the second iPhone 17-labeled entry. This report preserves those possibilities to avoid overstating the evidence.

Possible explanations include:

  1. Apple Private Wi-Fi Address behavior creating different network identifiers.
  2. Stale DHCP lease from a prior connection.
  3. Hotspot admin-interface delay or display issue.
  4. A duplicate device name appearing in the Orbic client list.
  5. A previously connected device still shown after disconnection.
  6. A real second iPhone 17 within range of the Wi-Fi network.
  7. Unauthorized Wi-Fi access if the hotspot password was known or exposed.
  8. Apple ID trusted-device irregularity if an unknown device is linked to the account.
  9. SIM/eSIM irregularity if Verizon records show unknown device identifiers.
  10. Device mirroring or cloning indicator if further evidence confirms duplicate identifiers, unauthorized sessions, or account compromise.

Because multiple explanations are possible, the evidence should be preserved and reviewed.


XII. Evidence Preserved

The following evidence has been preserved or should be preserved:

  1. Find My app screenshot showing the blue estimated location dot.
  2. Verizon Orbic RC400L / Rayhunter-related screenshots or records.
  3. Connected-device evidence showing two Apple iPhone 17-labeled entries, if available.
  4. Fargo Parcels public property screenshot showing 23,908 total building square feet.
  5. Hallway photographs taken near Unit 2**.
  6. Hallway photographs showing the exit-area direction.
  7. Hallway photographs showing the floor/common-area width context.
  8. Notes showing the hallway width measurement of approximately 72 inches / 6 feet.
  9. General building-estimation calculations.
  10. Notes regarding service instability and location irregularities.
  11. Any Verizon support, fraud, account-security, or escalation records.
  12. Any Apple ID security or Find My screenshots.
  13. Any Rayhunter captures, ZIP files, PCAP files, QMDL files, logs, or warning screens.

XIII. Exhibit List

Exhibit A — Verizon Orbic RC400L / Rayhunter Connected-Device Evidence

Screenshot or photograph showing the Verizon Orbic RC400L / Rayhunter-related environment and the reported connected-device condition involving two Apple iPhone 17-labeled entries.

Exhibit B — Apple Find My Screenshot

Screenshot showing Apple Find My device information and a blue estimated location dot. This exhibit is relevant to location irregularity concerns and the general near-building or exterior-area estimate.

Exhibit C — Find My Estimated-Location Analysis

Written analysis explaining that the Find My app dot is approximate, does not confirm a location inside Unit 2**, appears more general/exterior than exact indoor, and does not specifically identify Apartment Unit 2**.

Exhibit D — Fargo Parcels Public Property Screenshot

Screenshot showing public property data, including 23,908 total building square feet, apartment property classification, and 24 apartment units.

Exhibit E — General Building-Estimation Calculation

Written calculation:

23,908 ÷ 3 buildings ÷ 3 floors ÷ 2 sides = 1,328.22 sq. ft. per side/floor
1,328.22 sq. ft. ÷ 6 ft. hallway width = 221.37 linear feet

This exhibit provides general scale only and should not be treated as a precise architectural measurement.

Exhibit F — Hallway Photograph Taken Near Unit 2**

Photograph showing the common-area hallway from the area near Apartment Unit 205 toward the visible end/exit direction.

Exhibit G — Hallway Photograph Showing Exit-Area Direction

Photograph showing the exit sign, wall-mounted fixtures, wood-paneled wall sections, and hallway configuration.

Exhibit H — Hallway Width and Common-Area Measurement Notes

Measurement notes stating that the common-area hallway width was measured at approximately 72 inches / 6 feet.

Exhibit I — Visible Hallway Segment Estimate

Written estimate stating that the visible hallway segment from near Unit 2** toward the end/exit direction appears approximately 35 to 45 feet, producing an estimated visible floor area of approximately 210 to 270 square feet.

Exhibit J — Service-Instability and Device-Behavior Notes

Written notes documenting service instability, suspected mirroring/cloning concerns, location irregularities, and abnormal connected-device observations.

Exhibit K — Verizon / Apple Account-Security Review Request

Written request for Verizon and Apple to review SIM/eSIM records, device identifiers, trusted devices, Apple ID sessions, Wi-Fi client records, account-access history, and related security records.


XIV. Requested Verizon Review

I request that Verizon review the following:

  1. whether any unknown IMEI, IMEI2, ICCID, EID, or SIM/eSIM identifier is associated with my Verizon line;
  2. whether any SIM change, eSIM download, eSIM transfer, or device activation occurred without my authorization;
  3. whether any unknown device was associated with my line or account;
  4. whether any port-out, transfer PIN, or number-transfer activity occurred;
  5. whether the Verizon Orbic RC400L recorded multiple Wi-Fi client entries for iPhone 17-labeled devices;
  6. whether the Orbic interface can distinguish active clients from stale cached clients;
  7. whether the connected-device list includes MAC/private addresses, IP addresses, timestamps, or DHCP lease details;
  8. whether Verizon can confirm whether the second iPhone 17-labeled entry was an active device or a stale/local-display artifact;
  9. whether account protections such as number lock, port protection, account takeover protection, and SIM/eSIM security protections are active.

XV. Requested Apple Review

I request that Apple or an Apple security reviewer evaluate:

  1. Apple ID trusted devices;
  2. Find My device list;
  3. unknown Apple ID sessions;
  4. two-factor authentication history;
  5. iCloud account access history, if available;
  6. device names associated with my Apple ID;
  7. configuration profiles;
  8. VPN or MDM enrollment;
  9. certificates;
  10. Private Wi-Fi Address behavior;
  11. whether the duplicate iPhone 17-labeled network entry could be caused by Apple privacy features or device-name behavior.

XVI. Recommended Follow-Up Evidence Steps

To strengthen the record, the following evidence steps should be performed:

  1. Screenshot the Orbic connected-device list showing the two iPhone 17-labeled entries.
  2. Record the exact date and time.
  3. Write down each device entry’s IP address, MAC/private address, and device name, if visible.
  4. Disconnect the known Apple iPhone 17 from Verizon_RC400L-7E.
  5. Screenshot whether any iPhone 17-labeled entry remains connected.
  6. Reconnect the known Apple iPhone 17.
  7. Screenshot the updated device list.
  8. Change the Verizon Orbic Wi-Fi password.
  9. Reboot the Orbic.
  10. Confirm whether the suspected second entry returns.
  11. Preserve Rayhunter captures from the same time period.
  12. Preserve Find My screenshots from the same time period.
  13. Check Apple ID trusted devices.
  14. Check iPhone Wi-Fi settings for Private Wi-Fi Address status.
  15. Contact Verizon for SIM/eSIM, account-access, and device-identifier review.

XVII. Formal Statement

I did not authorize any person to mirror, clone, duplicate, access, control, monitor, intercept, or interfere with my Apple iPhone 17, Apple ID, Verizon wireless account, Verizon Orbic RC400L, Verizon_RC400L-7E Wi-Fi network, or related electronic communications.

I did not knowingly authorize a second Apple iPhone 17 to connect to my Verizon Orbic RC400L hotspot. If a second Apple iPhone 17-labeled entry was truly connected, I request that Verizon, Apple, or a qualified technical reviewer determine whether the entry was benign, stale, misidentified, or evidence of unauthorized access.

The current evidence supports a serious security concern requiring review. It does not yet provide final proof of the exact cause.


XVIII. Final Location and Find My Conclusion

The Find My app screenshot should be treated as an approximate location reference only.

Based on visual review, the blue dot appears to represent a general estimated location near the apartment building or exterior area. It does not provide a precise indoor coordinate and does not specifically place the suspected second Apple iPhone 17 inside Apartment Unit 2**.

The hallway photographs, 72-inch hallway-width measurement, Fargo Parcels public property screenshot, and general building-estimation calculation provide useful context. However, they do not convert the Find My dot into an exact apartment or hallway location.

The strongest accurate conclusion is:

Based on the Find My app screenshot, the blue dot appears to represent a general estimated location near the apartment building or exterior area, rather than a confirmed location inside Apartment Unit 2**. Because Find My location dots are approximate and can vary based on GPS, Wi-Fi, cellular, and indoor-location limitations, the screenshot should be treated only as a general location estimate. Based on this estimate, the screenshot does not specifically place the device inside Unit 2**.

Additional careful conclusions are:

Question

Careful Answer

Does the dot appear to confirm a location inside Unit 2**?

No, not from the screenshot alone.

Does the dot appear more general/exterior than exact indoor?

Yes, based on visual review.

Can the screenshot prove the second iPhone was outside my apartment?

No, not from Find My alone.

Can the screenshot show that the dot does not specifically identify Unit 2**?

Yes.


XIX. Closing Statement

This report is prepared to preserve my observations, screenshots, photographs, measurements, and technical concerns in a clear written record. I am requesting that the evidence be reviewed seriously because the reported duplicate Apple iPhone 17-labeled entry, service instability, Find My location irregularity, and device-security concerns may involve unauthorized access, account compromise, device-mirroring indicators, device-cloning indicators, or technical network irregularities requiring expert review.

This report is not intended to overstate the evidence. It is intended to document the facts, preserve the exhibits, identify the technical questions, and request proper review of the Verizon Orbic RC400L, Apple iPhone 17, Apple Find My, Verizon account, SIM/eSIM records, Apple account records, and related device-authentication evidence.

Respectfully submitted,

Sarai Hannah Ajai
*****, ***** ******
Date: May 12, 2026



















Comments