Skip to main content
VWO logo

Is VWO Down?

No — VWO is up
VWO's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 425 ms

Right now

We could not read VWO's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

app.vwo.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
425 ms
Checked

By region

  • Amsterdam reachable, 374 ms
  • Dallas reachable, 183 ms
  • Frankfurt reachable, 1405 ms
  • Newark reachable, 150 ms
  • Paris reachable, 406 ms
  • Stockholm reachable, 396 ms
  • São Paulo reachable, 347 ms
  • Toronto reachable, 144 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam57 ms4 ms13 ms209 ms
Dallas58 ms1 ms25 ms174 ms
Frankfurt1002 ms2 ms32 ms1216 ms
Newark98 ms3 ms11 ms143 ms
Paris104 ms2 ms11 ms247 ms
Stockholm60 ms2 ms12 ms237 ms
São Paulo159 ms2 ms8 ms338 ms
Toronto61 ms2 ms10 ms132 ms
We check that app.vwo.com loads, not every feature behind it. Test it yourself

History

VWO website availability

Measured by FlareWarden · app.vwo.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
434ms

Last 30 days

71-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 31 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 30 checks
Oct 17: 100.00% uptime, 29 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 31 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 31 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 24 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of app.vwo.com from multiple regions every 6 hours. VWO's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 71 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What VWO does

VWO is an experimentation platform for websites and apps. A JavaScript snippet called SmartCode loads on a customer's pages, decides which variation a visitor sees, and reports conversions back. Product and growth teams use it for A/B tests, personalisation, heatmaps and session recordings. Its parent Wingify merged with AB Tasty in January 2026 and is consolidating products under the Wingify name.

What an outage looks like

Running tests quietly stop applying. Visitors see the original page instead of their assigned variation, and conversions in that window are never recorded, so the effect is missing data rather than a broken site. The dashboard may fail to load or show reports that stop updating. Heatmaps and session recordings develop a gap over the same period.

What to do about it

Check status.vwo.com, which separates the VWO Application from DaCDN, the network that serves SmartCode to your visitors: a DaCDN incident affects your website traffic while the dashboard looks fine. SmartCode is asynchronous by default and times out rather than blocking, so your pages keep loading. Treat the affected window as unusable test data and exclude it before reading results.

Is it down for everyone, or just you?

If this page says VWO is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

VWO outage FAQ

Does a VWO outage break my website?
No. SmartCode runs asynchronously by default, so it loads alongside your page instead of blocking it. VWO applies a settings timeout of 2000 milliseconds and a library timeout of 2500 milliseconds, configurable up to 5000. When either expires, the original content is shown to visitors and the page finishes loading normally.
What happens to my running tests?
They pause without telling you. Visitors during the incident see original content rather than variations, and their conversions are not tracked. VWO retries on the visitor's next page view or refresh, so tests resume on their own. The lasting cost is a hole in the data, which is why excluding that window before reading results matters more than the downtime itself.
What is DaCDN and why is it a separate component?
DaCDN is the delivery network that serves the SmartCode library and campaign settings to your visitors' browsers. It is listed separately because it fails independently of the VWO Application: your dashboard can be entirely healthy while visitors on your site get no test at all, and the reverse happens too.
Why does VWO now redirect to Wingify?
Wingify is VWO's parent company and the brand the products are consolidating under. The application domain moved from app.vwo.com to app.wingify.com on 13 June 2026, though both still serve the same application, and help articles now sit on help.wingify.com. Wingify merged with AB Tasty on 20 January 2026.

How we measure this

  • We request VWO's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where VWO publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of VWO itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when VWO goes down

We check VWO every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required