Is 400 ms latency good (2026)?

Latency, in the realm of internet performance, refers to the time it takes for data to travel from a source to a destination and back again. It’s measured in milliseconds (ms) and directly reflects the responsiveness of a network connection. As digital systems grow more sophisticated—streaming high-resolution videos, powering real-time communication, and supporting competitive online gaming—the margin for delay shrinks dramatically.

From video conferencing to cloud computing platforms, modern applications depend on near-instantaneous data transmission. Even a few hundred milliseconds can shape the user experience with noticeable lag, reduced responsiveness, or data desynchronization. Against this backdrop, a clear question arises: is 400ms latency good? Let’s break it down by use case and performance threshold.

Mapping the Mechanics: Understanding Latency in Technical Terms

Latency vs. Bandwidth: What’s the Difference?

Latency and bandwidth serve different functions in a network, yet they’re often mistaken for one another. Bandwidth refers to the capacity of a data channel — how much data can be transferred in a given time, typically measured in megabits per second (Mbps). Latency, on the other hand, measures the delay: the time it takes for a data packet to travel from the source to the destination.

Think of bandwidth as the width of a highway and latency as the travel time from one city to another. A six-lane road (high bandwidth) doesn’t shorten the distance or remove traffic lights (latency). So, even a gigabit-speed connection can feel slow if latency is high.

How Is Latency Measured?

Latency is measured in milliseconds (ms), representing the round-trip time — the duration it takes for a data packet to leave your device, reach its destination, and return. Tools like ping and traceroute are standard methods for calculating this delay. In digital communication, even small latency variations can have outsized impacts, especially in use cases requiring real-time interaction.

Common Benchmarks for Latency

0–50 ms: This range supports real-time applications like online gaming and VoIP with no noticeable delay.
50–100 ms: Suitable for video conferencing and most real-time communications, though sensitivity increases slightly.
100–200 ms: Real-time interaction suffers at this point; lag becomes perceptible in fast-paced applications.
200–400 ms: Delay is obvious, with impacts on gaming, live calls, and cloud-based tools.
400+ ms: Interactivity dramatically decreases. Conversations experience gaps, and input response in applications slows notably.

How Your Internet Service Provider Affects Latency

ISPs play a foundational role in latency outcomes. Their network infrastructure, peering arrangements, routing efficiency, and load balancing strategies directly influence how quickly data travels. A provider operating with outdated routing protocols or congested interconnection points will introduce unnecessary delay, regardless of advertised download speeds. Furthermore, the physical distance from the user to the ISP’s nearest exchange or data center affects performance — the farther the data must travel, the longer it takes.

Some ISPs also implement traffic shaping policies, prioritizing certain types of data over others. Streaming might load quickly, while gaming packets experience micro-delays. This design choice can elevate latency for interactive tasks even when overall throughput remains high.

How Different Applications React to Network Latency

Network latency does not impact all applications equally. Real-time services falter under high latency, while others remain functional even with noticeable delays. Here’s how various categories measure what’s considered acceptable.

Online Gaming

Fast-paced multiplayer games rely on low latency to synchronize real-time actions between players. When latency stays between 20ms and 50ms, aiming, shooting, or moving feels smooth. Once latency exceeds 100ms, delays become obvious—players see phantom hits, rubberbanding, or characters teleporting across screens. At 200ms and beyond, many games become practically unplayable due to time lag between user input and server response.

Video Conferencing

Face-to-face interactions over platforms like Zoom and Microsoft Teams benefit from round-trip latencies under 150ms. That threshold allows virtually seamless conversation flow. Between 150ms and 300ms, speakers start interrupting each other or pausing awkwardly. Audio and video may go out of sync. At 400ms, back-and-forth discussion becomes stilted, with noticeable delays between questions and replies.

Website Load Times

Latency contributes to Time to First Byte (TTFB) and overall page rendering speed. Modern websites aim for total response times under 200ms for TTFB. When latency reaches 400ms, users experience sluggish initial loading, especially when multiple resources (CSS, JavaScript, images) come from different domains. Even with broadband connections, pages stall briefly before rendering.

Streaming Services

Buffering tolerance varies, but latency over 200ms often triggers pre-load delays or playback interruptions in adaptive bitrate streaming. Services like Netflix, YouTube, or Twitch optimize streams based on latency and available bandwidth. Persistent delays exceeding 300ms degrade stream quality, cause resolution drops, and increase buffering events.

