Webflow Site Down? Tell If It's Webflow or Your Domain

If you discover your webflow site down, the fastest way to diagnose the cause is to visit your default *.webflow.io staging domain. If your staging URL loads without issue, Webflow's core hosting infrastructure is working, and the outage is caused by your custom domain registration, your DNS records, or an SSL certificate issue.

When you run an online business, seeing a blank screen, a browser security warning, or a generic "Site Not Found" error on your production URL is alarming. Worse, founders often discover outages only after a customer sends an email asking if the company shut down. Before adjusting configuration settings or toggling options in your domain registrar, follow a systematic diagnostic plan. In almost every case, an unreachable site traces back to one of three distinct areas: domain registration and DNS routing, an SSL certificate lapse, or a platform-wide hosting incident.

The 3 Issues That All Look Like "Down"

To an everyday visitor, every failure looks identical: your website does not open. However, your Webflow site relies on a sequence of distinct systems communicating across the public internet. If any link in that chain fails, the browser displays an error. Understanding where the breakdown occurred tells you whether you can resolve it in your dashboard or whether you must wait for an upstream provider to recover.

Here is what happens behind the scenes across the three primary outage types:

• The Domain Failure (Registrar or DNS): This occurs when a visitor's browser queries internet nameservers to locate your server's IP address, but receives an error or no response. Common causes include an expired domain registration, an overdue billing notification from your domain registrar (such as Namecheap, GoDaddy, or Squarespace), or DNS records that were accidentally altered or removed.
• The Certificate Failure (SSL/TLS): Modern browsers block access to websites that lack a valid, matching security certificate. If Webflow cannot renew your Let's Encrypt certificate, or if DNS records change so automated domain validation fails, visitors encounter a prominent security warning such as NET::ERR_CERT_COMMON_NAME_INVALID or "Your connection is not private." The underlying Webflow hosting infrastructure may be active, but visitors cannot access the page.
• The Platform Incident (Webflow Hosting or Edge Network): In this scenario, your domain and DNS records point to the correct addresses, but Webflow's hosting cluster, upstream content delivery network, or routing proxies encounter an operational disruption and return 500, 502, or 503 HTTP status codes. Refer to the Webflow Help Center guide on connecting a custom domain for details on how custom domains route to Webflow edge servers. Source: University Webflow source. Source: University Webflow source. Source: University Webflow source. Source: Nightlamp source.

The 10-Minute Diagnostic Playbook

When your production site goes offline, guessing wastes valuable time. Work through these five steps in order to pinpoint the exact failure point.

Step 1: Test Your Staging Subdomain

Every Webflow project includes a default staging subdomain that ends with .webflow.io (such as your-project.webflow.io). This staging URL bypasses your custom registrar, third-party DNS provider, and custom domain SSL handshake, connecting straight to Webflow's core infrastructure.

Open a new private or incognito browsing window and load your *.webflow.io address directly:

• If the staging site loads normally: Webflow's underlying hosting tier is healthy. Your project design, CMS collections, published assets, and static files are intact. The problem lies with your custom domain settings, external DNS records, or domain-level SSL certificate. Do not unpublish your site or alter your Webflow design structure.
• If the staging site fails to load (returning a 500, 502, or 503 error, or hanging on connection): Webflow itself may be experiencing a hosting disruption, or your Webflow account may have an administrative or billing issue.

Step 2: Check Your Domain Registrar Status

If your staging site loads without errors, inspect your domain registration. It is common for teams to miss renewal reminder emails when a credit card on file expires with registrars such as GoDaddy, Namecheap, Cloudflare Registrar, or Squarespace.

Query your domain using the ICANN Registration Data Lookup Tool and review two key attributes:

1. Domain Status: Look for status flags such as clientHold or redemptionPeriod. A clientHold status indicates that the registrar suspended resolution of the domain, frequently due to an unpaid renewal balance or an unconfirmed contact email address under annual ICANN verification rules.
2. Expiration Date: Verify that the domain registration remains active. If a domain registration lapses, renewing the registration through your registrar account re-enables DNS resolution once global registry records update.

Step 3: Verify Your DNS Records Against Webflow's Standards

If your domain registration is active and healthy, check your active DNS zone configuration. Open the control panel of your authoritative DNS provider (often Cloudflare, GoDaddy, Namecheap, or Route 53) and check that your records match Webflow's requirements.

