API status

[djdembeck]

Before filing any issues, please first check the uptime/status of any endpoint you may be having trouble with:

https://status.audnex.us/

Incidents and downtimes can be reported in this issue.

[djdembeck]

Someone exploited a vulnerability on it again, probably from the host. This has happened before with this provider so I'll need to move it. Right now, I have other obligations for the next few hours.

In the meantime, the service is OFFLINE, with cached responses probably still working.

[Thanzex]

I couldn't hep but notice that the status page is down too.
I would suggest using an indipendent service/host to track the status of the API, there are even free soutions like https://github.com/upptime/upptime that make use of Github actions and pages, or other open source systems that can run on the free tier of services like fly.io.

May we know the name of the host so as to avoid it?

[djdembeck]

I think things have stabilized enough now to comment on this. Yes, our uptime monitoring is through the same company, with a very small VM running Uptime Kuma. I'll look into setting up upptime as well, looks like a neat project.

We use CapRover for it's PaaS simplicity for rapidly getting projects deployed on whatever hardware we want. Since the Audnexus API is not generating any kind of income, hosting needs to be performant while remaining very low cost.

We were using NextArray, which I already have colocation hosting through as well. It is a young company with growing pains, but the cost was unbeatable. Sadly you get what you pay for. The first time this happened at NextArray, the engineer said they are not responsible for security. This time they are supposed to be looking at the VM to confirm if it's a hypervisor leak.

I've since moved to an OVH VM. I trust them with my other production services so have no doubt they will not have the same issues.

[JaegerMaster]

Is the api down? I am getting the hoist down status.

[pkishino]

yeah,
this is current status when checking status page

Error 1000  Ray ID: 81758909b8fd528f • 2023-10-17 03:43:05 UTC
DNS points to prohibited IP
What happened?

You've requested a page on a website (status.audnex.us) that is on the [Cloudflare](https://www.cloudflare.com/5xx-error-landing/) network. Unfortunately, it is resolving to an IP address that is creating a conflict within Cloudflare's system.
What can I do?

If you are the owner of this website:
you should [login to Cloudflare](https://www.cloudflare.com/login?utm_source=error_100x) and change the DNS A records for status.audnex.us to resolve to a different IP address.

[djdembeck]

The host of the uptime monitor terminated service with 3 days notice. Haven't had time to set up another public monitor. The API is still up though.