CHECKSERVERPING
Gaming Ping Checker
Deadlock

Deadlock Ping Test

MOBA Shooter by Valve Corporation

Updated Published

Tick Rate
Source 2 server-based
Target Ping
<60ms
Protocol
Steam Datagram Relay (SDR)

Ping Test

28 server regions · 5 rounds

Test duration

Quick check: 5 rounds per region.

Ready5 rounds per test

Connection report

Find The Best Server

Run a test to measure your ping to the game server, also measure jitter and averages.

Min
—
Avg
—
Max
—
Jitter
—
Failed
—
Samples
—
Latency over time60 ms ping target
Counted measurements will appear here after warm-up.
  1. US East - Virginia
    Sterling · NA
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  2. US East - Atlanta
    Atlanta · NA
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  3. US Central - Dallas
    Dallas · NA
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  4. US Central - Chicago
    Chicago · NA
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  5. US West - Los Angeles
    Los Angeles · NA
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  6. US West - Seattle
    Seattle · NA
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  7. EU West - Amsterdam
    Amsterdam · EU
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  8. EU West - London
    London · EU
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  9. EU Central - Frankfurt
    Frankfurt · EU
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  10. EU North - Stockholm
    Stockholm · EU
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  11. EU North - Helsinki
    Helsinki · EU
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  12. EU West - Paris
    Paris · EU
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  13. EU South - Madrid
    Madrid · EU
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  14. EU Central - Vienna
    Vienna · EU
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  15. EU Central - Warsaw
    Warsaw · EU
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  16. Asia - Singapore
    Singapore · AS
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  17. Asia - Hong Kong
    Hong Kong · AS
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  18. Asia - Tokyo
    Tokyo · AS
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  19. Asia - Seoul
    Seoul · AS
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  20. India - Mumbai
    Mumbai · AS
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  21. India - Chennai
    Chennai · AS
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  22. Middle East - Dubai
    Dubai · AS
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  23. South America - Sao Paulo
    Sao Paulo · SA
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  24. South America - Santiago
    Santiago · SA
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  25. South America - Lima
    Lima · SA
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  26. South America - Buenos Aires
    Buenos Aires · SA
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  27. Oceania - Sydney
    Sydney · OCE
    —
    Avg
    —
    Jitter
    —
    Failed
    —
  28. Africa - Johannesburg
    Johannesburg · AF
    —
    Avg
    —
    Jitter
    —
    Failed
    —

Test history

Saved in this browser. Clearing site data removes history.

No saved tests for this game yet.

How it works

We test round-trips (HTTPS) from your browser to AWS/Cloudflare or Game server endpoints if they're public or published by the developers. The first request is warmup, and then consecutive requests (upto 5) are used to make out an average. Browser tests usually add some latency, so in-game is usually lower.

Avg:
Avg trip time. This is what creates the ranking and how well your connection is doing.
Jitter:
How much the ping jumps across tests. Under 10 ms is smooth and acceptable.
Failed:
Requests to some servers might fail. We ignore these tests in results.
Grade:
Combined average of all tests across all mentioned servers.

Server Regions

US East - VirginiaSterling
US East - AtlantaAtlanta
US Central - DallasDallas
US Central - ChicagoChicago
US West - Los AngelesLos Angeles
US West - SeattleSeattle
EU West - AmsterdamAmsterdam
EU West - LondonLondon
EU Central - FrankfurtFrankfurt
EU North - StockholmStockholm
EU North - HelsinkiHelsinki
EU West - ParisParis
EU South - MadridMadrid
EU Central - ViennaVienna
EU Central - WarsawWarsaw
Asia - SingaporeSingapore
Asia - Hong KongHong Kong
Asia - TokyoTokyo
Asia - SeoulSeoul
India - MumbaiMumbai
India - ChennaiChennai
Middle East - DubaiDubai
South America - Sao PauloSao Paulo
South America - SantiagoSantiago
South America - LimaLima
South America - Buenos AiresBuenos Aires
Oceania - SydneySydney
Africa - JohannesburgJohannesburg

Network Profile

Performance Target<60ms
Refresh RateSource 2 server-based
TransmissionSteam Datagram Relay (SDR)

Testing Tips

For high-accuracy results, we recommend performing checks during peak hours.

Use wired Ethernet if possible
Close background streaming apps
Disable active VPN software

About Deadlock

Out for stiff competition with Dota 2 and LoL, Deadlock is the brand-new PvP game by Valve that combines the elements of MOBA and Third-Person Shooter games. Deadlock is the first of it's kind, as most MOBAs that are available right know present a top-down view. Similar to a MOBA, Deadlock has a ton of playable characters with a huge variety of abilities with a decent amount of learning curve. Deadlock also has given huge priority to a mechanic that is not really popular in MOBA games, Movement. So far, the game is shaping to be a great E-sports title.

Why Ping Matters in Deadlock

Isn't it obvious? Unlike traditional MOBA titles, Deadlock is a third person game at the end of the day. Which means aiming is very important. So if ping can matter so much in a game like Fornite, why shouldn't it matter in Deadlock? On top of that, a lot of weapons and abilities of different characters in Deadlock have travel time. So if your latency is high, there will be a significant delay between when you are pressing the button and when your character is shooting or using an ability. And if your shooting and ability usage is delayed, then good luck winning fights. Though, it is highly recommended that you aim around 40ms ping, but anything close to 60ms should be good enough.

Optimal Network Settings

Just make sure that you are not using any sort of VPN while playing Deadlock. Deadlock uses Valve's SDR or Steam Datagram Relay, so using a VPN will disrupt the routing. Also, you can always use out ping test tool to find out the best possible server, then use any routing app to select that server.

Troubleshooting Connection Issues

In case of issues like high ping, lag, and rubberbanding in Deadlock, we recommend: 1) You check the status of the servers of Deadlock first from the dedicated server status page by Lockbuilds , to see if they are up or down. 2) Make sure that your Nat Type is not Strict. It should be either Open or Moderate. 3) As we said earlier, make sure you don't have any VPN or any downloads running in the background. 4) Picking a wired Ethernet connection is recommended over WiFi. 5) Then there is always the option of trying Cloudfare DNS(1.1.1.1) or Google DNS(8.8.8.8).

Deadlock Network FAQ

What is a good ping for Deadlock?

If you are looking to play competitively, you should aim for under 60ms. Pro players typically play at under 30ms. Just make sure that your ping doesn't go above 120ms as it will negatively impact gameplay.

Does tick rate affect my experience?

Deadlock operates at Source 2 server-based. Higher tick rates lead to more responsive hit registration. Your actions and how quickly they are registered in-game are determined by your ping and tick rate combined.

Which server region should I choose?

Use our Ping Test tool to figure out your latency with all the regions, and pick the one with the lowest.

How can I reduce my ping?

Pick a wired Ethernet connection if you can, as WiFi tend to bring a lot of connection issues. Fiber connections are better than the traditional ones. Close applications that are hogging all your bandwidth. If you are going to use a WiFi router, just make sure you have QoS enabled on it. Trying Cloudflare or Google DNS can help in a lot of cases.