Link Checker Report

[github-actions]

Summary

Status	Count
🔍 Total	489
✅ Successful	368
⏳ Timeouts	3
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	118

Errors per input

Errors in README.md

• https://devops.com/site-reliability-engineering-sre-true-ops-devops/: Failed: Network error (status code: 403)
• https://queue.acm.org/detail.cfm?id=3178371: Failed: Network error (status code: 403)
• https://rachelbythebay.com/w/: Timeout (status code: TIMEOUT)
• https://dastergon.gr/awesome-sre: Failed: Network error (status code: 404)
• https://devops.com/three-ways-to-minimize-the-impact-of-high-severity-incidents/: Failed: Network error (status code: 403)
• https://medium.com/swlh/the-ultimate-guide-to-structuring-a-90-day-onboarding-plan-c91af947376: Failed: Network error (status code: 403)
• https://blog.netsil.com/the-4-golden-signals-of-api-health-and-performance-in-cloud-native-applications-a6e87526e74: Failed: Network error (status code: ERR)
• https://honeycomb.io/blog/2017/01/instrumentation-what-does-uptime-mean/: Failed: Network error (status code: 404)
• https://devblog.xero.com/sre-xero-managing-incidents-part-ii-224a6e06f426: Failed: Network error (status code: ERR)
• https://queue.acm.org/detail.cfm?id=2891413: Failed: Network error (status code: 403)
• https://dzone.com/articles/the-cloudcast-301-sre-and-infrastructure-operation: Failed: Network error (status code: 403)
• https://medium.com/@jerub/sre-consensus-building-36ad5d2e470b: Failed: Network error (status code: 403)
• https://www.packtpub.com/web-development/real-world-sre: Failed: Network error (status code: 404)
• https://honeycomb.io/blog/2017/01/instrumentation-worst-case-performance-matters/: Failed: Network error (status code: 404)
• https://www.honeycomb.io/usecase/o11ycast/: Failed: Network error (status code: 404)
• https://medium.com/dm03514-tech-blog/sre-performance-analysis-tuning-methodology-using-a-simple-http-webserver-in-go-d475460f27ca: Failed: Network error (status code: 403)
• https://www.verica.io/blog/inhumanity-of-root-cause-analysis/: Failed: Network error (status code: ERR)
• https://medium.com/@allspaw/social-issues-in-postmortems-d48dde624d18: Failed: Network error (status code: 403)
• https://www.sidewalksafari.com/2018/12/sre-in-a-travel-emergency.html: Failed: Network error (status code: 404)
• https://www.inc.com/justin-bariso/meet-postmortem-googles-brilliant-process-tool-for-learning-from-failure.html: Failed: Network error (status code: 403)
• https://blogs.vmware.com/services-education-insights/2018/02/site-reliability-engineering.html: Failed: Network error (status code: 404)
• https://medium.com/@mattklein123/the-human-scalability-of-devops-e36c37d3db6a: Failed: Network error (status code: 403)
• http://www.networkworld.com/article/3182827/cloud-computing/srecon17-brave-new-world-of-site-reliability-engineering.html: Failed: Network error (status code: 404)
• http://www.wired.com/insights/2011/12/service-level-agreements-in-the-cloud-who-cares/: Failed: Network error (status code: 404)
• https://medium.com/observability/debugging-latency-in-go-1-11-9f97a7910d68: Failed: Network error (status code: 403)
• https://medium.com/expedia-group-tech/error-budget-policies-in-practice-4c98f56a28c1: Failed: Network error (status code: 403)
• https://www.loomsystems.com/single-post/2016/03/23/So-you-want-to-be-a-Site-Reliability-Engineer: Failed: Network error (status code: ERR)
• https://medium.com/expedia-group-tech/error-budget-policy-adoption-at-expedia-group-7d80d41c4a8b: Failed: Network error (status code: 403)
• https://www.rootly.io/blog: Failed: Network error (status code: 403)
• https://medium.com/site-reliability-engineering-leadership/sli-deep-dive-cae92bd90a79: Failed: Network error (status code: 403)
• http://queue.acm.org/detail.cfm?id=2839461: Failed: Network error (status code: 403)
• http://queue.acm.org/detail.cfm?id=2745840: Failed: Network error (status code: 403)
• https://medium.com/booking-com-infrastructure/incidents-fixes-and-the-day-after-c5d9aeae28c3: Failed: Network error (status code: 403)
• https://medium.com/@rakyll/the-sre-model-6e19376ef986: Failed: Network error (status code: 403)
• https://queue.acm.org/detail.cfm?id=3096459&__s=dnkxuaws9pogqdnxmx8i: Failed: Network error (status code: 403)
• https://devops.com/sre-devops-cloud-native-server-cage-match/: Failed: Network error (status code: 403)
• https://medium.com/@NetflixTechBlog/tips-for-high-availability-be0472f2599c: Failed: Network error (status code: 403)
• https://twitter.com/SREBook: Failed: Network error (status code: 403)
• https://twitter.com/usenix: Failed: Network error (status code: 403)
• https://github.com/fhivemind/sre-playground: Failed: Network error (status code: 404)
• https://blog.box.com/blog/a-tale-of-postmortems/: Failed: Network error (status code: 403)
• https://medium.com/google-cloud/production-guideline-9d5d10c8f1e: Failed: Network error (status code: 403)
• https://queue.acm.org/detail.cfm?id=3283589: Failed: Network error (status code: 403)
• https://medium.com/@jerub/hope-is-not-a-strategy-6a7d0a3b1c08: Failed: Network error (status code: 403)
• https://medium.com/@tammybutow/graduating-from-bootcamp-and-interested-in-becoming-a-site-reliability-engineer-b69a38ce858b: Failed: Network error (status code: 403)
• https://dubrie.medium.com/sre-cultural-values-a0073b475183: Failed: Network error (status code: 403)
• https://medium.com/the-telegraph-engineering/putting-customers-first-with-slis-and-slos-15352f9b6cbc: Failed: Network error (status code: 403)
• https://chaosengineering.news/: Timeout (status code: TIMEOUT)
• https://devops.com/code-yellow-when-operations-isnt-perfect/: Failed: Network error (status code: 403)
• https://twitter.com/SREcon: Failed: Network error (status code: 403)
• https://medium.com/better-programming/site-reliability-engineering-best-practices-for-data-pipelines-44a78e91f6f0: Failed: Network error (status code: 403)
• https://dastergon.gr/wheel-of-misfortune/: Failed: Network error (status code: 404)
• https://medium.com/@jerub/the-production-environment-at-google-part-2-610884268aaa: Failed: Network error (status code: 403)
• https://medium.com/back-market-engineering/how-back-market-sres-prepared-for-black-friday-5f017f343408: Failed: Network error (status code: 403)
• https://medium.com/@dlite/observability-the-new-wave-or-buzzword-fc23a68abf72: Failed: Network error (status code: 403)
• https://community.atlassian.com/t5/Jira-Ops-questions/I-m-John-Allspaw-Ask-Me-Anything-about-incident-analysis-and/qaq-p/957084: Failed: Network error (status code: ERR)
• https://dastergon.gr/error-budget-calculator/: Failed: Network error (status code: 404)
• https://www.weave.works/blog/gitops-part-3-observability: Failed: Network error (status code: 404)
• https://codeascraft.com/2012/05/22/blameless-postmortems/: Failed: Network error (status code: 403)
• https://blog.twitter.com/2015/how-we-break-things-at-twitter-failure-testing: Failed: Network error (status code: 403)
• https://medium.com/@venkatachalamrangasamy/site-reliability-engineering-demystified-ed676e0a7d56: Failed: Network error (status code: 403)
• https://twitter.com/TwitterSRE: Failed: Network error (status code: 403)
• https://twitter.com/SREWeekly: Failed: Network error (status code: 403)
• https://honeycomb.io/blog/2018/02/oncall-and-sustainable-software-development/: Failed: Network error (status code: 404)
• https://codeascraft.com/2016/11/17/debriefing-facilitation-guide/: Failed: Network error (status code: 403)
• https://queue.acm.org/detail.cfm?id=3028689: Failed: Network error (status code: 403)
• https://ai.google/research/pubs/pub45906: Failed: Network error (status code: 404)
• https://danrl.com/blog/srm: Failed: Network error (status code: ERR)
• https://devblog.xero.com/sre-xero-managing-incidents-part-i-7d02d650a71c: Failed: Network error (status code: ERR)
• https://medium.com/@copyconstruct: Failed: Network error (status code: 403)
• https://medium.com/@copyconstruct/on-call-b0bd8c5ea4e0: Failed: Network error (status code: 403)
• https://www.verica.io/inhumanity-of-root-cause-analysis/: Failed: Network error (status code: ERR)
• https://podcasts.apple.com/us/podcast/resilience-in-action/id1506828506: Failed: Network error (status code: 404)
• https://medium.com/@kobolog/sre-noun-see-also-confidence-trust-e7e33e19efc1: Failed: Network error (status code: 403)
• https://medium.com/@copyconstruct/monitoring-in-the-time-of-cloud-native-c87c7a5bfa3e: Failed: Network error (status code: 403)
• https://medium.com/google-cloud/measuring-reliability-in-gcp-step-by-step-slo-creation-guide-using-cloud-operation-sandbox-99043bd0e70f: Failed: Network error (status code: 403)
• https://www.youtube.com/watch?v=bwt6TZjefGM: Failed: Network error (status code: 404)
• https://www.youtube.com/watch?v=bC5dIPzNH24: Failed: Network error (status code: 404)
• https://ai.google/research/pubs/pub48033: Failed: Network error (status code: 404)
• https://medium.com/@awspyker/why-as-a-netflix-infrastructure-manager-am-i-on-call-bdc551ac01fe: Failed: Network error (status code: 403)
• https://medium.com/@jerub/service-level-objectives-in-practice-ed1200502d5: Failed: Network error (status code: 403)
• https://medium.com/@jerub/the-production-environment-at-google-8a1aaece3767: Failed: Network error (status code: 403)
• https://twitter.com/SREWorkbook: Failed: Network error (status code: 403)
• https://twitter.com/googlesre: Failed: Network error (status code: 403)
• https://medium.com/site-reliability-engineering-leadership/sre-tip-have-tiered-slas-2c432ffe46a: Failed: Network error (status code: 403)
• https://www.loomsystems.com/blog/2017/02/06/spiraling-ops-debt-the-sre-coding-imperative: Failed: Network error (status code: ERR)
• https://queue.acm.org/detail.cfm?id=2655736: Failed: Network error (status code: 403)
• https://blog.twitter.com/2014/push-our-limits-reliability-testing-at-twitter: Failed: Network error (status code: 403)
• https://cloud.google.com/blog/big-data/2016/10/a-google-sre-explores-github-reliability-with-bigquery: Failed: Network error (status code: 404)
• https://blog.netsil.com/beyond-google-sre-what-is-site-reliability-engineering-like-at-medium-71c65bd35f4e: Failed: Network error (status code: ERR)
• https://medium.com/concourse-ci/earning-our-wings-a0c307fa73e6: Failed: Network error (status code: 403)
• https://blog.twitter.com/2017/the-infrastructure-behind-twitter-scale: Failed: Network error (status code: 403)
• https://www.reddit.com/r/IAmA/comments/1w1y5m/we_are_the_google_site_reliability_engineering/: Failed: Network error (status code: 403)
• https://blog.netsil.com/microservices-devops-and-operational-complexity-be98cb01b660: Failed: Network error (status code: ERR)
• https://alexewerlof.medium.com/calculating-composite-sla-d855eaf2c655: Failed: Network error (status code: 403)
• https://medium.com/@jerub/monitoring-your-monitorings-monitoring-51d479100f4c: Failed: Network error (status code: 403)
• https://medium.com/@bellmar/sre-as-a-lifestyle-choice-de9f5a82d73d: Failed: Network error (status code: 403)
• http://googleresearch.blogspot.gr/2012/07/site-reliability-engineers-solving-most.html: Failed: Network error (status code: ERR)
• http://queue.acm.org/detail.cfm?ref=rss&id=2889274: Failed: Network error (status code: 403)
• https://queue.acm.org/detail.cfm?id=3194655: Failed: Network error (status code: 403)
• https://medium.com/@Knowlarity_Engineering/how-a-cat-inspired-system-reliability-at-knowlarity-ad73c24f29a7: Failed: Network error (status code: 403)
• https://medium.com/devopslinks/how-to-monitor-the-sre-golden-signals-1391cadc7524: Failed: Network error (status code: 403)
• https://medium.com/observability/want-to-debug-latency-7aa48ecbe8f7: Failed: Network error (status code: 403)
• http://queue.acm.org/detail.cfm?id=2371516: Failed: Network error (status code: 403)
• https://www.socallinuxexpo.org/sites/default/files/presentations/Scale%20x14%20Slides.pdf: Failed: Network error (status code: 404)
• https://queue.acm.org/detail.cfm?id=2371297: Failed: Network error (status code: 403)
• https://www.reddit.com/r/IAmA/comments/177267/we_are_the_google_site_reliability_team_we_make: Failed: Network error (status code: 403)
• https://medium.com/@jerub/tenets-of-sre-8af6238ae8a8: Failed: Network error (status code: 403)
• https://tech.buzzfeed.com/checklists-an-operational-gift-aaf42cf0be12: Failed: Network error (status code: ERR)
• https://www.verica.io/top-seven-myths-of-robust-systems/: Failed: Network error (status code: ERR)
• https://devops.com/sres-the-happiest-and-highest-paid-in-the-industry/: Failed: Network error (status code: 403)
• https://www.transposit.com/blog/2020.01.30-writing-runbook-documentation-when-youre-an-sre/: Failed: Network error (status code: 404)
• https://medium.com/@jerub/commentary-on-site-reliability-engineering-9ba9e1be2a8c: Failed: Network error (status code: 403)
• https://blog.twitter.com/2016/the-infrastructure-behind-twitter-efficiency-and-optimization: Failed: Network error (status code: 403)
• https://twitter.com/The_SRE_Dev: Failed: Network error (status code: 403)
• https://medium.com/@jerub: Failed: Network error (status code: 403)
• https://doordash.engineering/2022/04/25/using-fault-injection-testing-to-improve-doordash-reliability/: Failed: Network error (status code: 403)
• http://engineering.medallia.com/blog/posts/understanding-site-reliability-engineering-through-movies-and-books/: Failed: Network error (status code: ERR)
• https://medium.com/@jamesacowling/how-many-nines-is-my-storage-system-7d16e852d56d: Failed: Network error (status code: 403)
• https://www.verizondigitalmedia.com/e-book/oreilly-what-is-sre/: Timeout (status code: TIMEOUT)
• https://medium.com/lightstephq/what-made-slos-so-messy-and-what-we-can-do-about-it-89be415a80b3: Failed: Network error (status code: 403)

Full Github Actions output