If an entry left you with questions, if you found an error in a configuration snippet, or if you want to propose a topic for the blog, this is the channel. Tell us which article you are referring to, in what environment you applied it, and what behavior you observed. The more specific the message, the easier it is for us to read it and place it within what we have already published about Kubernetes, Terraform, observability, message queues, or instance costs.
If you prefer to write directly, the editorial team's inbox is hello@buckinghamcloud.com. You can also call +54 11 4281-7054. The mailing address is Av. Corrientes 1235, Piso 12, Oficina 1204, Edificio Torre Corrientes, C1043 Buenos Aires, Argentina.
Before writing, check the blog tags: networking, storage, and CI/CD usually concentrate the most repeated questions. If your inquiry is about a configuration snippet, copy it exactly as you have it and add what output or error you are seeing. If it is a correction, indicate the entry and the exact paragraph. We do not promise response times or email confirmation: the form only leaves a record of your message in the processor.
If an entry left you with questions, if a configuration snippet doesn't fit your environment, or if you spotted an error in a comparison, this is the channel. It's also for suggesting topics we haven't covered yet: networking, storage, CI/CD, anything you're solving in production that's worth documenting. There's no subscription form or account creation here; just a message that reaches the editorial team.
Buckingham Cloud is published from Buenos Aires. The address below is postal only: it is used for correspondence and editorial matters, it is not a public customer service space or a visiting point. If your inquiry is about a published post, a configuration snippet, or a tool comparison, email and the contact form are the direct route.
Before writing, check whether the topic has already appeared on the blog. Kubernetes, Terraform, observability, message queues, instance costs, and legacy service migration all have their own posts. If your question is a specific correction, cite the section and the environment where you applied it: that saves back-and-forth.
The location marked on the map corresponds to the declared postal address. It does not imply an open office, reception of visitors, or customer service hours.
A useful message does not need to be long. It needs context. If you tell us which entry you are reading, in what environment you applied it, and what result you expected, reading the message becomes much simpler on the other side. This page is not a support channel with guaranteed response times or a sign-up form: it is the way to leave an editorial inquiry, a correction, or a topic suggestion about the blog.
You do not need to fill in everything. If something does not apply to your case, leave the field blank and continue. We prefer a message with half the details filled in correctly over one that is complete but generic.