Looking for something? Visit: • vercel-status.com for status updates • vercel.com/help for support • vercel.community for the @vercel community
35
7
10,258
Our investigation has determined a member of our customer-facing team violated company policy. We have taken appropriate action. This was an error in human judgment; Vercel’s internal security systems worked as expected. The employee did not have access to any source code, secrets, or the ability to change settings or deployments. The employee used customer information, which they have access to for their job duties, to pursue a personal trademark matter. We have zero tolerance for this behavior, have taken action, and will continue reinforcing procedures to prevent future occurrences.
12
11
271
223,468
We are aware and are investigating this report. Please email security@vercel.com with any additional details to help us investigate.
1
46
26,340
Replying to @NikkitaFTW @vercel
Hello, We have unblocked your account and the deployment is working again. Let us know if you have any further questions or concerns.
1
20
We currently have a known issue with the Vietnamese ISP Viettel, who have decided to block Vercel's IP address. We have put in a request with them to get this unblocked and are working with them to ensure they don't block us going forwards.
6
18
Replying to @d4m1n @vercel
HI Dan, this issue should be fixed now. Feel free to reach out us at vercel.com/help if you have any question.
1
14
3,273
Replying to @theo @t3dotgg @vercel
Hi there! We're currently investigating this issue with certificate generation. We will share updates on our status page: vercel-status.com/incidents/….
10
Replying to @theo @t3dotgg @vercel
Hi there! Unfortunately, we are not able to replicate this issue — is it possible to clarify if you are still experiencing issues with the dashboard?
1
7
Replying to @wongmjane @vercel
Hi Jane, Apologise for the inconvenience that may caused. Could you send us an email to registrations@vercel.com from your registration email? We can take a closer look and advise further. Thank you!
1
7
Hi Rox! This should be working as expected now. We'd highly recommend the following article for advice on reducing your Serverless Function Execution: vercel.com/guides/how-can-i-… You can also reach out to the ▲ Customer Success Team via vercel.com/help for future Qs 🙌
7
Hi Cory! Appreciate you for getting in touch — we have responded to your support ticket now and can confirm that we are actively shipping a fix to resolve the issue.
1
4
403
Replying to @browniefed @vercel
Hello Jason, Monorepo support is a high priority for us. While we don't have first-class for it yet, you can use any build command on your project: vercel.com/blog/advanced-pro… A few users using monorepo will write a small bash script with all the commands needed to deploy their app.
5
Hi Jack! We have just replied to the case you submitted. Please check your email.
4
We take feedback from our customers very seriously. This is a process that we are not willing to give up anytime soon and we do appreciate you taking the time to write about your experience. I apologize for any inconvenience we may have caused. zeit.co/feedback
2
4
@nftliciousy Can you DM us with information so we can investigate? We're here to evaluate abuse reports and take action as needed. nitter.app/messages/compose?11762…
4
Hello Alistair, An official Deno runtime is certainly in our plans for the future. But you can use it right away with the runtime developed by @lcasdev: github.com/lucacasonato/now-….
4
Replying to @gustavobini @zeithq
Soon Gustavo. This will be another feature of zeit.co/blog/advanced-projec… where you will be able to specify secrets per project.
2
4
Replying to @ksaitor @zeithq
Thanks for the feedback! Our very own @pacocoursey has fixed this and we've pushed it to production!
1
4
Replying to @tdinh_me
Hi, we are currently investigating the issue. Please follow our status page for updates: vercel-status.com. We apologize for any inconvenience.
1
3
293
Hi there, The team is currently investigating an incident. Status updates can be found here: vercel-status.com
1
4
Hello Cristian, We don't support NX-powered apps at the moment. Our team is working on making this feature available for you shortly, and we should get back to you once we support NX.
1
4
Hello Jorge, When using Next.js with Vercel, we will automatically optimize your code and bundle several paths into a single function. So it is unlikely that you will ever face this limit on our platform.
1
3
Replying to @zlwaterfield
Hi Zach, we pushed a fix for this. Please redeploy and let us know if you are still having trouble: vercel.com/help. Thank you!
3
175
Replying to @theo @t3dotgg @vercel
Thank you for the clarification and thank you for sharing! We'll keep an eye out for similar issues in the meantime so we can investigate further.
3
Hi there, GitHub web hook was degraded momentarily and it should be resolved now: vercel-status.com/incidents/…
2
44
Replying to @JessTelford @vercel
Hello Jess, On Vercel, you can use the ICU package without any issues. Here is how: - Add the "full-icu" dependency to your project - Modify the build script of your app to "NODE_ICU_DATA=node_modules/full-icu next build" Give it a try!
1
3
Yes. We are continuing to investigate reports of elevated error rates on the Vercel Dashboard, existing deployments, and live traffic. We will share updates as they become available. vercel-status.com
3
Hi there, you can consider using monorepos for such an implementation as described here: vercel.com/docs/git#monorepo…. Also, please note that for a NextJS project, the API and the front-end can reside in the same project and hence the same domain
1
3
What we did: - Fixed a bug where "On Demand" instances were being used for free. - Full disclosure and transparency for a potential increase in your bill. - Reassured our pricing structure was not changed. You can view that information on zeit.co/pricing/v1
2
3
Hi Kostja, could you please try again? Our engineers have applied a fix related to this issue.
2
3
Replying to @wongmjane @zeithq
Hello Jane, We are sorry to hear you received that error when attempting to deploy your project. Can you write to us on zeit.co/support/request so we can assist you better? Alternatively, you can also DM this account for any assistance.
3
Hi there, We would gladly help assist you in debugging whatever issues you are experiencing. Please feel free to DM us.
1
1
Multi-env support is coming and directly in your project's configuration UI. This is our top priority and it should arrive very soon! My apologies for the bad experience and let us know if you have any other feedback.
1
3
Replying to @uwteam
We apologize for the confusion. The plan we are deprecating is called the "Free" plan. We will still offer a free plan for individual users, which is now called "Hobby". vercel.com/support/articles/…
1
3
Replying to @alistaiir
Thank you so much for your patience— the wait is almost over! Samples are in, items are being created , and will be shipping by march.
1
3
Hi Daniel. Please double-check the NextJS configuration with Tailwind here: tailwindcss.com/docs/guides/…. Otherwise, feel free to send us a DM using the button below with your account email and deployment link. Thanks nitter.app/messages/compose?recip…
1
1
3
Replying to @holyshtjoe @vercel
Hello Joel, We don't offer free plans for teams at the moment. However, you can ask for sponsorship if your project fits the criteria: vercel.com/knowledge/can-ver…
2
There was an incident affecting some of our serverless functions during 00:20 - 01:35 UTC. The incident has been resolved and reported at vercel-status.com/incidents/…. Please submit a case here if you are still experiencing problems 👉🏽 vercel.com/help
Thank you for sharing your case number — we can confirm that we've found this and are looking into the situation as we speak. We'll share an update on the case as soon as possible.
2
2
Thank you, Peter. Rest assured, we weren't intentionally trialling newspaper formatting for our articles 😉 Our team are aware and looking in to this!
2
2
Replying to @gr2m
Please, reach out to support@zeit.co so we can do identity checks and arrive at a solution.
1
Hi Matteo, our Engineering team is actively looking into the issue to ensure you face no difficulty with this. We will offer a more in-depth answer in reply to your ticket. We appreciate your patience; stay tuned for updates!
1
2
Replying to @mfrachet @vercel
Hi Marvin, this is a great question! I would encourage you to create a discussion here, github.com/vercel/next.js/di…, where you can get contributions from the entire NextJS community!
2
Replying to @wunderacle
Hi Claudio, If you have more than one Middleware, you should combine them into a single file and model their execution depending on the incoming request. nextjs.org/docs/advanced-fea…
2
59
Replying to @sreuter @vercel
There is a GitHub downtime (missed web hooks) from Apr 19 00:31 UTC until Apr 19 02:29 UTC that prevented the creation of new deployments. The issue has now been resolved by GitHub and new commits are triggering new deployments successfully.
2
Replying to @jackyef__ @vercel
Hi Jacky, if you upgrade to Nextjs 11.1, you should see a comparable memory usage since the ability for sharp being optionally installed was added. Post 10.0.8, sharp was removed entirely in favor of webassembly.
1
1
Vercel is the best platform to take advantage of Incremental Static Regeneration (ISR) with Next.js!
2
This should be resolved now! Let us know if you have any further questions or concerns.
2
Replying to @topazdecimal
We apologize for the confusion. The plan we are deprecating is called the "Free" plan. We will still offer a free plan for individual users, which is now called "Hobby". vercel.com/support/articles/…
1
2
Hi Xuanwo, thanks for your feedback. We would really appreciate it if you could share this feedback by clicking the Feedback button on the top right of your Dashboard page.
2
Replying to @y_shinnoki
Hi, this should be fixed now. Let us know if you are still facing issue.
1
1
2
Replying to @stephenhaney
We have an announcement scheduled for today for one of the most requested features so far. After that, we do plan to work on monorepo support and you should see it live in the upcoming months.
1
2
Hello Alan, Certainly, we do not take security issues lightly. We know at this moment that your webhooks were not exposed or shared with any 3rd parties. We will give you a full post-mortem about this incident in the upcoming days.
1
2
We can confirm that a site on your platform was reported as phishing. In compliance with our terms of service, we sent you an email before pausing your account. Please respond to discuss reinstating your account and removing the infringing site.
1
1
628
Hi there. Thanks for reaching out. Would you please be able to raise a support case via vercel.com/support/request so we can work with you further on the use case that you have here? You may find the documentation located here useful in the meantime: vercel.com/docs/concepts/fun…
1
1
Hi Tony, please review the NextJS getting started course here: nextjs.org/docs/getting-star…. Since NextJS is built on top of React, it will definitely help to have a good knowledge of React before starting.
2
Replying to @ananbatra @vercel
Hi Anan, our metrics show a momentary blip which impacted a small subset of customers. If any issues persist, please do follow the links in our bio to get in touch with the team!
1
2
Hi there, we are investigating this issue currently. Could you create a support case with our Customer Success Team → vercel.com/help#issues
1
2
79
Replying to @mds @vercel
Hello Matt, We highly recommend that you use Vercel with one of our git integrations: vercel.com/import Did you try that?
1
Hey Akos, we can navigate to the URL without any error on our end (tried both www & non-www versions). It is likely this may be a code-related issue. However, once you've ruled this out & still need further support, you can reach out in a case via vercel.com/help. Thanks!
1
2
Yes, we send alerts when your account approaches 75% and 100% usage, as well as warnings when it reaches 200% and 300%, to avoid unexpected surprises. If you ever need assistance with your usage, feel free to contact our team: vercel.com/support/request We're here to help!
2
Replying to @ddprrt @vercel
Hi there, I can confirm that your billing page is working as expected again, thank you for your patience.
1
Replying to @RyanCaoDev
Indeed. It appears they are recovering and you may now be able to deploy. Latest update at vercel-status.com/
Hi there! Are you able to send these details to abuse@vercel.com so we can take a closer look? Thanks.
1
1
2
Replying to @corscheid @vercel
Hello Corey, At the moment, if you want to rename a Vercel project, a re-import is required. We are working on this feature, and you should expect it soon.
1
2
Replying to @_zacharyhorvath
Hi there, thank you for taking time to report this. This should be fixed now. :)
1
2
Replying to @tdinh_me @minhlq96
We currently have a known issue with the Vietnamese ISP Viettel, who have decided to block Vercel's IP address. We have put in a request with them to get this unblocked and are working with them to ensure they don't block us going forwards.
3
2
Hi there! Unfortunately, it is not possible from this page. You can specify it in your package.json, or deploy it now, then configure it later in your project's General settings.
1
2
Replying to @j7s4_ @vercel
Hey Laes, all systems are normal on our end. If deployments are still not triggering for you, then please follow the link in our bio (to create a case or community post mentioning the SHA for the latest commit) as this will help us to help you more effectively. Thanks!
2
Replying to @crud_engr
Hi, we have received your request and currently routed to respective team. Our team will get back to you shortly about the next steps. Thank you!
1
Howdy! Thanks for reaching out. May you re-attempt your deployment, please?
2
Replying to @Mauriemm
I'm sorry to hear that Mauricio, can you open a ticket at support@zeit.co and include a link to a repository? I'd love to help you get this working even better!
1
2
Replying to @smakosh @Wix
Hi there, thanks for sharing. This can happen if your friend added the domain to a service that uses Vercel. Could you please ask your friend to submit a case here? vercel.com/support/request
1
2
Hi Azhar! We'll be able to help you out with your billing/bandwidth — please submit a request via vercel.com/support/request. Thanks 🙌
2
Replying to @gr2m @vercel
Hello Gregor, Our team is working on this feature as we speak. We can reach out to you once it is released. Stay tuned!
1
Replying to @ThisIsSingleton
Hey James, You can check the Next.js source code here: github.com/zeit/next-site We are glad you like it! Kudos to the Next.js team.
2
Hi Miguel. Thanks for the valuable feedback! I will share it with the product team
2
Replying to @Mathieu_Bour_
Hi, It sounds like related to this incident: vercel-status.com/incidents/… We are working on fixing this issue as soon as possible and will have updates there.
2
34
Replying to @__junaidshah
Hi Junaid! We are continuing to investigate reports of elevated error rates on the Vercel Dashboard, existing deployments, and live traffic. We will share updates as they become available. nitter.app/vercel_status
1
2
Replying to @gokul_i
Hey! thank you for sharing the feedback! we have passed this internally. :)
1
2
Replying to @_grsoares @vercel
Hello Gabriel, Using the memory of a Serverless Function to cache data is possible. However, do notice that two concurrent requests can be processed by different functions. Another factor to consider is that Serverless Functions will get recycled after a few minutes.
2
2
Replying to @DBauszus @vercel
Hi Dennis, We’re sorry that you found out about this in an unexpected manner. Node.js 14 is only used by default for new projects, as outlined in this Changelog post. In the future, we will make sure to email as well in case you miss the Changelog. vercel.com/changelog/node-js…
2
There is a feature request already opened for it. You can follow it over at github.com/vercel/next.js/is…
1
2
Replying to @vsnthdev
I have posted an answer over in GitHub 🙂
1
2
Replying to @howard86_ @vercel
It seems our partner is having some difficulties handling the unexpected spike of requests. We are working with them to resolve the issue as soon as possible.
2
Hi Rob, thank you for getting in touch. We will mark the ticket as closed. Have a good one!
2
Hello Oliver, We are glad you want some Next.js swag. Stay tuned for the announcements related to the conference.
1
Replying to @0xA5A5 @atmattt
Join us here to talk about all things Vercel nextjs.org/discord
1
2
Replying to @MinnerAlgo @vercel
Hi Minner, thanks for providing the case number. We will reply directly in the case which should come to your email.
1
2
Replying to @jkup @vercel
Hello Jon, Vercel offers first-class support for frontend apps and serverless functions as helpers. Serverful workloads, such as Express servers, are better deployed in a serverful environment. You can check templates on vercel.com/new.
1
2
Hi Martin, this story example may be helpful: github.com/vercel/next.js/tr…
2
Replying to @romansorinn @vercel
Hi Roman, I believe there is template-level code required to activate the integration. @supabase will be best to answer this question.
2