StatusStack

See the latest statuses of your app's most critical services, all in one place.

[StatusStack @Status_Stack]

https://t.co/F3NWM1DshA vs Better Stack: one runs incidents in Slack/Teams on top of your existing monitoring, the other bundles monitoring, on-call and status pages. We compared features, pricing and fit. https://t.co/qhnXsw9OnL

[StatusStack @Status_Stack]

Update: Google Cloud's Oct 20 europe-west2 (London) disruption is resolved. Google attributed it to a power event in zone europe-west2-b; impact ran about 7h52m (2:08am to 10:00am ET). Recap updated: https://t.co/aWc0WO7t3Q

[StatusStack @Status_Stack]

GitHub had two critical incidents on Oct 7 affecting Git operations, pull requests and Actions. The second was a recurrence of the first. Both are resolved, and no root cause has been published yet. Recap and timeline: https://t.co/erxkaNbfkx

[StatusStack @Status_Stack]

Google Cloud's London region (europe-west2) has been disrupted since 2:08 a.m. ET, with 37 products affected and Hostinger, MongoDB Atlas, JFrog and CloudAMQP reporting impact. Google hasn't published a cause yet. Our running recap: https://t.co/aWc0WO7t3Q

[StatusStack @Status_Stack]

Google Cloud Storage in us-central1 had about 11 hours of elevated upload/write errors and latency on Oct 8, from 8:19am to 7:30pm ET. Google's first public update came about 6 hours after the start, and no root cause has been published. Recap: https://t.co/BGZywJjr3j

[StatusStack @Status_Stack]

How to build a vendor dependency stack: tier critical vs important vendors, pick the first 10–50 to monitor, map blast radius, and alert without spam.

https://t.co/FXkBKar4WD

[StatusStack @Status_Stack]

GitHub posted the RCA for the Oct 5 Actions hosted-runner delays. We updated our recap with their findings.

https://t.co/FQTCjBHFDC

[StatusStack @Status_Stack]

Update: GitHub has resolved today's Actions incident. Hosted runners were back by 5:54pm ET, and the incident closed at 6:49pm ET, about 3.5 hours after it started. Root cause analysis is still pending.
https://t.co/FQTCjBHFDC

[StatusStack @Status_Stack]

GitHub Actions is in a major outage. Since 3:11pm ET, GitHub has reported delays assigning hosted runners, and some jobs are failing. As of 5:09pm ET, repo list, licensing, and billing pages are also affected. The incident is still under investigation.
https://t.co/FQTCjBHFDC

[StatusStack @Status_Stack]

Need budget for vendor monitoring? Lead with the cost of the problem: vendor-caused incidents, hours spent diagnosing them, and what that time costs. The guide includes an ROI template and a one-page summary for your manager.
https://t.co/h79pOpFoE2

[StatusStack @Status_Stack]

New tooling fails when rollout is rushed. Week-by-week StatusStack adoption: map dependencies by tier, route alerts by severity, put a vendor-status check at the top of every runbook.
https://t.co/JU0qsVl76V

[StatusStack @Status_Stack]

Claude elevated errors hit https://t.co/KsUa1xlbWq, Claude Code, Cowork, and the API on Sep 29. Anthropic lists ~59 min impact (10:00–10:59 a.m. ET); resolved 12:27 p.m. ET. Recap: https://t.co/B6OFp8nCvO

[StatusStack @Status_Stack]

OpenAI is monitoring recovery after elevated errors hit ChatGPT, Codex, and the API this afternoon (started ~1:52 p.m. ET; mitigation ~3:39 p.m. ET). Recap: https://t.co/cvaYzulWub

[StatusStack @Status_Stack]

Vendor SLA credits usually die in spreadsheets. How to automate tracking from historical incident data — without more manual export nights.
https://t.co/7DfOxVeIup

[StatusStack @Status_Stack]

https://t.co/GEYjLonVr4: service disruption with 503s starting ~7:02pm ET. Identified and mitigating; API hit too; some recovery ~7:44pm. Still Identified, not Resolved.
https://t.co/u5jnKLAoXA

[StatusStack @Status_Stack]

Wikimedia: critical service disruption Wed ~1:26pm ET after a power failure and DC failover. Reading/Editing recovered; incident still Monitoring.
https://t.co/B24NVmkWH5

[StatusStack @Status_Stack]

Confluent Cloud Console / AWS us-west-2 issues on Sep 21 are resolved. Start 11:26 a.m. ET; monitoring 8:40 p.m.; Resolved 9:31 p.m. ET. Kafka produce/consume not impacted.
https://t.co/FYC6dmX4yD

[StatusStack @Status_Stack]

Facebook and Instagram had a concurrent disruption Sep 20 evening. DownDetector peaks ~17,600 Facebook / ~5,600 Instagram around 9:15 p.m. ET. Recap: https://t.co/w4ByW1IUwf

[StatusStack @Status_Stack]

8x8 Admin Console and Work Web issues on Sep 21 are resolved. Impact ~8:47 a.m.–4:43 p.m. ET (~7h 56m) in Americas and EMEA. RCA underway.
https://t.co/qlWNYWmGxx

[StatusStack @Status_Stack]

SAP Concur US2 disruption on Sep 21 is resolved. Impact ~1:48–2:30 p.m. ET on Expense, Travel, Invoice, Request, and Analysis/Intelligence (sign-in/unavailable and HTTP 500 errors). Fix: DB server-tier config change.
https://t.co/QY5v1LgtCj