Is Vev Down Right Now? Check if there is a current outage ongoing.

We’re currently experiencing an outage due to issues with our authentication provider, Google Identity Platform. As a result, users are temporarily unable to access the platform. Only the platform is affected, not published projects We are monitoring the situation closely and will provide updates as soon as the issue is resolved. Thank you for your patience!

No reports about further issues have been received, so we assume all issues has been resolved

We have implemented a fix, and the platform should now be working. Please try reloading your browser window. We are actively monitoring the situation to ensure everything remains stable. Thank you for your patience!

The isse has been identified and developers are working on a fix

The incident has been successfully resolved by Google Cloud Platform at 03:44 CET. It appears that the issues were limited to authentication, ensuring that no data loss occurred during this period. Published content remained unaffected throughout the outage.

Google has confirmed the issue, causing access problems for authenticated users trying to access our Firestore database. Unfortunately, there are no available workarounds at this time. We'll need to patiently await resolution from the Firebase team. For more details, please refer to: https://status.firebase.google.com/incidents/JH8hiSsfnSZHMdZqFTaC

We've pinpointed an issue within our database that's tied to access rules, and it appears to be originating within the Google Cloud Platform itself. Our team is actively exploring potential workarounds, while also engaging with Google Cloud Platform to gather additional information and resolve the issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

Publishing operations seem to have normalized after the Cloudflare outage; we suggest you republish any impacted project, and contact our support team for any help while we continue to monitor progress.

We have resolved the issue that resulted in pages being published as blank, but we continue to face errors with publishing due to the Cloudflare outage.

We have identified that this issue is due to Cloudflare's outage, and we are currently working to find a solution.

We are continuing to investigate this issue.

We are currently aware of an issue where attempts to publish are resulting in blank content. The issue seems to be related to Cloudflare's system, and our team is actively investigating the cause and working towards a resolution.

The issue has been successfully resolved, and publishing should now function normally.

A fix has been implemented and we're now closely monitoring its progress.

We're still working on a fix. For now, republishing your project works as a temporary solution.

We've identified the issue and it's related to Google Cloud Storage timing out.

Some users report an unexpected error when publishing projects; the issue is currently under investigation.

The DNS issue affecting the .vev.site domain has been resolved, and staging links should now be functioning normally. Please note that due to DNS caching, you may still encounter a "This site can’t be reached" message. If this occurs, simply try again in a few minutes.

Our engineers have successfully identified the issue and are now working to resolve it.

We have received reports that websites under the vev.site domain are currently inaccessible. Our team is actively investigating the issue, and we will provide updates as more information becomes available. Please note: This issue only impacts the .vev.site staging links. It does not affect embeds, exported projects, or websites published to connected domains.

We're happy to report that the issue has been resolved. The issue only affected projects with a watermark that were published within the last hour. To ensure proper functionality of all behaviors in published content, we recommend re-publishing all watermarked projects that were published in the last hour. Thank you for your patience and understanding while we worked to resolve this issue. If you have any further questions or concerns, please don't hesitate to reach out to our support team.

UPDATE: The issue only concerns projects where the "Made in Vev" watermark appears.

We are currently experiencing an issue with publishing that may cause content behavior to break if published at this time. Our team is actively investigating the issue and working to resolve it as quickly as possible. We advise all users to refrain from publishing their content until the issue has been fully resolved to avoid any potential negative effects. We apologize for any inconvenience this may have caused and appreciate your patience as we work to fix the issue. Thank you for your understanding.

The issue has been resolved, all index pages now load appropriately for the affected stanard hosting instances.

We are currently investigating the issue of index pages showing up as "Not found" when published to a recently created standard hosting.

Good news, everyone! We're happy to report that the issue with some projects endlessly loading has been fixed! Our team was able to identify and resolve the root cause of the problem, and all projects should now load as expected. Thank you for your patience while we worked on this issue. As always, if you have any questions or concerns, don't hesitate to let us know via the chat bubble.

So, we've encountered some issues with a few projects that just won't stop loading no matter what you do. But no worries, we've already pinpointed the problem and we're currently working on a fix for it. In the meantime, we've also found a nifty workaround to bypass the loader. So if you happen to encounter this issue, give us a shout in the chat bubble and we'll sort you out!

This incident has been resolved.

The issue with loading should now be resolved after a reload of the editor.

We have discovered issues with loading assets and fonts in the editor. This is only an issue in the editor and will not affect published projects

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Some Vev users are encountering an issue with publication. We have identified the cause and are currently working on a fix, which shouldn’t take more than 30 minutes.

The issues triggered by the Google Cloud (Firebase) outage has been resolved.

We will provide a status update as soon as we know more.

