Forum Widgets
The Data Center is Evolving - Are You?
Times moves fast...don't they? As the line between public and private cloud continues to blur, we're seeing the very definition of "data center" evolve right alongside it. Colocation, edge, interconnection - these aren't just technologies anymore. They're becoming foundational building blocks in how hybrid cloud actually operates today. We used to think of hybrid as static: pair a hyperscaler with some on-prem gear and bada-bing, bada-boom, call it a day...right? Wrong. That model no longer cuts it. Now, we're watching new hybrid patterns emerge that are more agile, distributed, and value-driven. Let's face it, it's no longer about where the workloads are - it's about how infrastructure adapts to optimize performance, cost, and connectivity in real-time. What are you seeing in your markets? Are you rethinking their hybrid strategies through the lens of colocation and interconnection? Are edge facilities shifting the center of gravity? Would love to hear your take - what are your thoughts?Optimal by Design: Architecting for Hybrid from Day One in AI and Application Development
For every new AI or application project you embark on, your initial architectural choices will determine the probability of long-term success of that effort, especially as it scales or needs to adapt to changing regulatory or business environments. This article discusses why architecting for hybrid up front puts you in the optimal position for anything that comes your way. https://blog.equinix.com/blog/2025/05/21/why-you-need-a-hybrid-first-strategy/ Do you agree? Is 'hybrid-first' truly the silver bullet for future-proofing, or are there scenarios where a pure cloud or colo/on-prem approach still makes sense? Share your perspective!
Equinix Internet Access - additional IPs
Hi team, When ordering Internet Access over fabric for a redundant connection type, how many sets of additional IPs are provided? For example is it just one set of additional IPs anywhere between /30 to /24? Or as it's a redundant pair do we get two sets of additional IPs e.g. additional IP range 1: anything from /30 to /24 additional IP range 2: anything from /30 to /24 Thanks
Inconsistent monetary information for Japan via Billing v2 API
Hi, we have a presence in different Equinix data centers and retrieve billing information via the Billing v2 API. We observed that the information we obtain for the Japan invoice (and that one only) has inconsistent (dare I say wrong?) tax amount values across time: For invoices from 2024-02 (oldest I have) until 2024-05 (which is not downloadable anymore due to the 12 month limit but I have a local copy) the Japanese line items behave exactly like all others we can observe, namely: non-zero taxAmount (10% of recurringAmount) and recurringAmount + taxAmount = totalAmount. For invoices from 2024-06 until 2024-08 (both in the snapshot I had from a few months ago and the one I just took now) the Japanese line items now still has a non-zero taxAmount (10% of recurringAmount) but totalAmount = recurringAmount. Checking a few entries we saw that the netAmount is the same as in previous entries which makes me assume that the totalAmount does not include any tax amount. For invoices from 2024-09 onward the Japanese line items now all have taxAmount = 0 and totalAmount = recurringAmount. This means that we are unable to obtain any tax information from the invoice other than assuming that the 10% applies to all line items. Furthermore, this data is inconsistent with the reality that there is tax to be paid. Could you explain why the data is so inconsistent, changing multiple times withing a few months? Could you also explain why the data for invoices since 2024-06 is inconsistent with the reality? Is there any resource where changes in the API are documented and where I could have learned about these changes? What can we expect moving forward? Should we expect the data to change again, hopefully to be correct again as it was pre 2024-06? Thanks JonasBilling v2 API deprecation?
Hello, today I noticed that on the API documentation overview page it says that the Billing_v2 API is Deprecated. I can't find any further information on that and also noticed that, in contrast to the WorkVists_v1 API which is marked in the same way, no deprecation information can be found on the actual documentation page. Would you be able to provide some more information on the deprecation or links to where I can find it? I'm especially interested in whether this API is actually going to be disabled in the future and if there's any alternative to obtain invoice information programmatically and machine-readable. Thanks, JonasUnderstanding Sustainable Energy in the Digital Age
Just read the latest Equinix blog post on powering a sustainable future! 🌱💡 Great insights into energy innovation for the digital era. Check it out here: https://blog.equinix.com/blog/2025/04/29/powering-a-sustainable-future-energy-innovation-for-the-digital-era/?country_selector=Global%20(EN)
