Is Brev AI down today?

How to Contact Brev AI Technical Support?

- Support email at support@brev.dev or hello@brev.dev;

- Discord community at brev.dev/discord for peer support;

- Help documentation at docs.brev.dev;

- GitHub issues for CLI and technical problems.

Latest News and Current Information:

- Official Website - https://brev.dev;

- Documentation - https://docs.brev.dev;

- Discord Community - https://brev.dev/discord;

- X (Twitter) - https://x.com/brevdev;

- GitHub - https://github.com/brevdev;

- LinkedIn - https://www.linkedin.com/company/brevdev;

- YouTube - Search "Brev.dev" for tutorials.

Brev AI Outage: Platform Unavailable or Service Not Responding

Service disruptions manifest as brev.dev website not loading, development environments failing to start, API endpoints unresponsive, or complete platform unavailability.

- Check Brev status page and social media for incidents;

- Refresh browser with hard reload (Ctrl+F5 or Cmd+Shift+R);

- Test platform access from different browsers;

- Verify stable internet connection without packet loss;

- Clear browser cache, cookies, and local storage;

- Try accessing via CLI tool if web interface fails;

- Switch between different network connections;

- Wait 15-25 minutes during suspected maintenance;

- Check if issue affects specific cloud regions;

- Monitor community channels for outage reports.

Authentication Problem: Cannot Login or Access Account

Account access issues include login failures, SSH key rejection, credential errors, or session expiration problems.

- Verify email address and password entered correctly;

- Use "Forgot Password" feature for credential reset;

- Check email inbox and spam for verification links;

- Clear browser cookies specifically for brev.dev;

- Attempt login from different browser or device;

- Confirm email verification completed during signup;

- Try GitHub or Google OAuth if account linked;

- Regenerate SSH keys if authentication failing;

- Ensure browser accepts third-party cookies;

- Contact support if account appears suspended.

Environment Launch Fault: Dev Environments Not Starting

Instance creation failures include environments stuck in provisioning, startup timeouts, or launch errors occurring.

- Check cloud provider quota limits not exceeded;

- Verify sufficient credits or billing configured;

- Review environment configuration for errors;

- Try launching smaller instance type first;

- Check selected region has available capacity;

- Wait for previous environment to fully terminate;

- Verify GPU availability if requesting GPU instances;

- Clear browser cache and retry launch;

- Try launching from CLI instead of web;

- Review launch logs for specific error messages.

Connection Issue: Cannot Connect to Running Environment

Access problems involve SSH connection failures, VS Code not connecting, or terminal access denied.

- Verify environment status shows "Running" in dashboard;

- Check SSH keys properly configured in account;

- Test SSH connection from terminal directly;

- Verify firewall rules allow SSH traffic (port 22);

- Try reconnecting after network change;

- Check VS Code Remote extension installed correctly;

- Use web-based terminal as alternative access;

- Verify SSH config file properly formatted;

- Check VPN not blocking connection;

- Restart environment if persistent connection failures.

GPU or Hardware Fault: Compute Resources Not Working

Hardware-specific problems include GPUs not detected, CUDA errors, insufficient memory, or resource allocation failures.

- Verify GPU instance type selected correctly;

- Check GPU drivers loaded with nvidia-smi command;

- Confirm CUDA toolkit installed in environment;

- Review resource limits for your subscription tier;

- Try different GPU type if current unavailable;

- Check GPU memory not exhausted by processes;

- Verify machine learning framework compatible;

- Monitor resource usage in environment dashboard;

- Restart environment to reset GPU state;

- Request quota increase for higher resources.

Package or Dependency Problem: Software Installation Failing

Software management issues involve package installation errors, dependency conflicts, or environment setup failures.

- Update package manager indices (apt update, pip install --upgrade);

- Check internet connectivity from environment;

- Verify sufficient disk space for installations;

- Use virtual environments for Python dependencies;

- Check package compatibility with system version;

- Try installing packages individually to isolate issues;

- Review installation logs for specific errors;

- Use Docker containers for complex dependencies;

- Clear pip or apt cache if corrupted;

- Check repository mirrors accessible from environment.

Persistent Storage Issue: Data Not Persisting or Lost

Data persistence problems include files disappearing after restart, volume mounting failures, or storage quota errors.

