Arc Raiders updates arrive on a roughly weekly-to-biweekly cadence, with a hotfix appearing within 24 to 72 hours of any major patch that introduces a crash or balance exploit. The reliable window is Tuesday through Thursday, 5:00 to 9:00 AM UTC (typically 1:00 to 5:00 AM Eastern), because Embark Studios ships during Swedish business hours and rolls servers after the build is live. There is no fixed public calendar: the studio announces each patch a day or two before it deploys on the official Discord and its social channels. Anything calling itself a schedule is inference, not confirmation.

This explainer covers how the update pipeline actually works, what the deployment windows mean for your session planning, which assumptions mislead players, and how to verify a patch is real before you waste an evening reinstalling shaders.

How the update pipeline actually works

Embark Studios runs a build-test-deploy chain rather than a fixed release calendar. A build is compiled, passed to internal QA, then to a small external test group, then staged to the live servers. The staging step is where most timing variance lives: a build that passes QA can still be held if staging reveals a server-side fault that would affect extraction matchmaking.

Deployment is a two-part operation. The client patch is pushed to Steam and the Epic Games Store first. Server binaries are then rolled per region. This split is why you can sometimes download an update before the backend is ready, and why the "servers down" window is often longer than the download itself. Matchmaking is disabled during the backend swap, and the in-game build number is the fastest way to confirm you are on the current version.

The hotfix layer sits on top of this. When a major patch ships a progression exploit or a crash on a common hardware configuration, Embark has shipped corrective hotfixes within 48 hours of the main patch. Hotfixes are usually small downloads because they replace specific asset and configuration files rather than the full content bundle. That is also why hotfix windows are shorter and less disruptive.

One professional caveat most coverage misses: the announcement date is not the build date. A patch announced for "this week" may already be sitting in staging for days. The announcement is a communication decision, not a technical milestone, so treating announcement cadence as a schedule predictor will mislead you.

Quantified context: patch size, downtime, and cadence

Patch sizes scale with content. A balance-only hotfix typically lands in the low hundreds of megabytes because it swaps tuning values and small assets. A content update that adds a map, weapons, or a new event pushes several gigabytes because it bundles new art and audio. Content-heavy seasonal drops can exceed that, and they are also the patches most likely to require a shader recompile on first launch, which adds minutes to your first session afterward.

Downtime follows the same split. Hotfixes often avoid a full matchmaking shutdown, or shut it down for a very short window. Major content patches take matchmaking offline long enough to matter for a scheduled raid group. Server rollback capability exists, but Embark has historically preferred forward hotfixes over rolling back player progress, because rollback would punish players who already earned rewards.

The single biggest quantified trap is the timezone conversion. A 6:00 AM UTC deploy is roughly 1:00 AM Eastern, 10:00 PM Pacific the previous day, and mid-afternoon in East Asia. If you plan a session off a UTC time without converting, you will either wait hours or miss the window entirely. Write the UTC time down and convert once, deliberately.

Patch type Typical size Matchmaking impact Announcement lead time First-session friction
Balance hotfix Low hundreds of MB Often none or brief Hours to one day Minimal
Crash/exploit hotfix Low hundreds of MB Brief Often same day Minimal
Content update Several GB Window of downtime One to three days Shader recompile
Seasonal/event drop Largest tier Longer downtime Days to a week Recompile plus queue
Store/backend-only change Small Possible brief outage Variable None

Treat the size figures as tiers, not exact numbers. Embark does not publish per-patch byte counts in advance, and inventing a precise figure for a specific patch would be guessing.

Timeline behavior around a patch day

Understanding the shape of a patch day matters more than memorizing a date. The sequence below is the general pattern; exact offsets vary by patch and are not published.

Phase Relative timing What happens What you should do
Announcement T-1 to T-3 days Build announced on official channels Note the date, not the hour
Pre-deploy staging T-24 to T-6 hours Build final testing, backend prep Do not schedule a raid group yet
Client push Deploy hour Update downloads on Steam/Epic Download early if the store allows
Backend roll Deploy hour plus minutes Servers swap per region Expect matchmaking off
Live verification Deploy hour plus minutes Build number increments Confirm build before queuing
Hotfix window T+24 to T+72 hours Corrections if needed Check channels before long sessions
Stabilization T+3 days onward Cadence returns to normal Safe to plan normally