Vev users are reporting missing projects. We have discovered and identified that Google’s Firestore is experiencing an outage and responding with 500. Rest assured that live projects are not affected.

Issue resolved.

A fix has been implemented and we are monitoring the results for any other issues before closing. Any affected users should now see their layers reflected correctly in the Design Editor.

This issue has been identified. A patch is being released to fix this for any affected users.

The caching issue reported yesterday has been resolved. Contact Vev Support if you have any further issues or questions.

We are continuing to monitor for any further issues.

We have deployed a fix for this issue and will be monitoring the situation. If you are still having issues with content that seems to disappear or not be in the place you expected it, please contact Vev support by using the bottom-right in-app help bubble.

We’re currently experiencing a caching issue that makes it appear that content in your project is missing. Rest assured that it’s not gone, it’s just not visible. We’re actively working on a fix. In the meantime, working from an incognito tab will resolve the issue.

Our Standard Hosting experienced a partial outage due to issues with our cloud provider, Netlify. Uncached content could fail to load with an Internal Server Error. The issue was resolved by the provider 4 hours and 30 minutes later according to their incident page. See https://www.netlifystatus.com/incidents/f0frsy75h7n2 for more information

New Projects created would experience that Sections that are added would be gone when reloading. For the duration of the incident, the page lost track of the sections and does not show them after a reload. The content is not lost, and if you have experienced this issue, contact Vev Support to get it restored if your section does not automatically get restored soon. Issue was resolved 13:40 UTC.

The issue has been resolved and affected users projects should now publish every time.

We are continuing to investigate this issue.

We have received reports from users struggling with Publishing and are investigating the issue.

RESOLVED After monitoring and internal + external testing we now regard this issue resolved. If you are still not seeing your fonts rendered, updating your project by moving something will trigger Vev to re-render any cached elements and your fonts will render as expected. If you still encounter any issues with Fonts, please reach out to Vev Support.

A fix has been implemented and all fonts should work as per normal. We are still MONITORING the situation to ensure that we everything is working.

The problem has been identified and a patch is being released. ETA 1 Hour. Projects that have been published while the incident was ongoing will need to be republished to get the correct font rendered on the Published Content.

We've received reports and are currently working on resolving an issue where custom fonts are not being rendered on the published content after publishing. Please avoid publishing any LIVE projects, or publish to the STAGING domain first before publishing to the LIVE one before updating an article.

# May 19, 2021: **Platform and Content Downtime** The following is a detailed overview of the incident leading to downtime of the Vev platform on the 18th of May 2021. We sincerely apologize for any inconvenience this caused our users. Since the crash was reported, the Vev team has been working to ensure this does not happen again and to improve our routines when it comes to updating our users of the status of the platform. ## **Summary** From 22:30 on May 17th, 2021 all services connected to the vev.design domain were inaccessible. The DNS registrar \(Namecheap\) blocked the domain due to malicious content published by Vev users to the free hosting service \(eit.vev.design\). The incident was first discovered on Monday 17th May 2021 at 22:30, the root cause of the issue was not resolved until 11:38 am on 18th May 2021. **This incident does not in any way compromise security of other Vev accounts or content published through the Vev platform by other clients.** The consequence of the incident was 13 hours downtime of the vev.design domain including published sites with content on the Vev CDN such as images, fonts, videos, and scripts that did not load. ## **Timeline** | Report | Description | | --- | --- | | `22:30 17.05.2021` | `First reports of Vev crash came in` | | `08:28 18.05.2021` | `Root cause was discovered and DNS provider was contacted` | | `Every 15 min after 8:28` | `Talked with new Namecheap support agent` | | `11:38 18.08.2021` | `DNS running as normal` | ## **Root Cause** The root cause of the incident was due to users in Vev abusing the free publishing \(eit.vev.design\) to create phishing sites. These types of sites break with the Acceptable Use Policy \(AUP\) of our domain registrar \(Namecheap\), and thus the domain got reported as abuse, and therefore everything connected to the domain was blocked. We have since discovered a set of users in the Vev platform using the platform to create malicious sites. ## **Resolution and recovery** * As soon as we discovered the issue we contacted Namecheap support. * 1st line support did not have the rights to open the domain because of the abuse reports so had to wait for Namecheap Legal & Abuse Department to review the case. * Contacted 1st line support every 15 min after the first contact. * Tried helping clients in urgent need to publish project using the direct google storage URL, but required too much manual work. * At 11.00 we reached Namecheap Legal & Abuse Department and the blocker of the domain was removed. ## **Corrective and Preventative Measures** Preventative measures completed so far prevent this type of incident from happening again, as all published sites breaking with the Acceptable Use Policy \(AUP\) of our domain registrar \(Namecheap\) are taken down. Additional measures will be done consecutively to further ensure security routines: * **Suspend all suspicious users from the platform** * **Analyze all content on eit.vev.design and delete malicious sites** * **Transfer vev.design domain to our Cloudflare enterprise account** Moving our domain registrar over to Cloudflare will make it easier for us to discover issues, and since we’re enterprise clients of Cloudflare would not block our domain on this short notice. * **Setup status page for all services in Vev with automatic reporting/subscription features** This will enable us to faster discover the root cause of the issue as well as allow users to see what the status of the vev platform is. Live updates will also be shared here in the future . * **Transfer eit.vev.design to a.vev.site** This will be done as a measurement to make sure user content **does not** affect the authority of the vev.design domain. So if malicious sites were to be published on the free domain, the abuse will not take down our main domain name. _\*\*_ * **Stricter user control** We will introduce a stronger measure to validate our users, to make sure they are not using the platform with bad intentions. Password login will require verification All emails will run through an anti-spam check and not be approved * **Automatic Safe-browsing checks of the published content** We will add an automatic analyzer \([Web Risk | Google Cloud](https://cloud.google.com/web-risk) \) of all links when publishing projects blocking malicious projects from being published, as well as flagging users, abusing the platform. * **Client-hosting of Images and Videos** Our Engineering and Product team will look into solutions for our users to host images and videos added to Vev projects. _\*\*_ ## **Security Status on the Vev platform** In Vev Security and Privacy is something we strive to build into our products by design and by default. So, we rely on international and recognized standards to ensure we get the best of both worlds, from design and ease of use, flexibility and security. **This incident does not in any way compromise security of other Vev accounts or content published through the Vev platform by other clients.**

