Is Buildkite down?
Check the source. Compare experiences. Add your signal.
Checking provider
We collect the provider’s public feed and show the last successful collection time.
Open official source ↗Loading reports…
Reports describe individual experiences. They do not independently confirm a provider outage or count everyone affected.
Buildkite reports over the last 24 hours
Loading the reporting timeline…
Latest provider updates
Open incidents, information updates and advisories, with original source links.
Loading provider updates…
Troubleshooting Buildkite
People may look up Buildkite for API requests, authentication, deployments, storage, regional connectivity and developer dashboards. Choose the closest symptom when reporting.
- Match any Buildkite provider advisory to the product and region you actually use.
- Distinguish an overall platform signal from a product-specific incident.
- Keep credentials and customer data out of reports and support screenshots.
Read the complete troubleshooting guide →
How is Buildkite status determined?
We collect the provider’s public feed and show the last successful collection time.
What does “operational” tell me?
A provider reading covers the scope of its published feed. It can miss a local, account-specific, newly developing or regional issue. A failed collection is shown as unverified, not as an outage.
Can I report without signing up?
Yes. Choose the service, symptom and country. Device location is optional and rounded before submission. Reports are shown in aggregate, and repeated reports are rate limited.
Are provider incidents the same as user reports?
No. Provider updates link to the original source. Community reports record experiences submitted here. They are displayed separately to help you assess both.
SignalPier is independent and is not affiliated with Buildkite. Service names identify the products being discussed.