API Response Times

Latency can make or break user experience on websites and mobile apps relying on external APIs. For UI-sensitive endpoints, responses should stay under 100ms. At 200ms, users start noticing sluggishness. When latency climbs to 400ms, autocomplete fields may lag, dashboard loading spins longer, and transactional actions like “add to cart” or “submit form” appear broken.

Cloud Services

SaaS platforms, virtual desktops, and cloud-integrated applications depend heavily on WAN performance. For cloud-native workflows, latencies under 100ms allow smooth app interactions. Once you cross 250ms, navigation becomes choppy. At 400ms latency, working in cloud-based environments like Google Workspace, Microsoft 365, or virtual machines becomes noticeably delayed with every mouse click or file access triggering a half-second pause.

What Does 400ms Latency Really Mean?

The Real-World Impact of a 400ms Delay

A latency of 400 milliseconds means every action—whether clicking a button, loading a video, or firing a shot in an online game—will take nearly half a second to register a response from the server. This delay adds up quickly in applications that rely on real-time communication.

To grasp it more clearly, consider this: the blink of an eye takes about 100 to 150 milliseconds. A 400ms latency means users wait through nearly three blinks before the system processes a request. For interactive experiences, this lag creates a noticeable disconnect between action and result.

How Far Does Data Travel in 400ms?

At the speed of light in fiber optics—roughly 200,000 kilometers per second—data traveling to a distant server and back in 400ms may cover up to 40,000 kilometers round-trip. But raw distance isn’t the only factor. Routing inefficiencies, network congestion, and protocol overhead inflate time further.

For example, a user in New York accessing a server in Singapore might experience close to 300 to 350ms just from distance and hops, even before any processing delay on either side.

When the User Starts Noticing Lag

Users begin to consciously notice interface lag once latency rises above 100 to 150ms, especially during dynamic interactions like scrolling, typing, or gaming. At 400ms, the lag becomes disruptive for most real-time applications.

In VoIP conversations, this delay adds to conversation gaps, leading to unnatural pauses. In gaming, it introduces a sluggish feel, where input and feedback are visibly out of sync. Even in web browsing, a 400ms wait before a page starts loading can break the sense of speed users expect.

Benchmark Context: Is 400ms Fast or Slow?

Web browsing: Google’s research shows that adding just 200ms of delay in search results can reduce traffic and user engagement. At 400ms, bounce rates climb.
Online gaming: Competitive First-Person Shooter (FPS) games typically aim for latency below 50ms; anything above 100ms is suboptimal. 400ms causes visible lag—players see actions delayed, get hit before reacting.
Video calls: The ITU recommends < 150ms one-way latency for clear, fluid communication. A 400ms round-trip delay leads to audio overlap and awkward responses.

Compared to these benchmarks, 400ms doesn’t approach acceptable. It crosses the threshold where interactions start to feel unnatural and service quality declines.

Where 400ms Latency Breaks the Experience: Real-World Scenarios

Online Games

In fast-paced multiplayer environments—first-person shooters, battle arenas, real-time strategy—timing drives everything. A 400ms delay between action and response breaks immersion and ruins competitive play.

Slow reaction times: When pressing a key or moving a joystick, your character won’t respond instantly; in real-time combat, that half-second lag can mean the difference between a kill and a respawn screen.
Hit registration issues: Your gun fires when the crosshair aligns, but the server processes the event too late. The result: shots don’t register, and opponents escape damage they should’ve taken.
Gameplay interruptions: The game might compensate for delay with jitter correction, or rubberbanding—your character skips or teleports to sync with server data, breaking flow and accuracy.

Video Calls

Even slight audio or video misalignments disrupt natural conversation. At 400ms, latency distorts rhythm and makes emotional context harder to read.

Voice overlapping: You start speaking while the other person is still finishing their sentence on your end. This creates awkward interruptions and forced apologies. The flow feels robotic, not human.
Delays in emotional cues: Non-verbal feedback—a nod, a smile, a raised eyebrow—arrives late. In team meetings or client discussions, this delay dampens collaboration and signals disinterest even when none exists.

Website Experience

Online users demand instant access. Whether browsing ecommerce, reading articles, or interacting with forms, latency directly impacts satisfaction and revenue.

