Open page contents
See when the connection became slow, unstable or unavailable.
Install Orb on a device and keep it running. Its timeline records the network experience instead of one unusually good test.
Explain game lag
Match lag spikes with delayed controls or broken voice chat.
Catch intermittent faults
Catch brief dropouts and evening-only problems.
Create usable evidence
Share a result that includes time, room and connection type.
Important: Orb shows patterns; it does not automatically decide who or what caused the fault.
Download it, keep it running, and cover the problem period.
For intermittent faults, keep Orb running through the time when the issue normally appears.
Install from the official Orb site
Choose your device, review permissions and start monitoring.
Leave it running through the bad period
Cover the gaming, call or evening period when it usually fails.
Compare locations and connection types
Compare the problem room, beside the router and Ethernet where practical.
Record the context
Note the device, room, connection, provider and exact problem time.
Orb Score is 0–100. Higher is better, but the timeline tells the story.
Use the overall score for a quick health check, then look at the three component scores to find the weak area.
Scores in the green bands that remain stable and match a clean timeline.
Repeated orange/red periods, outages or a score under 70 that lines up with your symptoms.
Official bands and score composition: Orb Scores & Metrics documentation.
Responsiveness: the key score for gaming lag.
Higher is better. It reflects latency, jitter and packet loss.
What healthy looks like
A high, stable score during the time you actually use the network.
What looks abnormal
Repeated red spikes that match delayed controls, broken voice or slow reactions.
Likely causes: weak WiFi, interference, heavy background traffic, router load or provider congestion.
Reliability: did the connection stay online?
Higher is better. A lower score points to repeated interruptions.
What healthy looks like
High and stable, with no outage periods.
What looks abnormal
Outage periods match call drops or internet disappearing.
Blank does not always mean outage: first confirm the Orb sensor was running.
Likely causes: provider outage, router reboot, unstable power, loose WAN connection or device sleep.
Speed: is the connection fast enough for the job?
Higher is better, but compare it with your plan and your own normal baseline.
What healthy looks like
Stable performance without repeated buffering or long waits.
What looks abnormal
A sustained drop, especially when Ethernet is also slow.
Content speed is not peak speed: Orb’s manual peak test is informational and is not included in the Orb Score.
Likely causes: plan limits, weak WiFi, congestion, background downloads or device limits.
Use simple comparisons to narrow down where the problem lives.
Compare one condition at a time. These patterns point to the next check, not a final verdict.
Try quick checks first, then fix the confirmed bottleneck.
01 10-minute checks
- Restart the device and router; check power and cables.
- Pause downloads, backups and heavy uploads.
- Compare beside the router and on Ethernet.
02 Structural improvements
- Improve router, access-point or mesh placement.
- Use Ethernet for fixed high-demand devices.
- Escalate repeatable wired faults with timestamps.
Fixed cabling: regulated in-wall, ceiling, lead-in and socket work is allocated to an ACMA-registered cabling partner.
Review permissions and remember that Orb is a third-party service.
Orb is an independent third-party service. Review its permissions and privacy policy before installing or sharing a public result. It records patterns but does not replace an on-site inspection.
No affiliate link. We do not receive payment when you download Orb, and results are not sent to us automatically.