Ask ngrok
Questions
The short ones are here. For anything else, ask below.
Yes. It's at status.ngrok.com.
Yes, and ngrok doesn't charge it. It's an abuse control. Add a credit or debit card in your account settings and TCP endpoints unlock. Prepaid cards don't count, and removing the card locks TCP endpoints again.
No. Some antivirus tools flag ngrok because bad actors also use it, and ngrok works with those vendors to fix the classification. Download the agent from ngrok.com and check that ngrok signed the binary. The docs FAQ shows how to verify a signature.
Yes. Every endpoint sits behind ngrok's firewall, and Traffic Policy adds rate limits and IP restrictions on top. The DDoS protection page lists the extra measures.
No. HTTP endpoints listen on port 80, and HTTPS and TLS endpoints on port 443. A TCP endpoint uses the port ngrok assigned with its TCP address.
Yes. When you switch Wi-Fi or your IP changes, the agent notices and reconnects on its own.
The Terms of Service and the Data Processing Agreement spell it out.
Yes. Serve the CORS headers from your app, or add them at the edge with the add-headers Traffic Policy action. With an auth action in front, it blocks preflight requests by default, so add an expression that skips auth for them. The docs FAQ has the details.
The open source 1.x agent is still on GitHub, but nobody maintains it. Download the current agent instead.
en-grok.
The first commit landed on March 20, 2013.
They want a persistent, secure connection between their network and yours, so they can reach a service you run. The end customer guide covers how to install the agent and lock it down.
Answers come from the ngrok docs and can be wrong. Check the linked pages before you rely on one.