- Verify persistent storage properly configured;

- Check files saved to persistent volume path;

- Review storage quota limits not exceeded;

- Confirm volume mounted correctly in environment;

- Backup important data regularly to external storage;

- Check file permissions on persistent directories;

- Verify storage region matches environment region;

- Monitor disk usage with df command;

- Test writing files to persistent path explicitly;

- Contact support for data recovery assistance.

CLI Tool Malfunction: Brev Command Line Not Working

CLI functionality problems involve brev CLI commands failing, outdated CLI version, or authentication errors via terminal.

- Update Brev CLI to latest version available;

- Check CLI installation with brev --version command;

- Verify CLI authenticated with brev login command;

- Review CLI configuration file for errors;

- Check PATH environment variable includes Brev;

- Try reinstalling CLI from official sources;

- Verify API credentials valid in CLI config;

- Test CLI commands with verbose output flag;

- Check firewall allows CLI API connections;

- Review CLI documentation for command syntax.

Networking Fault: Port Forwarding or Tunneling Issues

Network connectivity problems include exposed ports not accessible, tunneling failures, or webhook endpoints unreachable.

- Verify ports properly exposed in environment config;

- Check firewall rules allow traffic to exposed ports;

- Test local connectivity before external access;

- Use correct public URL format from Brev dashboard;

- Verify service running and listening on specified port;

- Check port number not conflicting with system ports;

- Try different port number if current failing;

- Review network logs for connection attempts;

- Test with curl or telnet to verify connectivity;

- Contact support for persistent networking issues.

Environment Stop/Delete Problem: Cannot Terminate Instances

Management issues involve environments not stopping, deletion failing, or stuck in terminating state.

- Wait 5-10 minutes for graceful shutdown;

- Try force stop option if available;

- Check no active SSH sessions preventing shutdown;

- Verify billing allows environment termination;

- Clear browser cache and retry operation;

- Try stopping via CLI instead of web interface;

- Check environment not locked by processes;

- Review termination logs for errors;

- Contact support for stuck environments;

- Verify no protection settings preventing deletion.

VS Code Integration Issue: Remote Development Not Working

IDE integration problems include VS Code Remote not connecting, extension errors, or workspace sync failures.

- Update VS Code and Remote-SSH extension;

- Verify SSH configuration in VS Code correct;

- Check SSH key passphrase if using protected keys;

- Try reconnecting after VS Code restart;

- Review VS Code Remote logs for errors;

- Test SSH connection outside VS Code first;

- Verify VS Code settings not blocking connections;

- Try removing and re-adding remote host;

- Check VS Code firewall permissions;

- Use web-based editor as temporary alternative.

Billing or Credits Problem: Payment Issues or Unexpected Charges

Financial concerns include billing failures, unexpected resource costs, credit depletion, or payment method errors.

- Review detailed usage reports in billing dashboard;

- Verify payment method valid and not expired;

- Check for environments left running accidentally;

- Monitor resource usage and associated costs;

- Set up spending alerts and budget limits;

- Understand pricing structure for instance types;

- Review invoice line items carefully;

- Stop unused environments to prevent charges;

- Contact billing support with transaction IDs;

- Request itemized breakdown of charges.

Template or Configuration Fault: Pre-built Setups Not Working

Template deployment issues involve starter templates failing, configuration errors, or pre-configured environments broken.

- Try different template to isolate issue;

- Review template requirements and prerequisites;

- Check template compatible with selected instance;

- Verify all required environment variables set;

- Review template logs for configuration errors;

- Start with minimal template then customize;

- Check template repository for known issues;

- Verify dependencies available in environment;

- Try manual setup if template consistently fails;

- Report template bugs with specific details.

Performance Degradation: Slow Environment Response

Speed and efficiency issues encompass sluggish computation, high latency, or resource contention problems.

- Monitor CPU and memory usage with top or htop;

- Check disk I/O performance with iostat;

- Verify network latency to environment region;

- Scale up to larger instance type if needed;

- Close unnecessary processes consuming resources;

- Check for runaway processes with high CPU;

- Optimize code for better resource efficiency;

- Consider GPU acceleration for ML workloads;

- Test during off-peak hours to isolate load;

- Review application logs for performance bottlenecks.