isitdownrightnow.app
  1. Home
  2. Services
  3. StackPath
StackPath stackpath.com

Is StackPath down right now? Live status and outage tracker

No, StackPath is up.

No outage detected, and no user reports in the last hour.

Live Data refreshes every 5 minutes
Not working for you?
User reports, last 24 hours, 15 minutes a segment: 96 flowing, 0 slow (elevated), 0 jammed (outage)

User reports, last 24 hours

No reports in this window

No problem reports came in for StackPath in the last hour, and at this time of day there are usually almost none. There has been no spike in reports since 29 October. These are user reports from the US, where most people report StackPath problems.

No user reports came in for StackPath in the past 24 hours, and its uptime over that window is 100.00%. No 15-minute window had any reports at all, so the chart above stays flat.
Reports, last hour
0
Quiet
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
0
No reports
Last 24 hours

StackPath outages and problems

No user reports came in for StackPath in the past 24 hours, and its uptime over that window is 100.00%.

No 15-minute window had any reports at all, so the chart above stays flat.

No problems detected in the last 24 hoursReports for StackPath stayed at their usual level the whole time.
Report categories

What people can report about StackPath

People who report a problem with StackPath to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:

  • Hosting
  • Login
  • Domains
  • DNS
  • API
  • Dashboard / Console
  • Storage and Backup
  • Databases
World map

Where StackPath problem reports come from

The map shows where recent problem reports for StackPath came from in the US. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.

Map outlines: Natural Earth.

Last 30 days

StackPath problem spikes, last 30 days

Since 29 October, StackPath had no outage spikes or periods of elevated reports.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 29 October 2026. Monthly reports for all services

Troubleshooting

How to fix StackPath not working

StackPath is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach stackpath.com over your own connection, right now. Nothing is sent to us or stored.

  1. Check StackPath reports first

    Check the report level first. The status at the top shows whether problem reports from other people are above their usual level, counted in 15-minute windows over the last 24 hours, so a normal level points to a local fault on your side.

  2. Rule out DNS for StackPath

    Run nslookup for the hostname you use. Compare your default resolver with 1.1.1.1, because an ISP DNS fault can look like a StackPath outage. Flush your cache with ipconfig /flushdns on Windows or sudo killall -HUP mDNSResponder on macOS, then load the page again.

  3. Bypass VPN and browser blocks

    Disconnect your VPN or proxy, then open the site in a private window with extensions disabled, because a proxy rule can block only your machine. If the error clears, turn off the extension or split tunnel rule that touches the StackPath hostname.

  4. Test the StackPath edge from another network

    Use your phone on cellular data to load the same URL. If it works there, the problem is your local network or machine. On a desktop, run curl -I against the URL and compare the response headers with a request sent to your origin to see if the edge is returning an error.

While StackPath is down: what to use instead

  • Cloudflare Cloudflare works when your edge is unreachable.
  • Fastly Fastly helps if you want static assets served from a separate CDN while the main delivery path is broken.
  • Amazon CloudFront Point CloudFront at your origin bucket or server if you already run workloads on AWS and need a quick bypass.
  • Akamai Akamai fits larger sites that keep a second delivery network ready, so a failover does not turn into a scramble when the primary edge stops answering.
Your device

Fix StackPath on Windows, Mac, Android and iPhone

StackPath on Windows

Fix
Clear your Windows DNS cache and check your local hosts file to ensure StackPath CDN IPs aren't misrouted. You can also temporarily disable any third-party firewalls or VPNs that might block StackPath's edge servers.
Check
Check the official StackPath status page in your browser or use network diagnostics to test if your PC can resolve StackPath-hosted domains. If other sites load but StackPath-dependent assets fail, the service or its edge node might be down.
Command Prompt
ping stackpath.comTest whether StackPath's servers reply
nslookup stackpath.comCheck that StackPath's DNS resolves
tracert stackpath.comTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

StackPath on Mac