Standard custom domain configurations rely on precise A and CNAME record mappings:

• Root Domain (@): Webflow requires specific A records pointing your apex domain to their routing infrastructure, such as 75.2.70.75 and 99.83.190.102. Ensure no conflicting A or AAAA records remain from legacy hosts or previous website builders.
• Subdomain (typically www): Webflow directs subdomain traffic through a CNAME record pointing your host (such as www) to proxy-ssl.webflow.com or cdn.webflow.com as specified in your workspace dashboard.

A common cause of sudden domain drops occurs when a team member or integrated third-party service (such as Google Workspace, an email marketing tool, or an authentication provider) alters DNS settings and inadvertently deletes or overrides existing root A records. When changing DNS records, you may experience a partial cutover failure; review our guide on debugging broken DNS cutovers to learn why traffic drops intermittently after record changes.

If you use Cloudflare for DNS management, ensure that both the A records and CNAME records pointing to Webflow are set to DNS Only (Grey Cloud) rather than Proxied (Orange Cloud), unless your project uses an enterprise setup configured specifically for proxying. Double-proxying without required certificate parameters can trigger an immediate SSL handshake error (such as Cloudflare Error 525 or 526).

Step 4: Check Webflow's Status Page and Edge Networks

If your staging site fails or your DNS configuration is verified yet returning server errors, check whether Webflow's shared infrastructure is encountering a widespread outage.

Review the official Webflow Status Dashboard alongside our independent incident dashboard at Nightlamp Webflow Status. Webflow separates status tracking into distinct subsystems:

• Webflow Designer & Dashboard: The editor interface used to design and update pages. If the dashboard is degraded, you may be unable to publish updates, but live websites typically remain accessible.
• Page Hosting & CDN: The global edge delivery network responsible for serving live pages. When this subsystem experiences degraded performance, live websites may experience elevated latency, connection timeouts, or gateway errors.
• Form Processing & Asset Delivery: Auxiliary services handling form submissions or media delivery. In some incidents, website pages load normally while user form submissions or image assets fail to process.

Step 5: Identify If It Is Down for Everyone or Just You

Before making emergency changes to your account, confirm whether the downtime is globally reproducible or limited to your local network connection. Local operating system resolvers, home router caches, and browser storage can retain outdated DNS responses long after records are restored.

Use a public propagation checker like whatsmydns.net to query your domain across worldwide resolving servers. If international locations return the correct Webflow IP addresses while your local computer returns an error, the cause is local DNS caching. You can also test access from a mobile phone using a cellular carrier data connection with your local Wi-Fi turned off.

Understanding Browser Error Codes

The specific error code shown in Google Chrome, Apple Safari, or Mozilla Firefox highlights which network layer encountered the failure:

DNS_PROBE_FINISHED_NXDOMAIN

This browser message means the requested domain name cannot be resolved to any server IP address. The request rarely reaches Webflow. Check your domain registrar for renewal status, confirm your nameserver entries are intact, and check your active DNS zone for missing root A records.

SSL Handshake Failed or NET::ERR_CERT_DATE_INVALID

This message occurs when the browser reaches an IP address, but the server does not present a valid, matching SSL/TLS security certificate. Inside your Webflow project settings under Publishing > Custom Domains, check the SSL verification indicator. If the status displays an error or remains pending indefinitely, automated certificate issuance may be obstructed. This frequently happens if your domain DNS includes CAA records that restrict certificate issuance from Let's Encrypt. For detailed recovery steps on security certificate failures, refer to our guide on resolving expired SSL certificates.

502 Bad Gateway or 504 Gateway Timeout

A 502 or 504 status code indicates that the edge routing server received a connection request from the browser but encountered an invalid response or timeout from Webflow's internal hosting nodes. When staging subdomains and live domains both display 502 or 504 errors simultaneously, Webflow's platform infrastructure is usually managing an active service disruption.

404 Not Found (Webflow Styled)

If your browser displays a 404 page featuring Webflow styling or your project's custom 404 layout, network routing and domain connections are working properly, but the Webflow hosting proxy does not recognize the exact hostname or URL path requested. This often happens if you added a new custom domain in your project dashboard but have not yet executed a publish operation to all selected domains.

What to Tell Customers While Your Site Is Down

When a customer-facing site becomes inaccessible, silence creates uncertainty for users and prospective buyers. Transparent communication reassures users that their account data remains safe and that resolution is underway.

