New Term-Based Discounts for Equinix Fabric Are Here
We're excited to introduce Equinix Fabric Term-Based Discounts for inter-metro i.e. remote virtual connections (VCs) between your own assets and to your service providers including hyperscalers such as AWS, Azure, Google Cloud and Oracle. This new pricing option is designed to help you save more while enjoying the high-performance connectivity you rely on. What's New? You now have the option to select 12, 24, or 36-month contracts for inter-metro VCs from your Fabric ports, Network Edge virtual devices and Fabric Cloud Router instances. Here's how you'll benefit: Lower Monthly Rates: Save between 15% and 50% compared to on-demand pricing. For example, a 1 Gbps inter-metro virtual connection between London to New York drops from $1005/month to just $503/month with a 36-month term-based plan. See how much you can save using the Fabric pricing calculator, accessible via the Fabric portal. Simple Provisioning: No approvals required. Just select your term in the self-service portal or Fabric API and enjoy the savings. Broad Capability Support: Applicable across Point-to-Point (EPL & EVPL), Multipoint-to-Multipoint (EP-LAN & EVP-LAN) and IP-WAN services supported by Fabric Cloud Router. Also supported for Z-side service tokens. Predictable Cost Structure: Term based contracts provided set monthly rates, making it easier for you to manage your annual budget. Things to Note Discounts are available only for inter-metro VCs (intra-metro i.e. local VCs are not eligible. Discounts are currently not supported on Network Edge virtual devices to AWS, but are coming soon. Term-based discounts cannot be added to existing VCs, so you’ll need to create a new VC with your chosen term. Why This Matters By locking in discounted rates, you can optimize costs and achieve predictable spending without sacrificing performance, reliability, or flexibility. This is the perfect opportunity to create cost-efficient connectivity solutions tailored to the demands of your business. We'd Love to Hear From You Tap into these savings today by selecting a term-based discount during your next VC provisioning. We’d love to hear how this pricing option benefits your operations. Share your feedback with the team!
User created port labels
The ability to create user generated port labels would be amazing. This way I can more easily determine which one goes to which datacenter on our side. You can leave the current label in the port properties so it can be referred to when putting a ticket in, but the current naming convention is difficult to correlate which port is for which of our circuits going to which datacenter. Thanks!Connecting Fabric Cloud Router to AWS and Azure
In this video, we'll show you how to Create a Fabric Cloud Router, create a connection to AWS, create a connection to Microsoft Azure, and then run a ping test between those two virtual machines running in the cloud environments. This step-by-step demo shows how quickly you can create a Fabric Cloud Router, and then with the help of Quick Connect for AWS and Azure, connect the router with Virtual Machines at Equinix. And finally, how to test the new connections. Create connections using Fabric Cloud Router in the Fabric portal: https://fabric.equinix.com/
How to Order EIA with Fabric Using Provider-Independent IP Addresses
In this video, we'll show you how to order an Equinix Internet Access connection as a Virtual Connection within a Fabric Port using provider-independent IP addresses. This step-by-step guide takes you through the configuration of a new connection helping you to choose the correct bandwidth, port, and routing configuration. Create a new connection in the Fabric Portal: https://fabric.equinix.com/
Is a Digital Services Agreement (DSA) required to order/use Fabric Cloud Router (FCR)?
Hey Community! We often get questions about Fabric Cloud Router and we’re here to help clarify for others who might have the same question in the future. If you’ve got additional questions about FCR, ask them in Community! What is a Digital Services Agreement (DSA)? The Digital Services Agreement is a document that is presented to users when setting up a Billing Account to order digital services like Fabric Cloud Router. If this is your first time ordering digital services with Equinix and you do not have an existing Billing Account (or sometimes called a Cloud Billing Account), you’ll be directed to digitally sign the DSA. If you're creating additional Billing Accounts, you will be asked whether you want to use an existing Digital Services Agreement or sign a new Digital Services Agreement. If you need guidance on either DSA option, please review this documentation. [Example only for reference and may not reflect latest version of DSA] I’m a new customer; do I need to sign a Fabric DSA? Yes, if you are a new customer and using Fabric for the first time, you’ll log into the Fabric Portal to order an FCR and be prompted to follow the click-through DSA. This is meant to allow and support our new customers who are looking to quickly onboard and use Fabric. What about if I'm an existing Equinix customer using Fabric for the first time, do I need to sign a DSA? Great question! If an existing Equinix customer clicks through Fabric for the first time they would also be prompted with the click-through DSA, however, if this customer already has an existing MCA/GTC Agreement with Equinix, these can be associated (by the Sales / Legal Ops) to a Billing Account for Fabric, and once that's correctly completed, the Billing Account should how as Active for the customer in the Portal and they will not be prompted to sign the click-through DSA. I already have a MCA/GTC agreement, but I’m getting prompted about a DSA. If an MCA/GTC agreement has been associated with the billing account for Fabric and the customer is still being prompted with the click-through DSA: The association of the MCA/GTC to the billing account may not be setup correctly and we recommend to contact support. The user logged into the Portal may not be associated with the correct Fabric Account/Project that has access to the active billing account.What tools and vendors are folks using for multicloud networking scenarios?
Hey folks, I'm curious to hear how folks are managing multicloud networking setups. With so many tools and vendors in the space I'm eager to hear what everyone is using to connect between different cloud environments. What vendors or solutions are you using to manage multicloud networking? (e.g., Equinix, Megaport, Aviatrix, Cisco, etc.) Are you using Layer 3 or 4 networking for your interconnections? Which cloud providers or service providers are you connecting to? What’s your primary use case for these connections? (access to specific cloud services, redundancy, cost optimization, etc.) Feel free to share any challenges you've faced too!
