Menu
April 10th, 2018

Introducing Class Based Naming in our Portal and API

Today we made the change to our new naming configuration, this change is reflected in both the portal and on our website. This change is backwards compatible, so any API or other tools that you currently leverage with old names will still work. This way you can switch to the new names at your own pace.

That being said, the new names may take some time to get comfortable! To make it a bit easier, here’s a list of the new naming configurations matched with their legacy names: 

  • Type 0 - t1.small.x86 
  • Type 1 - c1.small.x86
  • Type 1e - x1.small.x86
  • Type 2a - c1.large.arm
  • Type 2 - m1.xlarge.x86
  • Type 3 - c1.xlarge.x86
  • Type S - s1.large.x86

Our newest machines were born with the latest naming convention, so no change there:

  • AMD - c2.medium
  • Intel Scalable - m2.xlarge.x86

Pro hint: since most of our machines are x86 architecture, the .x86 is optional. You  can use either “c1.small” or “c1.small.x86” and you’ll get the same result.

For further information on this change, please take a look at our documentation or just drop us a note via help@packet.net!

Don't see what you need? Need a platform demo? Contact us so we can chat about options, and help you get the most out of our platform.