Here are two communication templates based on the root cause:

Scenario A: Platform-Wide Outage (Webflow Down)

"We are experiencing a temporary service disruption affecting our website availability. Our hosting infrastructure provider (Webflow) is managing an edge network issue. User accounts and stored data remain secure. We are following provider updates closely and will provide our next progress update shortly."

Scenario B: DNS or SSL Routing Failure

"Our primary domain is undergoing network route propagation following a domain infrastructure update. All core systems remain fully operational. We are updating our DNS routing configurations to restore public web access as quickly as possible."

Recovery Expectations by Outage Type

How to Stop Finding Out About Outages From Customers

Many non-technical founders manage web availability reactively: they publish a site or web application, trust that hosting remains stable, and discover outages only after an annoyed customer sends an email or an important prospect abandons a signup flow. Running a dependable product requires continuous visibility into all delivery layers.

Basic endpoint checks only test whether a URL returns an HTTP 200 response from a single testing location. They regularly miss regional CDN routing issues, incomplete DNS updates across global networks, and looming SSL certificate expiration dates. Reliable monitoring must evaluate several critical components:

1. Your custom production domain across diverse geographical regions.
2. Your *.webflow.io staging address, ensuring you can immediately tell platform hosting issues apart from domain routing errors.
3. SSL/TLS certificate expiration windows, alerting you well before automated renewals lapse.
4. DNS record stability, alerting you if required A or CNAME entries are modified or removed.

For founders managing products without an internal systems administrator, review our guide on website monitoring for non-technical founders to understand how proactive verification protects your revenue and user experience.

Managed App Care: What Nightlamp Does Differently

When you build with platforms like Webflow, Bubble, Lovable, Bolt, or Replit, traditional monitoring tools often produce noise instead of clarity. Automated alert bots send middle-of-the-night notifications containing ambiguous error codes, leaving you to puzzle out whether a CDN dropped connections, an SSL renewal failed, or your registrar expired.

Nightlamp takes a fundamentally different approach with App Care. Human engineers diagnose incidents for you; Nightlamp does not just fire alerts. When your application stops responding, our team investigates the full connection path—including HTTP availability, SSL certificate health, DNS integrity, and mail delivery paths—and provides clear, plain-English guidance on what went wrong and how to fix it.

Nightlamp does not auto-remediate infrastructure on its own; a real engineer diagnoses each incident and tells you exactly what to fix. Whether the solution involves correcting an apex A record at your registrar, re-verifying a custom domain in your Webflow project settings, or waiting out an upstream edge network issue, you receive actionable diagnostic instructions rather than raw error codes.

Frequently Asked Questions

Can I fix a Webflow site outage by restoring a site backup?

Restoring a backup inside Webflow only reverts the visual design layout, page elements, and CMS database entries to a previous snapshot. It does not resolve outages caused by domain registration lapses, misconfigured DNS records, or platform-wide hosting downtime. If your staging subdomain loads normally, rolling back to an earlier backup will not fix a custom domain routing problem and could overwrite recent design work you wanted to keep.

Why does my Webflow site load on my mobile phone but fail on my computer?

This discrepancy is typically caused by local DNS caching or split network paths. Your mobile phone connected to a cellular provider queries that carrier's DNS servers, while your laptop queries your local Wi-Fi router or internet service provider cache. When DNS records change, cellular networks may pick up the updated records while a local internet provider continues serving cached data. Clearing your local computer DNS cache or testing through an alternative network often resolves the difference.

Do I need to publish changes to both the staging domain and my custom domain?

Yes. Webflow requires you to select which target domains receive published updates. If you check the box for your *.webflow.io staging domain but leave your custom domain unchecked, changes will not deploy to production. often confirm that your custom domain (selected as default) and your staging domain are both marked when publishing your project.

What should I do if Webflow's status page reports all systems operational, but my staging site is down?

If your staging site fails while Webflow's status dashboard shows operational systems across all services, the cause is usually account-specific. Sign in to your Webflow dashboard and check for billing issues, bandwidth caps, or unverified email notifications. If your workspace account is in good standing, submit an urgent support request directly to Webflow Support with your browser console logs and project details.

Stop waiting for customers to report that your site is unreachable. To have real engineers monitor your stack and deliver plain-English incident diagnostics, visit Nightlamp pricing to start a trial or see plans today.