InstaTunnel
instatunnel.my · Egress and tunnels · 1 record · JSON
InstaTunnel Egress and tunnels
fails: egressemailno cardDper-ip-shaping
| Free tier | Simultaneous Tunnels 3 ... Session Duration 24h ... Price FREE unit mixed; metered on none |
|---|---|
| Price | USD 0 (Pro USD 5/month) |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | No byte allowance is published. The page compares itself to ngrok with '2x the free tier bandwidth' and gives no figure.; ingress: http-only free_allowance: none published |
| Identity | email 'Start Free' account; MCP endpoints need Pro. |
| Limits | |
| Binding | per-ip-shaping Bandwidth is unstated, so an unpublished tolerance is what a 1 TiB/month user meets. Before that, the session cap ends the tunnel every 24 hours, and the protocol is HTTPS only. |
| Interface | cli npm install -g instatunnel. |
| Tooling | npm CLI. |
| Composes with | Webhook ingress only. |
| Reliability | Tunnels expire every 24 hours on free and the URL changes. |
| Notes | The 24-hour session beats ngrok's 2 hours, which is the vendor's whole pitch. Still HTTP. |
| Evidence rung | documented A published byte figure would sharpen the binding; a TCP or UDP tunnel type would change the verdict. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | instatunnel.my/pricing | free column: 3 simultaneous tunnels, 24h sessions, FREE; no bandwidth figure |
More fields (7)
{
"wg_path": "none",
"wg_detail": "",
"ingress": "http-only",
"volume_tib_month": null,
"volume_stated": "No byte allowance is published. The page compares itself to ngrok with '2x the free tier bandwidth' and gives no figure.",
"bytes_transit": "yes",
"transit_note": ""
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable