Link Checker Report #161
Description
Summary
| Status | Count |
|---|---|
| 🔍 Total | 256 |
| ✅ Successful | 225 |
| ⏳ Timeouts | 1 |
| 🔀 Redirected | 0 |
| 👻 Excluded | 0 |
| ❓ Unknown | 0 |
| 🚫 Errors | 30 |
Errors per input
Errors in README.md
- https://chaosengineering.news/: Timeout (status code: TIMEOUT)
- https://dl.acm.org/citation.cfm?id=3177123.3158134: Failed: Network error (status code: 403)
- https://medium.com/chaosiq/cloud-native-and-chaos-engineering-20842ee2fa8a: Failed: Network error (status code: 429)
- https://tinyletter.com/production-ready: Failed: Network error (status code: ERR)
- https://medium.com/netflix-techblog/the-netflix-simian-army-16e57fbab116: Failed: Network error (status code: 429)
- https://medium.com/@adhorn/chaos-engineering-ab0cc9fbd12a: Failed: Network error (status code: 429)
- https://dl.acm.org/citation.cfm?id=2723711: Failed: Network error (status code: 403)
- https://medium.com/chaosiq/exploring-multi-level-weaknesses-using-automated-chaos-experiments-aa30f0605ce: Failed: Network error (status code: ERR)
- https://medium.com/netflix-techblog/fit-failure-injection-testing-35d8e2a9bb2: Failed: Network error (status code: 429)
- https://www.youtube.com/watch?v=FCZVAZaXIjs: Failed: Network error (status code: 404)
- https://slack.litmuschaos.io/: Failed: Network error (status code: ERR)
- https://people.ucsc.edu/~palvaro/fit-ldfi.pdf: Failed: Network error (status code: ERR)
- https://medium.com/@njones_18523/chaos-engineering-traps-e3486c526059: Failed: Network error (status code: 429)
- https://medium.com/@run2obtain/from-resilience-to-dependability-security-chaos-engineering-for-cloud-services-9c6d6d152ed2: Failed: Network error (status code: 429)
- https://blog.twitter.com/engineering/en_us/a/2015/how-we-break-things-at-twitter-failure-testing.html: Failed: Network error (status code: 403)
- http://csel.org.ohio-state.edu/ResilienceEngineering.html: Failed: Network error (status code: 403)
- https://www.researchgate.net/publication/335922038_Security_Chaos_Engineering_for_Cloud_Services: Failed: Network error (status code: 403)
- https://medium.com/chaosiq/improve-your-cloud-native-devops-flow-with-chaos-engineering-dc32836c2d9a: Failed: Network error (status code: 429)
- https://medium.com/@NetflixTechBlog: Failed: Network error (status code: 429)
- https://proofdock.io/: Failed: Network error (status code: ERR)
- https://medium.com/netflix-techblog/automated-failure-testing-86c1b8bc841f: Failed: Network error (status code: 429)
- https://blog.loadmill.com/run-chaos-experiments-without-risking-your-job-2c8a5f4b0bfc: Failed: Network error (status code: 429)
- https://chaosconf.splashthat.com/: Failed: Network error (status code: 403)
- http://jm.taobao.org/2017/06/22/20170622/: Failed: Network error (status code: 404)
- https://www.rsaconference.com/industry-topics/webcast/35-new-paradigms-for-the-next-era-of-security: Failed: Network error (status code: 403)
- https://join.chaostoolkit.org/: Failed: Network error (status code: ERR)
- https://vmware.github.io/mangle/: Failed: Network error (status code: 404)
- https://www.katacoda.com/chaostoolkit/courses/01-chaostoolkit-getting-started: Failed: Network error (status code: 404)
- https://www.infoworld.com/article/3268017/devops/3-key-steps-for-running-chaos-engineering-experiments.html: Failed: Network error (status code: 404)
- https://www.verica.io/: Failed: Network error (status code: ERR)
- https://medium.com/@bbideep/why-should-chaos-be-part-of-your-distributed-systems-engineering-5bcb21497660: Failed: Network error (status code: 429)