Changed uptime badges to use Upptime #43
Conversation
Fixed! |
{{ message }}
Open
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@timvisee - The reliability of each Send instance is now tracked in this separate repository: https://github.com/tdulcet/send-instances-status. I sent you an e-mail last month with much more information. If it is OK with you, I can transfer this repository to you and then update the URLs in the PR accordingly.
@xbdmHQ - It looks like your Cloudflare "Bot Fight Mode" configuration is blocking the bot used to check the status of each Send instance. See https://github.com/tdulcet/send-instances-status/issues/34 for example. We obviously do not want your instance to be listed as down when it is not, so there is a possible workaround explained here: upptime/upptime#785. If this is not feasible for you, we could potentially continue to use Uptime Robot for your specific instance, although we would of course prefer to remove all uses of Uptime Robot if possible.