Trace Route Instructions

Game versions:  RS_Rune_final.png App_Icon-Circle.png  

A trace route maps the internet traffic between your computer and an internet destination and is often used to identify connectivity problems or delays.

 


Trace Route on Windows

 

 

test 

  1

Head to Start > Run

 

2

Open the cmd prompt - type cmd and press Enter.

 RS_Rune_final.png RuneScape users: 
Type tracert world1.runescape.com and press Enter.
Replace 1 with the world number you are trying to trace. 

 

 App_Icon-Circle.png OldSchool users:
Type tracert oldschool1.runescape.com and press Enter.

Although OSRS worlds begin with numbers in the 300s to 500s, those numbers won’t work for traceroutes. To run a traceroute to an OSRS  world  please subtract 300  from the in-game world number.

For example, OSRS World 301 would be tracert oldschool1.runescape.com

 

3

Take a screenshot of the information displayed and upload this to an image hosting website like Imgur

 

 


Trace Route on Mac 

 

test 
 

1

Launch Network Utility 

2

Click Traceroute 

RS_Rune_final.png RuneScape users: 
Type world1.runescape.com and press Enter.
Replace 1 with the world number you are trying to trace.

 

App_Icon-Circle.png OldSchool users:
Type oldschool1.runescape.com and press Enter.

Although OSRS worlds begin with numbers in the 300s to 500s, those numbers won’t work for traceroutes. To run a traceroute to an OSRS  world  please subtract 300  from the in-game world number. 

For example, OSRS World 301 would be oldschool1.runescape.com

 

3

Take a screenshot of the information displayed and upload this to an image hosting website like Imgur

 

  

What does this show?
A trace route will show the strength of your internet connection at different points from your system to the Jagex servers.

Your system will jump from locations around the world until it finally reaches a RuneScape world. It waits for a response from each 'hop' it makes, this response time is measured in milliseconds (ms). 

The time this takes is known as latency (or ping). The longer it takes to get a reply the higher your ping which results in connectivity problems.

 

What to look for
0ms to 60ms is acceptable latency, 60ms to 100ms or higher will lead to lag and disconnects.

If a large number of *'s are displayed, or timeouts, then this may indicate that there's a routing or stability issue on your connection.

Here's what a completed healthy traceroute should look like:

  

Got high latency?
Common solutions could be: 

 

 

Was this article helpful?