General
92 results found
-
SSL notifications recipients
SSL and domain expiration notifications recipients should be adjustable like the other checks too.
3 votes -
Capability to check UDP's ports, for services with just an udp port
For some services we have only a UDP port to check, just tcp is aviable at this moment.
3 votesIndeed that's an idea but unfortunately there's no notion of "connection" for UDP so it's not possible to know if a port is filtered or if a service is simply not responding because it waits for a specific message for example. There is just one obvious case when the port is "officially" closed and so a response is sent to tell you that. Which kind of service would you like to monitor? would it require to send a specific packet? would it need to check for a response? Is just knowing that no response is received (not knowing if it's filtered or open) enough for your use-case?
-
Read-only REST API keys per check
I would like to be able to generate read-only API keys per check, so I would be able to use the API to directly show information within customers sites (WordPress Dashboard).
6 votesThanks for the suggestion, this is something which have been asked a couple times in the past and is under review for the roadmap.
Quick question: if this is for website which have a public status page, how would you feel about a public (no api key) read-only API for them?
Or do you prefer one read-only API key per check?
-
Private URL monitoring
The ability to monitor private endpoints e.g. internal VPN connections would be a great feature for us. I imagine it would have to be a small agent/executable that reports to the API (?)
7 votes -
Accepting Bank Redirect (Bancontact, EPS, FPX, giropay, iDEAL, P24, Sofort)
Stripe offers an integration with some EU Bank Redirect solutions: https://stripe.com/docs/payments/bank-redirects
These do no support off-session charges though, which means no auto-renew, each payment has to be made manually. I create this suggestion to poll the interest in these. If you would like to be able to use one of these, please vote and let me know which one.
See also: https://updown.uservoice.com/forums/177972-general/suggestions/44091768-accepting-sepa-direct-debit
2 votes -
Add African Location
It would be awesome to have a server in Africa so that updown.io would cover every continent on this planet.
10 votes -
Accepting Direct Debit (SEPA, BECS, Bacs, Pre-authorized debit in Canada)
Stripe supports some Direct Debit solutions:
https://stripe.com/docs/payments/bank-debitsWhich means you provide your account details and updown can charge it automatically (so this method would support auto-renewal like with cards).
I create this suggestion to poll the interest in this solution. Keep in mind it is already possible to pay by SEPA Transfer (where you manually send money to our IBAN) by contacting me. So this suggestion is only for people who would prefer an automatic charge on their account.
1 vote -
Integration with status.io
Provide integration with status.io, so your status page is updated automatically when updown detects an issue.
As a data point, status.io is another well known "status page" provider. They're actively developed (unlike Atlassian StatusPage these days), and used by a lot of places.
1 vote -
JSON version of the status page
Having a JSON version of the status page allows any possible integration with 3rd party tools/dashboards. Lowers the amount of API requests required to get similar content (even though I think not all of the information that is currently visible on the status page is also available using the existing API). Probably you want to put it behind the API key except maybe for public status pages.
14 votes -
DNS record checks
Hi,
I have implemented a simple php script on one of my servers to take a query via GET method and returns the requested DNS record.
The site is restricted to updown.io servers and uses a URL in the following format :https://webserver.com/lookup.php?T=A&D=google.co.uk&R=IP
This uses the following fields :
T - Type of record to return eg. MX/A/TXT
D - Domain to check eg. google.co.uk
R - Record field to return. eg. ip for ip address
The server code simple checks if the record type is a valid one we accept, checks the domain name is in a valid format…16 votesThanks for the suggestion, I’ve just merged this with another one about DNS check. This is something we’re thinking about but is not planned yet.
In the meantime what you made is a great workaround, if other users are interested I encourage them to leave a comment here with a way to contact them so you may give them the URL of your service if you want.
-
Grafana plugin
This has been suggested by a client so I created the suggestion to gather interest:
It would be great to see an updown plugin in Grafana, From what I know from grafana you would need to create some API endpoints for data output and then use it as data source and configure some demo dashboard's, here is example I found https://grafana.com/grafana/plugins/raintank-worldping-app
3 votes -
Full white label functionality
I want to be able to white label status pages, email alerts, etc. (total white label possibilities)
3 votes -
Show Total Time on dashboard
I like to see the Total Time from the last 24 hours (so REDIRECTIONS + NAME LOOKUP + CONNECTION + TLS HANDSHAKE + RESPONSE TIME) on the dashboard.
Would be very nice to not only see the Apdex, but also the Total Time for all websites at one overview page.
7 votes -
Allow Green Status when using letsencrypt staging CA
In dev environments is common to use the letsencrypt staging CA rather than the production one .
This CA does not verify using the standard system ca store.
Would be useful to allow marking the letsencrypt staging ca as allowed on a per check basis
1 vote -
Finetune the SSL expiration alert period
Right now, Let's Encrypt certificate expiration alert is sent 14 days, 7 days, 1 day before.
I have a certbot that renews it 5 days before.
So every month, I receive alerts 14 days and 7 days for all domains,
which are perfectly normal. Hence, some 'alert noise' that I don't take into account anymore...Suggestion:
Let us select a custom period for SSL expiration dates.
I think globally, with 2 different settings: one for "standard" certificate, the other for 'let's encrypt' certificates.--> only alert when worth alerting :)
--> smarter monitoring8 votesHello,
Actually 14, 7, 1 is already the special schedule for let’s encrypt certificates. This is automatically detected by updown.io so you don’t have to, normal 1-year certificates get an additional 30 days reminder.
The threshold for let’s encrypt certs starts at 14 days because the default renew delay is 30 days before expiration: https://certbot.eff.org/docs/using.html. This can be down to 23 days with a weekly cron for example (pretty common) so that’s why we chose 14 days, so you have plenty of time to renew but still have time to investigate and fix any potential auto-renew issues.
If you’d rather renew your cert only 5 days before expiration that’s up to you but we won’t recommend or support this configuration as we consider it dangerous ☺
I’ll mark this suggestion as “Under Review” to measure the need for this.
-
Break down the time taken by redirects since they're often a key part of the user experience
Currently updown.io breaks out the time of normal requests into:
- name lookup;
- connection;
- tls handshake; and
- response time
but shows redirects as a single block of time. It would be useful to see redirects broken out the same way.
Users often type naked domains, like example.com, into browsers. That might lead to this sequence of redirects:
http://example.com/ -> https://example.com https://example.com/ -> https://www.example.com(HSTS preload requires the first redirect; you can't go straight from http://example.com/ to https://www.example.com.)
Depending on how you're handling both http and naked domains the time for the redirects can be much greater than the time of…
11 votes -
Test based on hash
It would be handy if instead of content we could choose to hash the response and test if the response matches the hash.
1 vote -
South America checkpoint
Hello, I suggest that a South American checkpoint is a priority. I have (among others) websites in Spanish and Portuguese, and although Spain and Portugal are in Europe, the majority of users in these languages turn out to be from South America. If you need a VPS in Brazil, I can recommend Virtuaserver (I had a good experience with them), or there are many others. Best wishes and keep going.
34 votes -
Add Belgium location
Add more server locations ( in particular Belgium)
7 votes -
servers in hong kong and indonesia
servers in hong kong and indonesia
2 votes
- Don't see your idea?