You can now filter the bandwidth usage of servers and projects by the current and previous billing cycles, giving you the ability to see how your bandwidth consumption changes over time.
As the internet gradually moves to IPv6, all new deployments and reinstalls now include an IPv6 address.
This means you no longer have to request an IPv6 address, and your servers will now include a /64 address by default.
Also, you will see the IPv6 address showing up on the device page and the API for currently deployed servers. To make the new IP work with your server, you can set it manually on the device or trigger a reinstall.
We are incredibly excited to welcome London to latitude.sh's Edge Network. London is our first European region and one of our most anticipated and requested regions.
You can get a server in the region running in under 10 minutes starting today. We are starting with availability for the c2.small.x86 server, but have built enough spare capacity to support custom deployments too.
Interested in deploying custom hardware in London? Lets talk →
Use Flatcar to deploy container workloads and RHEL for that stable OS enterprises love all in under 10 minutes. Both Operating Systems are available for deployment on all available servers through the dashboard and API.
Searching servers across your different projects is now easier. On top of searching by device label, you can also find devices by their hostname or an assigned IP address.
The dashboard now remembers your last selected project: After logging in or switching to a different team, the dashboard will now send you to your last selected project instead of the Projects page.
Spot servers are now available on the new Latitude.sh Experience
Server filtering allows you to select servers that match certain criteria. You can set a filter that will show all available servers that are located in a region, leaving out all of the other ones.
This is especially useful for projects with many servers so you can more easily find and manage your bare metal servers around the world.
You can now see detailed information about your invoices.
The detailed invoice in the dashboard lists all line items and a description for each one. In addition, line items for Servers expand, allowing you to see costs associated with each bare metal instance in a project.
Read more in the documentation.
In addition to Google, we have added two more identity providers for you and your team to log into and sign up to Latitude.sh — Microsoft and Github.
If you are already using Google or email to log in, selecting a different identity provider will work without any additional setup.
Log in to the dashboard.
It is now possible to add a new card, remove one that is no longer in use, and select which of your cards should be the default one without going to a different page.
You can manage cards by going to Settings & Members -> Billing on your Latitude.sh dashboard.
You now have the ability to select a start and end date to filter Servers and Project Usage, allowing for a better understanding of your usage.
Check out the documentation to understand how Bandwidth Usage is calculated.
You can now see when an API token has been last used by going to Team Settings → API Keys.
Instead of buying pre-defined additional bandwidth packages, you can now add more bandwidth to your projects in increments of 10TB, reducing costs by up to 50%.
The new pricing is available at the Network pricing page →
We are excited to announce that for customers in the new Latitude.sh experience, bandwidth for servers in the same region and project are now automatically pooled.
That means you no longer have to monitor your bandwidth consumption for each server individually, and can now share unused bandwidth between servers that are located in the same region and project.