hook.io

Twitter account for open-source microservice hosting platform. Tweet here for Questions or Support. Live Chat:

[hook.io @hookdotio]

We've recently started to enforce the stated rate limits for all accounts. If you have any issues or questions about your account please let us know.

[hook.io @hookdotio]

@digitalocean We got an auto-responder email asking me to fill out a Google Form to register a Global Event Sponsorship with a start date / end date / location.

Any suggestions?

[hook.io @hookdotio]

Hey @digitalocean, is there any chance we could get an open-source sponsorship with some hosting credits? Our entire platform is 100% open-source and hosted on DO.

[hook.io @hookdotio]

@digitalocean Done, thank you!

[hook.io @hookdotio]

Due to increased demand our free plan now costs $2.00 per month and comes with a 60 day trial.

If you are running an open-source service on your current free plan please let us know in the next month and we'll make sure your services stay online.

[hook.io @hookdotio]

Updating our load balancers and web servers today to Node v10.15.3. Not expecting any downtime.

[hook.io @hookdotio]

Currently migrating our production databases to larger instances. Not expecting to have any downtime during the upgrade.

[hook.io @hookdotio]

We are still talking to @telegram support to restore bot services for users. It looks like Telegram has an aggressive retry policy for non 200 response codes which is causing problems with our rate limiting and error handling systems.

[hook.io @hookdotio]

Just had a minor unexpected service outage during some routine maintenance. CouchDB is now updated to latest version.

[hook.io @hookdotio]

We've just now blocked all incoming traffic originating from 149.154.167.0/24 ( @Telegram Bot API Servers ). Something is not right with their servers and we were getting flooded with requests. Telegram bots are now disabled on https://t.co/h1PFdwJhTq. Hopefully will get resolved

[hook.io @hookdotio]

We may have to drop support for @telegram Bots on our platform. Talking to their support now. They don't seem to have much in place to prevent a group of Telegram Bot webhook API users from being able to DDOS an arbitrary web host.

[hook.io @hookdotio]

@smstelegram @telegram Is there any status on this? We've had to start temporarily blocking IP addresses and traffic from https://t.co/SKBBQ8SKzJ. Please let us know.

[hook.io @hookdotio]

@telegram We are seeing a lot of repeated HTTP requests per second from IP addresses originating from https://t.co/SKBBQ8SKzJ. It's flooding us and looks like a lot of these are abandoned bots. Can you assist? We may have to block your entire IP range.

[hook.io @hookdotio]

@smstelegram Certainly. Thanks.

[hook.io @hookdotio]

We are experiencing record high usage in the past week. In order to free up system resources we'll be migrating some networking code from the application to iptables to improve overall performance and response times of platform.

[hook.io @hookdotio]

New core updates have been deployed and preliminary tests looking good! Will continue to test. Back to rolling deployments.

[hook.io @hookdotio]

Performing scheduled maintenance to update core services. Improving core capacities as well as many good user facing features. Stay tuned.

[hook.io @hookdotio]

Had to perform a quick migration to Lets Encrypt. SSL and all other services should be back online.

[hook.io @hookdotio]

SSL certificates seem to have unexpectedly expired. Working on a resolution now.

[hook.io @hookdotio]

We had to switch back to returning 200 status code on hook timeouts. This will fix issues for certain Telegram users seeing repeat requests.