Slower page loads: A 400ms delay on each server request adds up quickly, especially on JavaScript-heavy websites. On dynamic pages, several small requests stack into multi-second waits.
Higher bounce rates: Google's research shows that when page load increases from one to five seconds, bounce probability increases by 90%. With 400ms latency, mobile and desktop users leave pages before full rendering completes.

Cloud Services & APIs

Modern software depends on cloud infrastructure not just for storage but for active computation. High latency slows automation, sync, and user experience across applications.

Delay in document sync: Editing a shared document in tools like Google Docs or Microsoft 365? A 400ms delay affects co-editing fluidity. Edits appear out of sequence or lag behind keystrokes.
App functionality degradation: APIs drive everything from weather forecasts to user authentication. With 400ms latency per request, multi-API workflows choke on round-trip delays, producing slow dashboards, incomplete forms, or stalled actions.

Speed vs. Latency — Which One Matters More?

Speed and latency are not the same — here's how they differ

Download and upload speeds refer to how much data your network can transfer per second, typically measured in megabits per second (Mbps). Latency, on the other hand, measures the delay between a user action and the response — recorded in milliseconds (ms). A gigabit connection with high latency can still feel sluggish, while a modest-speed connection with ultra-low latency can deliver a seamless experience.

High download or upload speeds improve tasks that require moving large volumes of data — think streaming a 4K movie, downloading a game, or syncing a cloud backup. But latency dictates how fast you get a response after initiating a request, making it the primary performance driver for interactive applications.

Use cases where latency dominates the user experience

Real-time gaming: Online multiplayer platforms demand latency under 100 ms to be playable. Competitive scenarios usually require under 30 ms. A shooter game with 400 ms latency means your actions appear almost half a second after they were performed — enough to lose an encounter every time.
Video conferencing: Delay above 250 ms introduces noticeable echo, awkward pauses, and people speaking over each other. With 400 ms latency, conversations become inefficient and unnatural.
Remote work interfaces: Virtual desktop infrastructure (VDI), SSH sessions, and cloud IDEs all suffer from input delay when latency rises above 150 ms. Typing, scrolling, or navigating becomes cumbersome at 400 ms.
VoIP and phone calls: Latency beyond 200 ms degrades call quality. According to ITU-T G.114 standards, one-way latency should stay below 150 ms for high-quality voice communication.

Who ultimately controls latency and speed — and can you do anything about it?

Both latency and speed depend heavily on the capabilities and structure of your internet service provider’s (ISP) infrastructure. Fiber-optic networks typically deliver lower latency and higher speeds than cable or DSL. But more than just physical mediums, upstream peering agreements — where your ISP connects to other regional and global networks — significantly affect routing efficiency. Poor peering leads to greater hop counts and longer round trip times.

Certain ISPs prioritize optimized low-latency routing through better-tier interconnects, while others focus mainly on bandwidth capacity. Evaluating an ISP based solely on advertised speed overlooks how responsive the network truly is. For latency-sensitive users, routing quality should headline the checklist.

What’s Slowing You Down? Key Factors That Affect Latency

Latency doesn’t emerge from a single source. Instead, multiple layers of a digital journey—hardware, software, physical distance, and infrastructure—shape the final delay observed in milliseconds. Digging into these components reveals why some connections feel instantaneous while others drag.

Distance to the Server

Data travels at the speed of light through fiber, which translates to approximately 200,000 kilometers per second in glass. Still, covering long distances creates measurable delay. A round trip from New York to Tokyo, for instance, adds around 140ms in latency on distance alone—even under optimal conditions. The farther the server, the longer the latency. No amount of bandwidth will offset the laws of physics here.

Server Response Times

Once a request hits a server, processing time becomes the next variable. A modern cloud environment using high-performance hardware can return responses in under 10ms. But server load, outdated components, or inefficient software can push this number significantly higher. A poorly optimized backend architecture increases the time between request and response, bloating the final latency measurement.

ISP Routing and Network Congestion

Internet Service Providers route data through a web of peering agreements, regional hubs, and traffic optimization paths. These decisions aren’t always ideal from a latency standpoint. Some ISPs prioritize cost-efficiency over speed, routing data through long or congested paths. During peak traffic hours, localized congestion can spike latency by 100ms or more, even if users are geographically close to a server.

Network Type