Fix
Flush the DNS cache in macOS and verify that your local network configuration is not blocking StackPath's IP ranges. Restarting your web browser or testing from a different network connection can also help resolve routing issues.
Check
Use network lookup tools to query StackPath's DNS servers and verify connectivity to its edge servers. You can also check the StackPath status portal to see if there are active incidents affecting CDN endpoints.
Terminal
ping -c 4 stackpath.comTest whether StackPath's servers reply
nslookup stackpath.comCheck that StackPath's DNS resolves
traceroute stackpath.comTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

StackPath on Android

Fix
Clear the cache of the web browser encountering StackPath connection issues, or toggle your Wi-Fi off and on. If you use a private DNS provider on your Android device, try reverting to default settings to ensure StackPath domains resolve correctly.
Check
Attempt to load the StackPath dashboard or a StackPath-hosted resource using a mobile browser to see if the connection times out. Check StackPath's system status page to confirm if the outage is widespread.

StackPath on iPhone and iPad

Fix
Toggle Airplane Mode or reset your network settings on your iOS device to force a fresh connection to StackPath's CDN edge nodes. If you are using iCloud Private Relay or a VPN, disable them temporarily as they can interfere with StackPath routing.
Check
Try accessing the StackPath status dashboard or a known StackPath-hosted asset in Safari to check for loading errors. If the page fails to load across both Wi-Fi and cellular networks, StackPath is likely experiencing downtime.
About

What happens when StackPath goes down

StackPath is an edge platform that runs CDN delivery, DDoS filtering, WAF rules, and edge compute for websites and applications. Developers and security teams route traffic through it; when it breaks, page loads and API calls fail.

CDN delivery breaks first. Pages load slowly, images stall, scripts time out, and visitors see gateway errors instead of content when the edge stops serving assets. API calls and TLS handshakes then fail, so apps that depend on the edge for auth and routing stop responding. WAF and DDoS filtering can also reject legitimate traffic or fail open, which makes some regions or customer networks see problems while others stay fine.

Servers and network

StackPath IP address, servers and network

Checking stackpath.com from our server…

Questions

StackPath FAQ

Is StackPath down right now?
The status at the top of this page shows whether problem reports for the service are above their usual level, counted in 15-minute windows over the last 24 hours. This site does not ping, probe, poll, or monitor the service, so it can only reflect what people report. To check whether the problem is only on your side, load the same URL on a phone using mobile data, then try another network or device; if it fails only on your Wi-Fi, your router or local network is the likely cause.

Why does my StackPath CDN keep serving a stale file after I purge the cache?
Cache purge can take time to reach every edge location, and a browser or CDN cache-control header can keep the old copy alive. Check the response headers from your origin. Then request the file with a cache-busting query string to see if the edge has the new version; if other people see the new file and you do not, clear your local cache or test from a different network.

Why is StackPath WAF blocking legitimate visitors to my site?
A WAF rule can match a form field, header, cookie, or URL pattern and return a block page to real traffic. Check the security event log in the portal. Use the request path, rule ID, source IP, and timestamp to create an exception for that specific case, then replay the same request from the same network before you loosen the rule for everyone.

Why won't my StackPath edge compute workload start or stay running?
Edge compute workloads can fail when the image cannot be pulled or the health check never passes. Open the workload logs in the portal. The first failure message points to the image name or environment variable that needs a fix, and if the workload starts then stops, check the health check path and memory limit before you redeploy.

Why can't I sign in to the StackPath portal or reset my password?
Portal sign-in failures can come from an old password or a browser extension that interferes with the login form. Try an incognito window, check your spam folder, request a new reset link, and try a different browser. If your account was suspended for billing or abuse, the reset link will not fix it; contact the service through the channel listed on your invoice or account page.
For your site

Put the StackPath status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

StackPath status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/stackpath/"><img src="https://isitdownrightnow.app/badge/stackpath.svg" alt="StackPath status" height="20"></a>
Markdown, for README files
[![StackPath status](https://isitdownrightnow.app/badge/stackpath.svg)](https://isitdownrightnow.app/services/stackpath/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track StackPath

The status on this page comes from user-submitted problem reports for StackPath, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for StackPath, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. StackPath doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.

Elsewhere

Check other services

See all 500+ services

Problems elsewhere right now

Strips: user reports, last 6 hours, 15 minutes a segment.