The counterintuitive detail: the longest wait is often not the deploy itself but the discovery that you queued on the old build. The client can take several minutes after the store push before it prompts you to update, and if you launched from a running session, you may not see the prompt at all. Restarting the client deliberately resolves this faster than refreshing the server browser.

Misconceptions that cost you sessions

The most common wrong assumption is that Arc Raiders runs a fixed patch day like some live-service titles. It does not; Embark has shipped on multiple weekdays, and the studio's communication is event-driven rather than calendar-driven. Planning around a supposed fixed day produces false confidence.

The second is confusing "servers down" with "update available." During a backend roll, the client patch may already be live while matchmaking is disabled. Players who see the download and assume they can immediately play are usually disappointed for a short window. Conversely, players who see matchmaking blocked sometimes assume no patch exists, when in fact the patch shipped and the backend is still settling.

The third is treating community aggregator sites as schedules. Aggregators surface announced dates, but they frequently mark speculative dates as confirmed, and they are slow to correct. The official Discord and the studio's own channels are the only places a date is actually confirmed. If a site gives you an hour with no source, it is inference.

A subtler misconception: patch notes describe intent, not verified outcome. A fix listed in the notes can be reverted by a follow-up hotfix if it breaks something worse. Treat the notes as a changelog of effort, and treat your own in-game testing as the ground truth for whether a specific issue is resolved.

Practical actions: verify before you plan

Check the in-game build number against the patch notes before you assume you are current. A mismatch means your client has not updated. Restart the launcher and client deliberately after an announced deploy, rather than waiting for a prompt that may not appear in a running session. Convert the deploy time from UTC to your local time once, and write it down. Do not re-derive it under time pressure. Join the official community channel and enable notifications for the announcements feed, not general chat, which buries patch notices. Before a long planned session, check whether a hotfix window is open by looking for a same-week follow-up notice. Download the patch early if your storefront permits preloading, but do not assume preload equals a ready backend.

Red-flag warnings for patch-day planning:

A date with a precise hour that no official channel has published. Treat it as fabricated or inferred. A claim that downtime is "a few minutes" for a content-tier patch. Backend rolls are rarely that quick. Any schedule presented as permanent. Cadence is current behavior, not a contract. A patch notice that lists no build number. Without one, you cannot verify the push landed for your platform.

Edge cases and platform variance

Platform timing is not perfectly synchronized. PC storefronts and console storefronts each have their own certification and propagation characteristics, so a patch that is live on one platform can lag briefly on another. When Embark says "available now," that describes the studio's deploy, not a guarantee that every storefront has propagated the build. If you play across platforms, verify each one separately rather than assuming parity.

A second edge case is the mid-session deploy. If a patch lands while you are in a match, the session typically continues on the old build, and you are prompted or forced to update when you return to the lobby. This is why some players report playing "on the old patch" minutes after a deploy. It is not a bug; it is session continuity.

A third edge case is regional rollout order. Backend rolls happen per region, and your region may move before or after others. Players comparing notes across time zones will see different windows for the same patch, which fuels false claims that a patch was delayed or canceled. The build is the same; the timing is regional.

Limitations: what no one can tell you

No public source provides a forward calendar far enough ahead to plan around, because Embark has not published one. Cadence is observed behavior, and observed behavior can change without notice. Any specific future date you see, including one in this article, would be a guess, so none is given here.

Patch note contents are also incomplete as a record. They describe headline changes, not every tuning value, and they do not always enumerate backend adjustments. For players tracking a specific mechanic, the only reliable method is in-game measurement after each patch, documented yourself over time. That is laborious, but it is the only method that does not depend on someone else's summary.

Finally, verify claims about any single patch's size, downtime, or contents against the official notes for that patch. The tiers in the tables above describe typical behavior, not measured figures for a named update. The moment you see a precise byte count or minute figure attributed to a specific patch without a source, discount it.

This article is general educational information about how live-service patch deployment typically works, not a schedule, a service commitment, or advice about any specific product decision. Embark Studios controls all timing and may change it at any time. Check the official channels for the current status of any update.