Mobile Data: Cellular networks introduce several layers of processing, hand-off coordination, and radio signal travel. Latency commonly sits between 50ms and 120ms on 4G LTE, rising into the 150ms–400ms range on 3G. 5G has improved metrics—often hovering below 30ms—but coverage remains inconsistent.
Wired/Broadband: Ethernet and cable/fiber broadband connections offer lower latency due to physical stability and direct routing. Typical latency through fiber sits well below 20ms in optimized pathways. Variations still occur based on provider infrastructure and local congestion.
Satellite Internet: Even with upgraded low-Earth orbit (LEO) constellations, satellite data must travel thousands of kilometers to space and back. Traditional geostationary systems produce latencies between 600ms to 800ms. LEO networks like Starlink have reduced this to around 40ms–60ms under ideal conditions, but consistency is still a challenge.

No matter how fast the download speed claims to be, these latency influencers can create a sluggish experience. Look beyond Mbps, and examine every layer contributing to the millisecond count.

How to Test and Monitor Your Latency

Reliable latency measurements depend on using the right tools and running repeatable tests. Without consistent tracking, those spikes in delay can be dismissed as anomalies—even when they’re recurring problems affecting your user experience or application performance.

Precision Starts With the Right Tools

SpeedTest.net: Use SpeedTest.net to quickly check your ping, download, and upload speeds. While primarily designed for measuring bandwidth, it displays latency (ping) in milliseconds as part of each test result. Results vary based on server location, so test against multiple targets for a fuller picture.
Ping utilities and traceroute: Open a command prompt or terminal and type ping [destination]. For example, ping google.com sends packets and returns round-trip times. Consistently high responses above 200 ms on a local or regional server point to an issue worth diagnosing. With traceroute or tracert, track each hop between source and destination to identify which segment introduces delay.
In-game latency tools: Online games often include built-in performance HUDs. Look for ping or latency meters alongside frame rate (FPS). For instance, in Valorant or Call of Duty, the network stats show real-time latency and packet loss. Spike patterns during gameplay suggest local interference or mid-route congestion.

Collecting Data That Tells the Full Story

One test won’t cut it. Latency fluctuates based on time of day, network load, and even background applications. To develop a clear baseline, collect at least 10 to 15 readings under similar conditions. Spread the tests across different times—early morning, midday, evening—and don’t rely on a single server or destination.

While performing these tests, take notes. Record timestamps, test location, service provider, and concurrent network activity. If latency consistently rises during peak evening hours, congestion is the likely culprit. When gaming performance drops without visible spikes in ping, packet loss or jitter could be more relevant metrics to track.

You don’t need enterprise-level tools to uncover where delays emerge. But without a disciplined, repeated approach, diagnosing the root cause of a 400 ms latency spike becomes guesswork—not analysis.

Fixing High Latency: Potential Solutions

Optimize Your Internet Service Plan

ISPs often market packages based on download speeds, but latency performance varies significantly between providers. Upgrading to a higher quality plan can reduce congestion during peak hours and minimize interconnection delays. For users stuck around 400ms latency, shifting to a fiber-based service or a plan with prioritized routing can cut latency by half or more.

Switch to an ISP with Stronger Regional Peering

Routing paths make a critical difference. Some ISPs maintain better peering agreements, meaning your data takes fewer hops and passes through more efficient routes. Switch to a provider that peers closer to your destination servers—especially if you're gaming, using VoIP, or accessing cloud apps hosted in specific geographic regions.

Reduce Local Network Load

Heavy local usage causes packet queuing and jitter. Streaming 4K content, cloud backups, and dozens of connected IoT devices add up. Try these adjustments:

Schedule high-bandwidth activities (like file syncs or updates) during idle times.
Limit simultaneous users during latency-sensitive tasks.
Enable QoS settings on your router to prioritize latency-critical traffic like gaming or video calls.

Use a Wired Connection

Wi-Fi introduces impedance, retransmissions, and signal degradation—resulting in extra milliseconds of delay with every packet. Ethernet connections avoid interference and provide more stable latency. Connecting your primary device directly to the router can shave 10–40 ms instantly, and eliminate spikes altogether.

Upgrade Your Modem and Router

Older networking hardware lacks support for modern protocols and buffers traffic inefficiently. Devices from more than five years ago often suffer from firmware gaps and outdated chipsets. Invest in hardware that supports:

Wi-Fi 6 or 6E for lower overhead and better multi-device handling
DOCSIS 3.1 or fiber-compatible modems to support higher throughput and reduce network-level latency
Multi-core processors and automatic QoS for smart traffic management

