fshy

fshy / Egress and tunnels

FRP.VIP

frp.vip · Egress and tunnels · 1 record · JSON

FRP.VIP Egress and tunnels

fails: quotaemailno cardRper-ip-shaping

frp.vip/ · udp port forward · egress/frp-vip · JSON · compare

Free tierDomestic 1M: 1 Mbps, free, 1 port, frps version 0.35.1, note: free trial, one per customer. [translated]
unit unlimited; metered on none
PriceUSD 0
Per-object capnot applicable
Retentionnot applicable
EgressPaid tiers say 'unlimited traffic, fair use'; the free tier lists only 1 port and 1 Mbps.; ingress: udp
free_allowance: none published
Identityemail Registration and per-day billing in 'kai coins'; the free tier is limited to one purchase per customer.
Limits
Bindingper-ip-shaping 1 Mbps sustained is about 0.32 TB per month, so the speed cap fails 1 TiB long before any byte quota could.
Interfacecli frpc with a panel-issued config.
Toolingfrpc 0.35.1
Composes withCannot carry 1 TiB/month at 1 Mbps.
ReliabilityRuns frps 0.35.1, an old release; nothing about uptime is published.
NotesThe 'unlimited traffic' label is attached to a 1 Mbps pipe, which is the recurring pattern: unlimited bytes at a rate that cannot deliver them. 1 Mbps is 328 GB per month at full duty.
Evidence rungreported Numbers are from the site's extracted plan table; a direct read of the order page would raise the rung.
Checked2026-10-23 (live); stale on 2026-11-06
Parsed numbers
  • $.price_per_tb_month price-per-tb USD0.0 TB / month
Evidence (1)
datesourcewhat it proved
2026-10-23frp.vip/free tier is 1 Mbps, 1 port, unlimited traffic claim, one per customer
More fields (7)
{
 "wg_path": "inside-udp",
 "wg_detail": "An frps 0.35.1 endpoint; UDP proxying is an frp feature, but the plan table does not confirm that UDP is enabled for the free port.",
 "ingress": "udp",
 "volume_tib_month": null,
 "volume_stated": "Paid tiers say 'unlimited traffic, fair use'; the free tier lists only 1 port and 1 Mbps.",
 "bytes_transit": "yes",
 "transit_note": "FRP.VIP domestic nodes relay the datagrams."
}
Unknown or withheld values (2)
  • $.per_object_cap.stated not-applicable
  • $.retention.stated not-applicable