Platform and all staging and live content is down

# May 20, 2021: **Google Firebase Brought Down Access to the Editor** ## **Summary** Around 09:47 our system detected the Vev editor was not loading. We discovered this issue was related to Google Firebase routing rules not working as expected, this caused the users not to be able to open the editor. At the time of writing this report, the issue has still not been resolved by Google, but we have deployed a workaround to make the editor run. ## **Timeline** | Reports | Description | | --- | --- | | `09:47 20.05.2021` | `Issue was detected` | | `10:00 20.05.2021` | `Root cause of issue was discoverd` | | `10:45 20.05.2021` | `Workarround to the firebase rules was deploy` | ## **Root Cause** The root cause of the incident was a Google Firebase router breaking. This was a widespread issue for all applications using Google Firebase Hosting, utilizing the hosting rewrite rules ## **Resolution and recovery** * First, we tried to replace scripts loaded from the \_\_ folder with full URL to \[[https://vev-prod.firebaseapp.com/\_\_/](https://vev-prod.firebaseapp.com/__/)\]\([https://vev-prod.firebaseapp.com/\_\_](https://vev-prod.firebaseapp.com/__)\) which was working at the time * This failed since these scripts disappeared as well * Changed all scripts loaded from \_\_ to be cdnjs script or loaded locally ## **Corrective and Preventative Measures** * Review all scripts not included in the editor bundle if it advantageous to include them

An issue with Google Firebase has bought down access to the Editors, the platform is currently inaccessible. Stay tuned for updates.

# June 8, 2021: **Google Hosting Brought Down Access to the Editor** ## **Summary** Around 11:55, we discovered issues related to google hosting responding with 503. After a short time we found many other services like [http://nyt.com](http://nyt.com), [amazon.com](http://amazon.com) [http://stackoverflow.com](http://stackoverflow.com) were down as well, and the issues seemed to be linked with services using the Fastly CDN. The issue was resolved within an hour by fastly. ## **Timeline** | Reports | Description | | --- | --- | | `11:55 08.06.2021` | `Issue was detected` | | `12:50 08.06.2021` | `Fastly found the root cause of the issue, and services started working again` | | `13:30 08.06.2021` | `Everything seems to be back in order` | ## **Root Cause** The root cause was the Fastly CDN having outage for unknown reasons ## **Resolution and recovery** * The issue was resolved by fastly before we’re able to apply any fixes of our own. * A potential fix would have been to move our static hosting of the tool to another CDN network ## **Corrective and Preventative Measures** None, as Fastly is one of the biggest CDN providers in the world, we have to trust that they keep their services running, as so many large companies rely on this

Google is down! Which has brought us and 99% of the entire internet down. Vev is currently inaccessible — stay tuned for updates.

Issue seems to have been resolved

We are continuing to monitor for any further issues.

We found some issues related to old elements which broke because of changes in release today

Animations are missing from Design Editor projects. We are currently investigating the issue and will update once a solution has been found. Currently, animations on all past published content with animations are working. We recommend you do not re-publish otherwise animations may be removed until we find a solution.