Rely on CDN-Backed Content Delivery

High latency often stems from physical distance. If you’re serving or accessing content from far-flung servers, introduce a CDN (Content Delivery Network) layer. CDNs place cached assets close to users via edge servers, which cuts latency by bringing content geographically closer. Services like Cloudflare, Akamai, and Fastly offer latency reductions of over 60% in global delivery scenarios.

Improve Backend Hosting Infrastructure

If you're managing web services yourself, evaluate your hosting stack. Overloaded servers, outdated protocols, or inefficient routing logic extend round-trip times. To improve network responsiveness:

Move to hosting providers with low-latency global data centers
Use HTTP/2 or HTTP/3 protocols for reduced connection setup overhead
Optimize backend code to lower processing time before response dispatch

Each of these fixes targets a different layer of the latency puzzle—from user-end devices to global routing paths. Applied together, they transform a laggy 400ms connection into something far closer to real-time interaction.

Latency by Use-Case: What’s Acceptable and What Breaks the Experience

A 400ms latency figure doesn’t mean the same thing in every context. Browsing a static website? You might barely notice. Try real-time multiplayer gaming or VoIP at that speed, though, and the experience collapses. Use-case defines the line between functional and frustrating.

Latency Reference Chart: How Different Ranges Perform

This table categorizes latency into functional ranges based on real-world user expectations across different online activities. Values reflect round-trip time (RTT) in milliseconds.

20–50ms: This range delivers near-instant communication. Ideal for online gaming in competitive formats, real-time collaboration tools, and responsive remote desktop sessions. Users experience no perceptible delay.
50–100ms: Smooth enough for HD video streaming, casual online gaming, and most voice communication platforms. Light latency becomes noticeable only during fast-paced interaction or critical timing scenarios.
100–200ms: Delays start surfacing, especially in interactive applications. First-person shooters feel less responsive, and voice communication can have slight overlap or echo, requiring users to adjust conversational pacing.
200–400ms: This is where applications begin to struggle. Video calls develop noticeable lag, cloud gaming loses sync, and actions in multiplayer games feel delayed. The overall user experience frequently becomes disruptive.
Over 400ms: Communication loses fluidity. Real-time control systems fail; gameplay deteriorates into choppiness; live collaboration apps, such as whiteboarding tools or shared design platforms, become unreliable due to delayed feedback loops.

Consider the applications you use most. Would a 400ms latency disrupt your workflow or derail your online session? If the answer is yes, optimizing latency isn’t optional—it’s non-negotiable.

Final Verdict: Is 400ms Latency Good?

400 milliseconds of latency introduces a noticeable delay. In the context of modern digital interactions, responsiveness defines user experience, and at this level, the lag becomes disruptive in many real-time environments.

Incompatibility with Real-Time Applications

For real-time use cases—such as online gaming, voice-over-IP (VoIP) calls, video conferencing, and live broadcasting—400ms latency creates degraded performance. Here's what happens in practice:

In competitive multiplayer games, actions arrive a fraction of a second late, breaking real-time feedback crucial for playability.
During VoIP calls, 400ms round-trips result in conversational desynchronization, often causing speakers to interrupt or talk over each other—negating the natural flow of dialogue.
In live broadcasting scenarios, it delays streaming control inputs and video/audio sync, impacting both creators and viewers.

These environments typically require end-to-end latency below 100ms to maintain fluid interaction. 400ms quadruples that baseline, pushing the system far outside optimal bounds.

Narrow Use-Cases Where It’s Tolerable

Certain functions, especially those involving non-immediate interaction, can withstand this delay. For example:

Email or asynchronous messaging platforms tolerate it without functional loss.
File uploads and downloads remain feasible—though less efficient—particularly if throughput, rather than responsiveness, dominates the workflow.
In cloud-based data backup or scheduled batch jobs, latency plays a minor role relative to availability and consistency.

These are the exceptions, not the norm—most interactive applications demand faster response times.

How to Know if 400ms Is Affecting You

Understand your daily workload. Ask questions like:

Do I rely on real-time communication with clients or teams?
Is video conferencing part of my day-to-day operations?
Do slow-loading webpages or file sync delays impact my productivity?

Use latency diagnosis tools to pinpoint exact delays. Compare the results to benchmarks based on your most-used applications.

When responsiveness matters—and in most interactive use-cases, it does—400ms latency will fall short. Reserve it for scenarios where speed is secondary.